usr/bin/install000075500000427140147207357730007550 0ustar00ELF>@F@@&@8 @@@@@@88@8@@@$$ h h bh b 1   b bTT@T@DDPtdAAQtdRtdh h bh b/lib64/ld-linux-x86-64.so.2GNU GNUb `=l9">M   !BEKaƺ|= 9p|BÈ<9 qX PXpN$&  oEUkAf 0hcPx^uJx)\C2Y UcjDh d>2<N1M-OE}o\H^@9:(9*vGr} %n0t ,'b JA)b?b@bAbBbCbD bE(bF0bG8bH@bIHbJPbKXbL`bMhbNpbOxbPbQbRbSbTbUbWbXbZb[b\b]b^b_b`babbbcbebfbg bh(bi0bj8bk@bHblPbmXbn`bohbppbqxbrbsbtbubvbwbxbbybzb{b|b}b~bbbbbbb b(b0b8b@bHbPbXb`bhbpbxbbbbbbbbbbbbbbbbbbbbHHE!HtH5b!%d!@%b!h%Z!h%R!h%J!h%B!h%:!h%2!h%*!hp%"!h`%!h P%!h @% !h 0%!h %!h %!h%!h%!h%!h%!h%!h%!h%!h%!h%!hp%!h`%!hP%!h@%!h0%!h %z!h%r!h%j!h%b!h %Z!h!%R!h"%J!h#%B!h$%:!h%%2!h&%*!h'p%"!h(`%!h)P%!h*@% !h+0%!h, %!h-%!h.%!h/%!h0%!h1%!h2%!h3%!h4%!h5%!h6%!h7p%!h8`%!h9P%!h:@%!h;0%!h< %z!h=%r!h>%j!h?%b!h@%Z!hA%R!hB%J!hC%B!hD%:!hE%2!hF%*!hGp%"!hH`%!hIP%!hJ@% !hK0%!hL %!hM%!hN%!hO%!hP%!hQ%!hR%!hS%!hT%!hU%!hV%!hWp%!hX`%!hYP%!hZ@%!h[0%!h\ %z!h]%r!h^%j!h_%b!h`%Z!ha%R!hb%J!hc%B!hd%:!he%2!hf%*!hgp%"!hh`%!hiP%!hj@% !hk0%!hl %!hm%!hn%!ho%!hp%!hq%!hr%!hs%!ht%!hu%!hv%!hwp%!hx`%!hyP%!hz@%!h{0%!h| %z!h}%r!h~%j!h%b!h%Z!h%R!h%J!h%B!h%:!h%2!h%*!hp%"!h`%!hP%!h@% !h0%!h %!h%!h%!h%!h%!h%!h%!h%!h%!h%!h%!hp%!h`%!hP%!h@%!h0%!h %z!h%r!h%j!hAWAVAUATUSHHHdH%(H$81RH;Ld$PE1E1E1C!H5{ H5R`H==`zH=1`H=g~_L(1D$dDŽ$D$TD$eD$fD$gD$XD$hD$kD$lD$qD$mD$nD$oD$xD$rD$sD$wD$yD$\D${D$PD$zD$`D$~D$D$|D$uD$tD$pD$vD$}HDŽ$HDŽ$H!H!!!H=9_H$H$HD$ D$D$D$HD$HD$(@H !HN_E1HމctEPf[=~hCDD$f.pvstMH5l1|1H¿1;Ll!M(@T ZbsL8!AIHLEgmmo3L!IH^!=tK= L!I8`D$H,!oH!H HkH81=!s|$pDD$t!&=!pLZ!!IHHD$ L6!IHD$1t!d!=V!t_=N!t-H5,l11H¿1= !t)Mt$H5:l11H¿1eH<$Ht'H!H1E|$tD$Pt3|$puH|$ t;H5l1E1H¿1H|$ Ht EH!D=n!1Hc)EHu1M9$UH5\11H11*SuL!AIH$\du!K=}uH !Lz[H [H5|[E1HHC!H811Z1D$L:!IH!D$}D$nH5i11H11L!I8H5iǀ|$cEu MH|$HtNBHIlE1L1115L!1L1Ҿ!L!|$t =!<=!t(|$nN=!R!SH=!HH@]!H=I!HFHJ@%!=!OHLHމ+ADH;طH5iHú1rHH1111Mt$H5i1D1H¿1yH{qHH5eYL!HT$(I0LD$0LD$0$%=@jI8LD$0H5XIź1LH11gLD$0)H5X1zLH/oD$p ^MLE1E1T l$L,$DMIO,LyH<$1H}LHLHHA=EDID9t$AGI8LD$8"H5W1HD$0IBHL$00L1lLD$8!!H|$ 躵H5[g1ITI0LL1HT!H HeH81CH5g11H11H5gH5gH52h11H11p|$tqL;HkA?/Lt$@D$@AHLLH1ِHrEE1ADE1AHsH;LރUHcHDL0HD$LNwHHHD$HHt 1| /$H$L0D8EAxE119$~;LD $H5QUIƺ1[LHD1D $EHcL,yH|$pH5}UI1 LH11[Lt$@H=]!E111Lu H9D$@v6H=7! H5'UIƺ1LH11`HD$@!Lt$@H=!E111Lu H9D$@v6H=!虲H5TIƺ13LH11HD$@x!NLWH5S1HD$ HL$ HD1E11L$E1%=@ A"HD$H8ޱH5nSI1xLH114LHLD LκALE1$6EDH5S14$HH11H5kS1HR0HH11|X}/Lt$@D$@E1L蕻1I^HHPTI@AHЖAHǰ7@fDbUH-bHHw]øHt]bbUH-bHHHH?HHu]úHt]Hƿb=!uUH~]!@H=p!tHtUx bH]{sH(!D!HL HD$D$!D$!$zH(Df.SzH5O1HHH!H[H81 ff.~-u @f.UHHSHHu{-u H[]fDHD$ dD$ H[]fAWAVAUATIUHSHHdH%(H$1ztHT$ H;=!LD$E11HHL.S=`!}th=M!uD$8%=tOHD$hH$@HH$@HD$pH$HHD$xH$PH$H$XS+5!!VH5!H߽=!.H$dH3 %(H[]A\A]A^A_D-y!LD$AH$LLD$LD$H$@H޿LD$$r$XсW ЩJH$pH9$4A9%!;$\!j;$`=!t }$11LA11HAy@,H5%!DHtL9H5!H=!HH5!D tHIuD=D5ZH訫H5LHź1BH0HH111ff=!HD$H$@H޿%=:!t ;/4$XHT$H!H|$H\RLتHH5_K+@ RH-!1H1HHH5GK1.I0HL1HH5(K1Hw0H1H1@HH5KIĺ1H20HL111_?f.HȩIH5LHt$1҉RxlD$u ąBH5lL1(1H11DH5I1H0H11H5IHD$H=BJ HuHHHH|$SHC/uf.H/tHt H /uLhL)HzIHImLLHZ/1LfHLP@vfD8_INHLl$H5[K1HA4$HMH11<IzA}o_D I-A}".Ht$LHD$HD$eLD$LHLD$GLD$tYLl$Ht$LD$LLAH|$ELD$DDLD$H|$LD$DhmAUATUSHt@HQ!H5"J1HcHH!HH81wPL%!H5 J1I$"H1IIHHwH!H5yJ1L+HLOL+H5-L1LH.L+H5\L1LH L+H5N1LHL+H5BO1fLHL+H5Q1ELHL+H5HR1$LHL+H5WR1LHhL+H5nR1LHGHH5-S1HH&H52F1H SH/FHƿ11HtH5FH!u6I<$gH5SH1>HHƿ1I<$~gH5SH1HHƿ1f@USHHHT$0HL$8LD$@LL$Ht7)D$P)L$`)T$p)$)$)$)$)$dH%(HD$1HHHP!H8H=7WHٺGH$HHH$D$0HD$HD$ HD$HC(H;C0s%HPHS( HD$dH3%(uH[]þ HP@f.Ht2SHt [fDH߾[@f.ATUSH AX$dH%(HD$1t_Ax"IHt$LLD$LD$ H|$LD$3LD$fDH|$@AX tHt$dH34%(H []A\Ax%lAx(LD$Ht$LD$H|$LD$LD$jLD$LD$=tJ_tELD$H|$I舡H5)S1H"A4$HH11LD$Ax%H|$1fDHHN^Iċ=_HH5T1HA4$HH11VLD$HŋLD$=t?_t:LLD$覠H5'T1I@uHL11LD$Ax%D1=LD$LD$HnILD$xH|$LD$LD$Df.ATH=V!AUSHtNHu =DH)t3H-!H5-!DH9HFHhH9t[]1A\[]A\H=߽!HH!uH!H!H!wAWAVAAUATIUHSH(Ll$pHD$xH\$ht$LL$DD$IEHL9LHHFDHItmH)IE|$t5HtHHPH8u HH8HPtHxtH9|$LHsgI91HL$xHۈpH([]A\A]A^A_@8AH|$HD$cH5}X1HLD$HH11A01H([]A\A]A^A_D|$LHxGXH|$`H51XHź1H0H1H1G1H|$`蹝HH5WHxfHSHH EP"dH%(HD$1Et Ax'AEEX$EuEX HHEHD…H$HHD$HHD$xyB1HEHcHDEHHDPH\$dH3%(uFH [D1IEL!LDEHLD@E1Ax(=;SHHT$0HL$8LD$@LL$Ht7)D$P)L$`)T$p)$)$)$)$)$HdH%(HD$1Q0=uHD$dH3%(uDH[Ð_tH$HH1$D$0HD$HD$ HD$8SHHT$0HL$8LD$@LL$Ht7)D$P)L$`)T$p)$)$)$)$)$HdH%(HD$10H$1HH$HD$HD$ D$0HD$茹HD$dH3%(u H[@f.ATUHSH輚1HI诚H5 UHL1Ht0H虚H5THú13HHƿ1H!H8HG(H;G0sHPHW( []A\[]A\ Df.AVAAHAUAպATIUHHSӁA9E 8ItXL軙H1I讙H5M1HXAuMHH11[]A\A]1A^HutEt0HgH5SIź1LHƿ1_AHLjDuQ@[]A\A]A^f.HH5[S1HAuHH11O1If.AUATUHSHH86dH%(HD$(1ytmH}HH!H5R1H HH+!IHپH81HD$(dH3%(H8[]A\A]Ld$}LID]HDmD$HHq!H5K1AH|HH!L$$MIHپH81cff.S1Xu[fH5K1HHڋ0[1ATUHSy"uc@HGeIH1H5K1HA4$HH111m[]A\fDY%uy(@u$Gu"Iċ=t_uGt[]A\fHH= QIH@1@8u f.HLHH@LIrH q1HqSH={gHC8[DLrH q1HqSH=KgHC@[DSHHuR@u\@un1@Ht H@t 1HfGtCC[fH{@G@t1HfW@tDHfSHwƒtC[ff.AWAVAUEATIUSHH|$P"HD$X!ʉLDD$ T~DD$ t[Hŋtu {L蕔H59O1I/uHL11DDJ}D0IAAH1LH5H1IH)0LH11XC#H[]A\A]A^A_*LHD$XODLuH[]A\A]A^A_(Iƃt 5DLA.D1E7fJ!t@S18Élj.!)[DUHAWIAVAAUMATSHEHHLHEHHE HHE(HdH%(HE1AytHHtHLLLA}%=@&AEt0ۃDEEME1ƅE1t?I}8t8Eu3AEu+EH B%=EMA}-t6@t*E,1ҀHLIEhEMEA}!t;A}u4H.AEt A})HDžEME|DAA}*t EeAA}L@3MHLDžN@E1@A}LHL E1E8IaEMƅE1ƅE1EEEI}@LLTf.nL薏H5%0Iĺ10H0LH11E1HMdH3 %(D}He[A\A]A^A_]HHH'6H<EM)E@# HH5HHHLɑ A}HUH1IDH5 EH1MHH111D@A}A}+A}A}A}LHL]ADH茍H5.Hú1&A6HH11E1@A}HLDAA6D D>IċDD@Ht A<$A}-@1ҀHLIEDžƅf.MHLrD?@ A}+ A?/t@HN8.HfHH5QT}HHL.E1ƅƅuJA}uC@t7A} yA}$t%H1Lu A}%t*I}8t#L0HLvA}t@DEDvA}tyHH0HH0HH8HH@HHHAt8&DDEsDA}tvDu D;,H(DHLHD$$E1ɃڀEӉA}&oA}A}yA}* EME !D HDHD6H5E1IHX011LHA}#DHHHF0HH@AM-HAHaA}$H8MHLhA}-H$L1IH5DH1LHHڿ1AHAH9A}E1Ɂ@ A},;1A}tA}t1HH9HLLDDvDDHHtHHH.HHt+AM-HAHE1gADI}@LLKALD跆HH5;TfD fDH脆IH5BLDaH5!AHú1HH111DfDA}-t*1ҀHLDIEDA}  HHtI}8HLDJDFf.HHH,Hf.A}AEh EV(%=@tL@ t3A}t,I}8HLDID@t(%=@w EMEuEE0 (%=@E EK A}uA}! H  HDD費Ds~8ID[HH5>1H蹼A6HH11wDH0HHH趼H/HH5!臃H5!1HvH5:Iĺ1 IHL111HDHH9`A}A}R#HHDHHDH0LHH踻D1HH98MHLH%=Au A}A}B%=rAA%=^HL1IH5<Hú1裺MHH111_E1s1ɋML%=:(%=$HLDD6A}AEAwDHH'A}tA}tA}LA]"EDH޽HH9uHH9LjH57Hú1HH1111HDž諺H1AƅƅdD(DIċA}uA}t`AA%=tHIyvAHLLHDƂDHL) B%=t5AA%=t%IAH9BsIH9gA}A}t%=<A}tAA%=.A}B%=H0HHAA%=)HLHHH98HH90A}=ADHMLoHHHtTH HHt@H9PuH9HuL}H5 6Hú1膶HH111E7H0HHD$/HHHHHHPHHCu(%=@6 HD!H;}H5yIĺ1յH]L0H11茻~H|L1I|H57Hú1胵A4$HMH11=HHJ#E1>A}HAEtJ-A}."(HDDADDHIvDDmDDHHA{HL1DrDA%=@(%=@Ez LDDu>8.DDXEu(%=@HDD]/LHH蛶D A}PH501莳HLzHI1zMHH111)H荱E11DžƅxA}u%=E1ƅE1yAƅE1dA}t AULyH1IyHH5.%= ' LyHH55H11AL?1E1ƅƅA}t EuEH/yH5.Hú1ɱHH111舷E1蛱;I}8H=QHxL1IxHH5/LxH1IyxH5/1I#H諯0MLH11׶HIvDDDD$HwL1IwHH5/HLD {E1ɃDpHH0H1#H0 HuwIH535HH9b(%=HށU0ƅH84 A}- A}?H1HH9A}$]1E1ƅ H5!DtvH5ݹ!1IcvH5\-Hú1 MHH111ɴHDDHLV(DA}#1Ҁx.DHL~rH5-1IH蠩LHڋ0HMLpA}'eLrH1IqHH5='Au$LqIH5-H0H޿fH8H9H肨HqHH5)LDL,HPHLHH)H|$/H茭HIHL.DaEMƅƅ/HH1HDž#GXH辬?HpIH5,ZƅzHL#HH% HHЩ胧A},tu(%=HHpH5(1H蛨HH11VHIyLLHDHDHL~HHDHrHHAE1ɋDHD)oH5)Iƺ1çLHƿ1E1EMƅƅDHnIH5ZHI9E1dD8IDHnHH5m)Dž4KLXnH5[*1IHz01LH1詬H 094H1mL1ImHH5#H1LHHHHADpA}"H1G1茤A} IDA}$yy A} DžJH0HH$BA}0h tHcHHH1HHu1ҸLhHI$HHHCHHH9¸LG110H%=wDE1HHII)ؿLDDHLH9LHF$DHLDAAuHHPI9LGIt 1HHH)I9IrHuIƅxHDLʐHL1HDHHH)EHXdHDž`%=u AE `H1HhH0HH*HA11LPLHHHLLIIH@IDH D LLE1Hh!DHkHPL(L`KD%H9s I9ILOM)MI)I) 1LHl`1LԣH AHH`LHPHXHD$H@ALd$EHD$HH$ HHITDEH9 DAD9 LLD9AE1DHkHPLhE10AUHD%HhIH5#H0LLDKDLHHDDH5A}$tA}HvhLXH51蛠H#HD!7* (ЅLfQHLLLMgH5"Hú1Io0HL11螥HP1ۋ腡HfH5"1I苟H0HL111@AA}DH1AD#pDb*觝DHA5Aƅ0H8t)H1HE1HHр|/AAƅHDeH5Q!1H|DHHDkAu$H1LD=DbA}%W1HDžQ1E1ƅL2eIH5t!A}cƅAƅƅ#LdH5 1IoH0LH11&ƅHdH51I(H谛0HL111ݢHDž=HDžA}2A}tyDD;LuP9t[HDLHHHD$$ڀEӉA}&tdHE1䋍HM苵LuA]'Et H#pA}A}A}*A}ЅpHCHbH51IiHH0L11A}#EvH0H9DLH3H蕙A}-t4HbH5Iĺ1贚LHƿ1A} pHML aƅ1HDžsHaH5Hú17HHA4$,HHH@HHH9HDA16"HD %H^H5H1謖HH111k$AH)载EuLLLILLLPALLVHHDxHXMHD$HLAHD$HD$HH$蜽%H0赖H0HdDE1AM D%=t1ƅxaL\HH5dHHHH9}ADIHLLL \HH5CHHIH[H5o1IzH0LH111DALLLL[HH56HLŀHLH1ƅxHHH)HXf.H8dH%(HD$(1H>9DQ ABA0yu_~HD$'LL$LD$IE11HD$$H5 !H= !D$'Ht$(dH34%(uYH8y+tH HH5$H= cAxH H5H= 7RH H5H= H H5H= H H5H= ՓH H5wH={ 趓fDH1HH@1HH9t@HFH9G@SHHcH[Zf.SH H<$H=!Ht$HHD$dH%(HD$12HHtHx HHD$dH3%(uH [fDH(H<$H=I!Ht$HdH%(HD$1'HtH@HT$dH3%(u H(1f軑f.AUIATIUHSH}HHH=ɛ!HHCL#Lk^1HHt*H9t!H{(H HEH[]A\A]Ð1LH bHKH1gK)HHI!tHEDH=1!t+@>FHF HFFFFAWAVE1AUIATUHSHH_ HWdH%(H$1I1LHAEA} f H$HD$HHT$LD$1e}D$AEM} L)LH4@HAEH|HIE D$H|$0HL$ HH)H9ID$ 1IEP(9S@HHSH9}II)I9L)HHx9t$HHH)HLHxHH)H9vH H5H= fIUH9DAHuHHf!Hn]!H ALHHf.HHt>uH=k6~H=^HHHHuf HHEH9HHFfHt1IHIHtLI1IHu1HIIILI9w1LHL9uLAWAVAUAAATUSHdH%(H$1DH|$4$D$FeH|$YHD$[HMw0HgIH11u~H9^!8bwf1qH}ypH}HphH[]MDv0HH11}f.fH=!@=т!USHHW!H8ˣt=!t$iv8 uHW!H8襣uNH[]H5m1wH=p!HHt3=Hv0H5IH11C}H ]!85vu0HH11}fAVAUATUSwHHt H3zvH[]A\A]A^fJAx:k}IuMHD0t8HLxDuH[]A\A]A^DSuE1HD0DxxfDHwHtHHeU1SHH?/@HH)H9v+x/HQtf|/HBuHH9rHH[]H@f.AUATIUSHHLhH@@L4zHt?HLHy@HuHH[]A\A].L1f.fH/uDH/t1H„t@fH t/t @tHH 1ufSHGuHv |/HPt[@HHu[D wf.HtSx11[Df.@HXHT$01dH%(HD$1@@u'1zHHL$dH3 %(u*HX@HD$`$T$0HD$HD$ HD$tfAUATUHSHHt^II`LHbHID$HHHCI$HCdHt*H9tHH[]A\A]HH[]A\A]bH(dH%(HD$1Ht#HBH4$HHD$HHD$ HHL$dH3 %(uH(sf.%=n=@s=`x= ==r=w=s?EЉ%ໃrF%ඃwF@sF ໃrFඃwFtrsFໃrFඃwFtF F tF ÐF F ൃxF fDൃxൃx8DcfD-fDdfDbfDlfDpfD(HHtH8`AWIAVE1AUATIUHSHHHHL)HH4H4$t E1|/Aƀ}/Ht~H6qH $HD$J|1H@uHItxH$HLvM/J<0t1}/HH)IHT$H^vLH[]A\A]A^A_fH;/uH;/h@1f.fAUATUSHHHt_AHE1Ht3IHH)tHHD:HuHL[]A\A]fDnHL[]A\A]E1f.AUATUSHHHt_AHE1Ht3IHH)tHHD9HuHL[]A\A]fD#nHL[]A\A]E1f.H  IH vbHIHHRH9tBA fD1HIHHtLHH9r1HHHu HHuHùHHrH1HHHH9fSHHHsS0H;Cs HH[m@f.AVIAUAATIUHSIH0HHtxI9t LU8t`H3Et.HCHLLPL LSHHMHHHHEH[]A\A]HA^H0L9t/LU8uH[HCHu[]A\1A]HA^HCH0EtHHHKHHMHHHHEHH[]A\A]A^DHxff.HHH9tq@.vS .vFH . v8. r+X P.v.r .wfHIH1fAWAAVIAUATIUSHL.L;n@ImHtpI]HuX@HHHHKHXt?HH+LHH8HSuH(ID$HHID$HHCI\$HuImEIEt'IM9nyH[]A\A]A^A_DHLmH8Ht?ID$HHt@HPIT$HH(HSHPHCIEIInM9nH(ID$ؿpHuH1[]A\A]A^A_f.HGÐf.HGÐf.HG Ðf.H7H1H9s9fH>t&HVHt@HRHHuH9HBHH9rHLG11L9s6H9t'HAHHHtfH@HHuHL9r1H9wtH9W AVAUATUHSH-HIHIHIHKLHH1qHG1LHqMxbI*MYxuI*^H@LH߾KqHHH[]A\A]A^1*qf.LLHH MH*XY=yLAHL H*XuATIUHSHHHt#HH3H9t#HAT$8uH[Hu[]1A\@H3[]HA\f.HH t+HHOH9r$HH9sHHtH1Hg@f.UHSHH?HHHRHtH9uHBHu#HU HHu HH9r1H[]HH[]ff.L1L9OvWI Ht7H9vHH IIL@LHt@H9t+LHLDHIHuIL9Owf.ff.AWIAVAUATUSHL7L9wvPII1I>Ht LH;LAԄtH[HHuIM9ww@HH[]A\A]A^A_1fD1Et%DHHHH)1IDHEuHff.G?GL?G ?GAWHwIPAVMAUIATIUHSHHLDHYHLDMkHHQH:HH{(HDHk(f}MuKMI*^.".\ HL,I1DLHHH9wfHHkteHhHHtPHHCHC HLk0Lc8HCLs@HHCHH[]A\A]A^A_HCH8dH1[]A\A]A^A_L,NfDLAHL H*XD1ff.ATUHSL'L;gsoI<$t^I\$Hu 2DHHE@HtH;HCHHUHHHSH]HuHE@HtI<$I$ID$IL9ewHEHE []A\ff.ATUHSH@tH uqHELeI9s1fDI|$Hu @HH_bHuIL9ewH}HHufHH_bHuH}b[H]A\bL'L;gsĐI<$LHufH;U@H[HuHEIL9wXDf.ATUSHH`Ho(dH%(HD$X1}MuFHH*^.U7.L2\>HH,H1HHHPIHH9L9cLfHH$Ld$I1LHHHD$HC0Hl$(HD$HD$ HD$0HC8HD$8HC@HD$@HCHHD$H1HD$HHHHCH1HHH<$a fDHL$XdH3 %(usH`[]A\1@H,fDH;`H$HHD$HCHD$HCHD$HCHD$HHCHHHH H*XNb`ff.AUATUHSHdH%(HD$1Hw1IHHIwHt2MI$1HL$dH3 %(H[]A\A]@HCHKH*HCHS(HH*YJ.w^H$H88HCHHHPHSHH(H$HJHHHBHC ff1VfH{(HCHS(HRH*HCHH*(Y.\zYB uY.<.3H,H1LHHH_fDHHH H*XfDHƒHH H*XfDH(HC HCN\HH,H1VHHH H*XHHH H*XdH`,`ff.{f.SHHHdH%(HD$1Pt#HHD$HL$dH3 %(u H[1_Df.ATUSHHHdH%(HD$1HHNH$Hk H:tHL$dH3 %(H[]A\HCHHHCH*HCHS(HH*Y .wHfH{(HSHC(HH*HSHH*Y.vxY@uY@.H,HH.H{HHuLLgT\MuHCHHHHH H*X.fDHƒHH H*X1\HH,H1XHуHH H*XHуHH H*X]f.DUHSHHH?謊H3E1HH[]HfHG1HHHFH9Gt1HFH9GuH6H?{'f.1HVH9WtHNH9OuHH6H?_Hf.SHH?ZH[Zf.AWIAVIAUE1ATIU1SHH(Ht$HL$IAT$A$MLLHHLL$HLL$$$D$   A шL$'DL$t$HLL$HHD$(YLL$tX|$ D vEAH !H5IHú1YHHD11c_1H$dH3%( H[]A\A]A^A_1fLHADD%$D!҃D$'yf.DEAE׉T$f.DfEJfDMHt$(HT$0\D$H%=@vf.HbfDVD D$Lt$(HL$0HL>&!$HD$ T$E|$0IEƉ $$H蜊Et!A"MgV8 YVHH|$'HH5'HHE1WuHH11V]1E1Wf.ATUSHPЀHf.<+t 1<-HHτuHH9HCL1E1D#Aa~gAo AuAgHT1[]A\f.1@HЀlHvA-t A=tA+uIHIIgfD@o6@uHAPE D!EAxEHEAP D#A+tD-IHsHS@gNЀw;12DVAOLHvf.Hӿ1fDX@ M@Ic LfDH3Iʒ $H8DHDAHA8A AH)ڻH  2A=@@hX @[]A\DE@,u>HE A@A@AHA@*A,uH)@tXfE>HD(:B@SHHHdH%(H$1W1҅u-\$ Q@=@H@X@ @H$dH3 %(Hu HĠ[S@f.AU1%ATUSDYE:@E1DAuWA!EA$AEEAAA$AEAAE EAIAEAAIE E E˅AADDE!DE!A-A=tjA+uD D HDYE@DQ YEAA AE!ADQ0AEAIAIA EEsfDAڅAEDHE D!ED DYAAD E}MtA8[]A\A]f.D AD!DfHSHtw/RHtRHPHH)H~BHpH=u.H=HH@@8uHXH1!HH7\!HHm1!H[Hq1!H=j7HPXOf.AWAVIAUIATEUSH~SHHHމ8O[OD8ID H-HmXHD[]A\LA]A^A_BfTHHN8讅HD[]A\LA]A^A_HXAu?AA@tg1H[]A\A]A^A_@HھLRDLtH߻WDLvE>뜐@LTHHt+H¾@L;RuHMWcQfDMD HHWD#+փtTTf.AWAVAUIATAUSHQHHAHDBMu6HV%=@tx1u5H[]A\A]A^A_3MHID8eVA>݃uYHD[]A\LA]A^A_.fDH¾LQqLxNxxfDE>f.HHHdH%(HD$81HHt]4$H$HL$8dH3 %(HHD$HBHD$HBHD$HBHD$ HB HD$(HB(HD$0HB0HuHH NLAUATAHUH1SHqMH9HtHH[]A\A]{߀UuhP߀Tu<P߀Fu0x-u*x8u$xu;`HHyHDHlHfAHE|DGuP߀Buπx1uɀx8uÀx0ux3ux0uxuIHHA}`HE#ff.AWIAVEAUIATUSDHH$H|$(HL$ DD$4D$HD$XH$H$H$ HD$xdH%(H$1LH$AD$3 HDL\$ HcHDD$3D$ E1HD$h1D$3M1MMރD$8D$ $H$HD$`H$HD$pL9IzMAt |$ M)E1E A~H AHcHD$4$HEI9A|)?uA4N߀wrHQ8tb|$3L9s H|$(?HSI9v H|$(D"HSI9v H|$(D"HSI9v H|$(D?HAHfD|$8t $u!Ht$XHtDDҋrEt|$3L9s HD$(\HHL9s HD$(D$HL9IA<)~HMMu|$4u |$3|$3u6H|$ht.HT$ht"HL$(H)fDI9vHuL9HH|$(fIIH|$4|$3DMMHD$xD$LDD$4H|$(LH$LHD$H$AHD$WH$dH3<%(H[]A\A]A^A_fDr|$4{|$ -A\Dbfffvfnftfaf|$ }|$3L9s HD$(\HUHCI9v/A|)WЀ w!I9HCI9v HD$(D0HCHA0cf|$ t|$3t ED|$4%|$3ZL9s HD$('HCI9v HD$(D\HCI9v HD$(D'HDH$LL$PLT$HD\$@NHAD\$@LT$HLL$PPf"T$ H|$3HL$(s@L9s\HsI9vD@0@tHsI9vD@0@tAHA0HH9jL9sD$E$)HuEtL9s\HE1D|$34MtHD$('HD$ AHD$hW|$3MtHD$("HTD$ AHD$hD$3D$ E1HD$h1H D$3D$ A1D$4HD$hDHD$3D$ A1D$4HD$hD\$4t3H=L\$ H=H$~L\$ HD$x1ۀ|$3u/H$t HL$(L9sHuHl$xL\$8HDHl$hID$ L\$8INdu%IvLLT$HLL$@DLT$HLL$@IM9M)rOHt$hLLLL$PLT$HLD$@FLD$@LT$HLL$Pu|$3 AE1HD$`IH1H$D$Hl$HHL$D$ALl$PMLt$@L$HD$HHT$@HL$`H|$pL,O4/L)L,DHHHH|$3tL|$4uEHt?fDA<O!wHH+HHHH9uы$JH|$`DDHEJ:DD$D$HHl$HL$H$Ll$PLt$@MH"T$ $*HLl$PL\$@WAy@LL$LD$PD\$HLL$@\BL$ILD$PD\$HLL$@#|$3zDH|$(0"DHHl$HL$D$MH$D$Ll$PLt$@ HHl$HL$D$D$MH$Ll$PLt$@MMLt$@LHHl$HL$D$I9D$H$Ll$PL$v"A?uDA<tHHTI9wSHnD$ A1HD$h3NAHJD$ A1HD$hAWLcAVAUATUSHHHHt$ HT$(-?IŋEL%&!D$4kD;=u&!rhAoH&!ALHI9-1V-H5_&!H=`&!IH>&!H0Hx=)&!L1H)HHLyA- &!HC0IkMDL{M$Mt$HD$HC(HL$(HT$ ALL<$LHD$L\$8CL\$8I9wnHpHJ!I9I4$tLHt$8=Ht$8HHt$86,ID$IHC0DHL$(AHT$ Ht$8LHD$HC(L<$HD$D$4AEHHL[]A\A]A^A_ÐL(,IH%!=@ATUHS=H=J!D HHþ8HEV-D#[]A\@f.HJ!HHENjDf.HJ!HHElj0Df.HiJ!HHE@@H4~1ƒ1Vf.H)J!HHDGwÐf.H J!HHHDHtHt Hw(HW0H|AH)HcHL(1AAfHDB L%0fDAVl@8AFVAA.AF.fDAFlH κH5H=M1DH H5H=/)1f[.tuAAFH tAAFH ?H5H=й[0f.ATIUSHdH%(HD$1?HHcHf._'Hl$[D1HL$dH3 %(H[]A\f{-HAD$f.[-81H4xD$AD$ǃt ,D$wD`3u3A$YH H5ZH=/,A|$(H0A$Al$>H H5H=,R/m.,fDS?HwWHZHcHD/[ËGxH BH5H=.f.H H5H=Ƿ.AWAVIAUATIUSH(H $|$dH %(HL$1ɅD$D$ x=AHHHƀ8/HDfDHH:/u|AAuHl$1E1HD9l$~4T$ IcMD$H%=toHT$H޿H$dH3 %(H[]A\ÐHT$0H޿u.HT$Hz?tKHz?ta&Du]'!r'!DnfH$HL$xHBH HT$DH$H$HBHJq8&uifAVAAUALATALUHSAHHt`Ht4L.DIDHD1GH[]A\A]A^HDHD1I H[]A\A]A^H5Z1VH0H11 f.II111AWAVAUATMUHSLHXHIHI1H!H51H HAH1 H5c1HHI HJcHf.LK8LCH5HC1Lk0Lc(L{ LsLL$@LD$8HHD$0/LL$@LD$8HLl$Ld$HL|$L4$LL$ LL$0H1# HX[]A\A]A^A_@LS@LK8H5)HCLCLk0Lc(L{ LsHLT$HLL$@HD$0LD$81LL$@LT$HHLD$8Ll$HLd$L|$HLL$ LL$0L4$LT$(1HX[]A\A]A^A_ÐHH5]1"HXHH[]A\A]A^A_H¾1/LcH5,H1HXHH[]MH¾A\A]A^A_1LkLcH5H1HXHMHMH[]A\A]A^A_1fLsLkH5٣LcH1>L4$HMMHپH1O'f.L{ LsH5LkLc1HL|$HL4$MMHپH1LCH5Lc(L{ Ls1LkHLD$0LD$0HLd$L|$L4$MHپH1nLKLCH5ILk0Lc(1L{ LsHLL$8LD$0(LL$8LD$0HLl$Ld$HL|$L4$H1&IHH1fLS@LK8HCLCH5DLk0Lc(L{ LsLT$HLL$@HD$0LD$8HE1I8tIK<u@HhLE1dL%(LD$XE1I$ELXADMMOt.II t$DA0rLXMSLPMMOuHD$XdH3%(uHhIfHLD$@LL$Ht7)D$P)L$`)T$p)$)$)$)$)$dH%(HD$1H$IHD$HD$ $ D$0HD$HD$dH3%(uHfSH51 HHƿ1fH51H Ho|Hƿ16H H51HHH[ f.=!t!H!!HSHHt[HtfD1HHH9r HPf.HSHtHHt[Ht1[HtHH1HH9r HP]f.HIHt51HIH9s=HAHHHIHXHu1Ҹ1IHHP@f.HHt(HH9w0HPHHHH@HHDHHPSHwH1H[fH7HtHXUHHSHH,HHH[]HSHwHHp[f.H5H1)H H11:HH1Ht Hk8tH qH5BH=F)WHt1t@H~XfS11&HHtH[f8 uAWAVAAUATUSH(dH%(HD$1$HD$HIHIMLDHH fDHDBDJ u-u0H|$dH3<%(H([]A\A]A^A_;DLHHD$2M7HHL$I9u1MtAuI]놐"rLT$HT$0LT$HT$tAFEH&H1HH9 H 1Hc1HH1HE1D ƒtH9sHAHc1HH1HE1D ƒSH9sHAHc1HH1H9YE1HD ƒu Hc1HH1HE1D ƒH9sHAHHc1HHH9HH9H1HHc1HHH9vHvHc1HH1HE1D ƒKH9sHAH?H9wsH 1Hc1HH1H9r^E1HD ƒu1A~BL k\HAHHA뚺H{ H ěH5H=`< f.fAWAVAUATIUHSH(dH%(HD$1HHH$HFHD$LvLt$HE1I&ƒL$H: LIBHt INj$0rHT$HBHD$DH=HxIH4HUEL2L1 HIHLLIt'E0rHUHBHEſIHÐLHL$dH3 %(u!H([]A\A]A^A_3 K1 @HIdH%(HD$1tx<%uNsuHI1 %u;xsu5IAHIu^HT$dH3%(u8HfHHLB.H$y8 t11fD[ fDS 1H dH%(HD$1H Ht$H|$HD$HD$HY H~HT$DH|$ H|$HL$dH3 %(uH [ @ATUSHPdH%(HD$1HD$pHT$0HL$8$HD$HD$ HD$D`/!$D12!xl=!uc1x߉1u9"D HʼnU Def.HD$HP1HL$dH3 %(uMHP[]A\11b8J11Dx8!>jf.HSHt uH[% DtHߺ19H[ 1HO H9O(wHG1H+GtHWXH+WHHDSHHHGH9GtHH[ HG H9G(uHHuT$ H4$" T$ H4$cHt #H1H[f.1HVH9WtfHH9fDHG1HHH1HH@HH9fDHH1HH9@Cf.AUATIUHSHHH9W8Lo@HGHfHHXH[HuH}LLkHULHHIH L LAHHMAuJTHBH[]A\A]Hr(HH9Hw8w!HH HtHEKfDH}HEHE8HH[]A\A]HH1ff.AUIATIHUHSH HHtYHHLƄ+Hk`LcPID$ C@HCfStHC HC81HC(fCrHH[]A\A]fUSHHHu"HH{HkHtHHuH[]SHf.H2yHL2t[fD9USHHw,9tDu"CHu fxk,H[]DH{`1xk,H[]ÃtU1SHHWHut(yH{`0H[](1@@f.AUATIUHjxSHHHzXuu uHs0HbD IADc@@Hﺐg@E@#1Ht Ht 1HfGt H[]A\A]HS0AHuC@tD t1H[]A\DA]DC@(fA$H H҃H)Ѐ.HChJ t.)H{XDHfD1HfOfDCxHfHs0HRAE SHHHH9w$HH?H~Ht9H[H?H$1[f.H;XH1[f.SHt4L H H1胙HH[ HH1Ht-[f.IЉS  ʁt!L175Åx +[ÐL1tAUATIUSHHtxNHHHCxHHEHH]HEI<$?IŸL9t%HD$ MtaIUD$ fKpHH[]A\A]fI<$Hrx,tHfSpH[]A\A]H[]A\A]H1[]A\A]AWIAVAUIATA1USHdH%(H$1MHT$tA8.uAx.uAxA_H݃tOt1ExDfDH$dH34%(H[]A\A]A^A_DDEu)MA8.Ax.AxHT$ DL$L$EWD HDD#<@v޹A,L‰L$LD$SAA_HLD$L$7fDHD$H|$(H98u,A_HDDwXfHD$ I9Et6DMw`LD$L/+LD$SLh+ALD$x2A_HAĹtfDDL2AwHbf.H(HdH%(HD$1uAHBHtHxXxH6H~t}HH9>tKHD$dH3%(u\H(fDHBxH9HH$HHD$!Ht2HfHRxH9VuHPxHVHHHDAWAVAUATUSHHL/dH%(H$1t$XI}HD$^8CH KHIu0%  10&HOfA}p IEn{HH{@H1HD$ Hd$ Hl$ |$XtCHH|$^D$_u-HAă|$XAEED$_fDIEHIM8HD$0|/HPHDƒHs0HHHHD$8HC0D$]HL$E1E1H4$IuXH) $HD$@HKHHC HD$Ll$HHL$PHt$(HD$HDHt$HD$(IEXHIuHIEIICHIIE0H{@t CISH1 1fAMpAN w HH?AIEH?HH|$IIL9d$ MoMHD$HxHoHICH u x.InHrHHHHIHPH9$HHt$8HK H|$HHHt$@H $kHC H;$tCHD$]t HD$HD$0HC0HH$HD$H)$HHt$hMLl$LH|$I}IEfAupKH@$1'IE8H|$0IIE0IE`HP f.{,Ht$P1L~H|$fAEpIE^IL9d$ Ll$]|$]Ll$HCHS Ht+HH0HH9t H+H8HHH0HP8H@HuHD$HHxXHH0HH9t H+H8HHH0HHHP8HuHH@xt fx.M1AF9HHS HJ/HL$0W 3I}Xҁ IIuxE1Ht{HD$_{H5ID$_ HH)€|$^NLcXLLq{,HsH1L{HLLu 1xs!"fDEtEu=fAMrI}IECIt xIED$_{H<AE@@{,MLl$LHD H|$I}RIE1fA}pKH@DeH$dH34%([H[]A\A]A^A_Iŀ|$]"CHtHD$H9C0tMuHl$0HD$0|$_t3|$^u,Mt|$Xu)I}XHMI'v"H{@2Ht$LH2fH{@tIwHD$fLl$I}H1)IED HÉD#|$XIE1{,HsH1LLfAEp{HIELHHHpxl|$XtJH|$1ZI}|$XIEzAfEEpAE@1!fAEpCI{,Ht$`uHD$`H=iiH=HVHt$LHHC@rHC@HD$H|$fAUpKH@19fAWAVAUATUSH($%=@IIHI1LHMt$@A\$HAD$,I}HCM1KH9HBII?HuHUHHBIt$0I|$ uD$LI}H5u1L]HH$H@XIuMtAD$H D$HID$HI\$HD$11HD$C|$ MILJfAOpIoLHM|MLFt$uHvA|/@LHLHI6H@XH$HIGIIG0ZA|$,Ht$1LMfAGpaHIGHD$HL|$LxM|MIH6H5^t1LHI$HhI$ It$XfPpA|$H(tlAt$HI|$`H(L[]A\A]A^A_fA|/HHuD؀AD$HrfDHH<$I|$ L1H([]A\A]A^A_@ H(1[]A\A]A^A_@A|$,HAD$(/AL$H$MHHLH1H$ML|$L1O1uf.ATUHSH?HtIHXyDH{Xx$HH_HuH_H{XyHH}HtH}H} EHt`},x@1H}`H}PHtEHH}XtRHtH@1[]A\Ðu}(uE}(t_IA$fDf;nH&}(IċYKCiDf.AWAVAUATIUSHH/dH%(H$1HGI@Etf]tff f}pu3fDI$HH{XqCtfkHH]HuH]H{eI$HH{XNf{p IT$ HCHH{XCrGAD$H{DK@fCpAD$I@uHAL$H@1H$dH3 %(bHĘ[]A\A]A^A_DEpPfBfDAD$H@IL$H9MxErZI|$HtID$AIt$XHfDUpA|$HHOfuDLP$AD$HI|$XTHt*HS`HHHSHI|$ H/HHt+H9LpLHPILHLk`ID$ It$XHC8HC0A|$HI$Spf fH|H{Xu HCxID$A|$HIt$XH@H؄M 1;f>HSHHBHHR8|/HxHEI|$ /HC`HHPI$Spf \HH&H[I|$H LE0HHuxLUt6,fMrE@I\$Ht"HCH@0HC0H[HuI\$ID$It$XfSpA|$HHUHwH,1HfEpHHCLxLHHpxkC@AL$H@LssDL:HHwH,HHffEpAt$H@A|$,HxEDvfMrHsI$1AD$H,ID$LHID$Hz H{XHk~H}huAD$HA|$,It$H1HfCp%=@H{XHEhHHHEhSp}DI$IT$ HCHLHHtsHMA|$,It$HHQffCptZfst{D|T{D(IAmk@AL$H@UAD$I@~H]At$H@uA|$,H@vCDfKruA|$H@3DM@Etf}ptAfDEpA|$HIt$XH>HL}PAGIMwPbMHExHLH$7|HtJDxE.ZAfD]pE@@f{pC@HIA,Ht$E1!u H|$sIeRAE}HExLLIE詅HtDI9^VL H XHA1 }HIIGP _L8Rw fVt1@HgHAVAUATAUSHH/.CI@IMpf 1fuEH{HtA At8H}XuHE08/t sH@t7DHHC[]A\A]A^KH AH}XtD{,HsiDHCIHCtZHkHC[]A\A]A^fD[HE]A\A]A^31[]A\A]A^f1YfYu>@HC1)A]1A]HtH t H@HH=.s HuH={_@f.SHHމ[|ff.SHGHމ[\ff.SHHމ[/tkLt$ HLHILHvD$=M9tLL$ H$L$ H$|$tW\$LHt2-H$dH3%(aH[]A\A]A^A_ Lt$L2Ex D9d$DLH~1LLC9(7fkD$fQ] T&K_Bf+{@(HL+(@L \w8k8T@AVAUIATIUSH dH%(H$1&MtI}?tgI}?t]LLA DH$dH3%(UH[]A\A]A^fDHL$ ALI}?I}?IEIUH$HT$IEIUIHD$HT$=f.;tLt &< x8&u LL1@tfDI}?HD$hH$HD$pHD$6f.HD$xIHD$H$HD$dLf.fSHH1HdH %(HL$1HHHHtBH$HwHH\$dH3%(u'H[HKиfAUHIATUSHLd$Ht$HD$dH %(H$1LHHYHHHl$LHHH9w@L9tHHwMH$dH3 %(uRH[]A\A]L9t!D(IHE,$KLUf.@L I E111f.fDAWIAVAUATIUHSH(H<$HT$M7MID$HD$1Rf.HD$HH|$LHIH L$EȈL$HLM4Mt@H4$LL9uLL9tXH|$uH\$HLM4Mu|$HuHD$H([]A\A]A^A_fDD$fH(H[]A\A]A^A_HD$ATHUHSHtKH5 i1IHHھ1HLH]A\111cH5h1If.AWI1AVAUE1ATIԺUHH5hSHHi H9HH1M7Mu?rfLIeHuhHH, HLH81M4Mt5HtLHL2uLH.hHf.Hѷ H8HG(H;G0sHPHW( H[]A\A]A^A_H []A\A]A^A_Zf.AWMAVIAUMATILUHLSHHHHHxH[]A\A]A^A_HLLLHHAHAVAUATUSL&Mt2IIHHnLeLHMtLHLu[]LA\A]A^fAWMAVIAUATIULSHH(dH%(H$1M<$Hu Ld$fMfDHHUHItiHLL<$AHHH9M9tLUH@H9vHH9HHUHIuHEHtHK1 H$dH34%(HH([]A\A]A^A_HD$HL$"J1M9HD$$tLU$HD$DHD$HqAD I9tZH9v'M9t"HELH_LHHENLE{1$+H- qHH4$UHHH4$tHHLNH f.U11SH(x2ƒ@D19tH[]øf1Ҿ1fATUHS]HIv …ut Mt,[]A\Dһub[]A\DK1ۃ8 ۉ[]A\f.HGGÁubHWHt&HH9FtEHJ1HHOu.HuHGHHGHFH1fDHGH9uH cPH5cH=c<UDSHH1H dH%(HD$1>t!H1H$HHD$HiHCHD$dH3%(uH [f.@Ht$1fDH7HHHu1HH1GGG7www wDf.GÐf.GWDDƒH 1OW9u DOGf.SHu)SsH 1;StS[C[%DAWAVAUATUSHdH%(H$1L5 HHH]UHDMuLhIlH[LtA.@t)LHt @*uA~uL)I\;HaHDH$dH3 %(H?HĨ[]A\A]A^A_H=~aHIt 8gL=Pa A A</A$.MI}HHLLH$tBD%/IHcharset.IEsAEaliafAE H1>AH59EHIHD$`Ld$ H$HD$fIGI;G?HPIW8 tGvڃ#L)HL$H5h`1LL L H!%tLT$DHJHDHL)A I!%tDIJLDIL+T$H<$I&HHHxHT$LT$H $(LT$HT$IM:L4$HLH)M)LLHt$K|5MIGI;GLD@L5hRHL5 E1$H^HItH@DtIGI;GHPIW u݃LdH$HwAtH$LLT$HT$HHHpH $LT$IHT$L5Q<LL5QLLt@af.AWAAVEAUIATAUSHdH%(H$1DD$ HT$DD$ Ņu&L$(%=@zxtGbD(IĉE,$H$dH34%(Hĸ[]A\A]A^A_fDYDvDD$ af.AtjD9d$,tcۉL$ DDxuL$ uVIuy1D1 Ѕ$<$!D xdzAtD9D$0u밐fALtrL$ @ʁ |L$ cL%fSH5P\1jH ދ:H1%SH5P\1:HӰ ދ:H1HXHL$81dH%(HD$1@u(1IHt$dH34%(u+HXDHD$`$L$8HD$HD$ HD$"ft ~&t_tu1AT1USHH Hl$dH%(HD$1HV~GLd$ *D$ t t uEHH%~H|$LyȸHL$dH3 %(uH []A\fT@V1tHxHf.;8HfSHHGH=GY11Tx1[fD11HHC[@f.x HSH?xH{[7?xHuHH hZH5ZH= Z?U1 SHH?xH+1H[]øfAWAVAUATUHSH(dH%(HD$1IʼnA}$t#HL$dH3 %(H([]A\A]A^A_H$HLdD$H=*1}/HUHHHHz/tHtPL|$H5 OL-;/H &YH5XH=XD12H}L/H)}HIL|$HL~A/A~/I^uIFHHx/tI9Lt$LH)H=~a/HHHtzH)H=HLME/u8}/H]uHUfHHz/tI9L|$v;HLt,A]LlA]AE$ |$uLD$ 3D$ H WH5?WH=WFH WH5 WH=WW'H qWH5WH=W}H RWH5VH=W~fATUSHdHx\Hu4H|tDD HHEt De[]A\fH1ZHuH[]A\ f.fAVAUATUHSHH0dH%(HD$(1: AxmHHxHwKH dVIEHH1hHHL$(dH3 %(H0[]A\A]A^@HHu1HH=U OAxXL UH UA H11H)D҃- " D 1:*f.UHAWAVAUATISHH8HXHpdH%(HE1HHHHLHIHLHaHHPHHHGHHxH9H H$HDžHH)HD$7HPHPHX HHLxMLXHl1HDž0MH MM'M9MHM)MILBL9HwQHL9IBH=L;X@Mt @MHLH(L80L8H(ILMHI< LLWH0H9p#AGH<%IWPH HFH 9L(:L 9tN8DNcIAfDA0EL_ADML@HH H9w1fDDA0EL_ADED@@DA0EL_ADEfD@DA0sOEL_ADED@wDL_MCLGZL_MCLGzL_MCLGfL_MCLGzDGAEL_ADGA@fL_MCIMXL_A(xDA0EL_ADMMMDL@fDA0s7EL_ADMMMDL@hfDf.L_MCLGfL_MCLG7L_MCLGrAWHF E1AAVIAUIATIUSHXHFHHD$ HBHHD$HD$HBHD$HNHD$(H6@@%IT$t=IA<$@uHHFL$HD$MNIF1HX[]A\A]A^A_fDHLI}LL$HHH9|$LD$@L$8DT$0'HIIUDT$0L$8LD$@LL$HH9T$}M]LA9HI9LI}LL$8HH9|$LD$0蠠HHIULD$0LL$8ZH9T$IMH6]Ht$(HHuPHH>L|$(HD$(HOLL$8HLD$0EA I}IEH9w HPHIUIEI}H9vHHHuLA$A$LH軞HIDT$0L$8LD$@LL$HXIUHt$LLL$HLD$@L$8DT$0HԝLL$HLD$@IËL$8DT$0@1VIHt$ HLL$8LD$0HHPH茝LL$8LD$0HHHHLD$0LL$8IUHt$HLL$8LD$0H=LL$8LD$0H0A^AQADA7H菝HHLD$0LL$8t9IUHt$HLL$8LD$0H辜LL$8LD$0HHH|$f.AWAAVIAUIATL%s UH-s SL)1HH}HtLLDAHH9uH[]A\A]A^A_Ðf.f.@H1Ht H1*1HHcreating directory %scannot stat %sfork system call failedcannot run %swaiting for stripcannot unlink %scannot set time stamps for %scannot change ownership of %s<> %s online help: <%s> GNU coreutilsen_/usr/share/localeSIMPLE_BACKUP_SUFFIXfailed to access %starget %s is not a directoryDavid MacKenzieinstallbcCsDdg:m:o:pPt:TvS:Zbackup typemissing file operandextra operand %sinvalid mode %sinvalid user %sinvalid group %scannot create directory %sbackupcomparegroupmodeno-target-directoryownerpreserve-timestampspreserve-contextstrip-programsuffixverbosehelpversionstrip process terminated abnormallycannot change permissions of %swarning: %s: failed to change context to %sTry '%s --help' for more information. Usage: %s [OPTION]... [-T] SOURCE DEST or: %s [OPTION]... SOURCE... DIRECTORY or: %s [OPTION]... -t DIRECTORY SOURCE... or: %s [OPTION]... -d DIRECTORY... This install program copies files (often just compiled) into destination locations you choose. If you want to download and install a ready-to-use package on a GNU/Linux system, you should instead be using a package manager like yum(1) or apt-get(1). In the first three forms, copy SOURCE to DEST or multiple SOURCE(s) to the existing DIRECTORY, while setting permission modes and owner/group. In the 4th form, create all components of the given DIRECTORY(ies). Mandatory arguments to long options are mandatory for short options too. --backup[=CONTROL] make a backup of each existing destination file -b like --backup but does not accept an argument -c (ignored) -C, --compare compare each pair of source and destination files, and in some cases, do not modify the destination at all -d, --directory treat all arguments as directory names; create all components of the specified directories -D create all leading components of DEST except the last, then copy SOURCE to DEST -g, --group=GROUP set group ownership, instead of process' current group -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x -o, --owner=OWNER set ownership (super-user only) -p, --preserve-timestamps apply access/modification times of SOURCE files to corresponding destination files -s, --strip strip symbol tables --strip-program=PROGRAM program used to strip binaries -S, --suffix=SUFFIX override the usual backup suffix -t, --target-directory=DIRECTORY copy all SOURCE arguments into DIRECTORY -T, --no-target-directory treat DEST as a normal file -v, --verbose print the name of each directory as it is created -P, --preserve-context preserve SELinux security context (-P deprecated) -Z set SELinux security context of destination file to default type --context[=CTX] like -Z, or if CTX is specified then set the SELinux or SMACK security context to CTX --help display this help and exit --version output version information and exit The backup suffix is '~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX. The version control method may be selected via the --backup option or through the VERSION_CONTROL environment variable. Here are the values: none, off never make backups (even if --backup is given) numbered, t make numbered backups existing, nil numbered if numbered backups exist, simple otherwise simple, never always make simple backups http://www.gnu.org/software/coreutils/Report %s translation bugs to For complete documentation, run: info coreutils '%s invocation' multiple target directories specified%s: warning: option '-P' is deprecated, please use '--preserve-context' instead WARNING: ignoring --preserve-context; this kernel is not SELinux-enabled%s: cannot force target context and preserve it warning: ignoring --context; it requires an SELinux-enabled kernelthe strip option may not be used when installing a directorytarget directory not allowed when installing a directorycannot set target context and preserve itfailed to set default file creation context to %smissing destination file operand after %scannot combine --target-directory (-t) and --no-target-directory (-T)WARNING: ignoring --strip-program option as -s option was not specifiedoptions --compare (-C) and --preserve-timestamps are mutually exclusiveoptions --compare (-C) and --strip are mutually exclusivethe --compare (-C) option is ignored when you specify a mode with non-permission bits: failed to get security context of %sfailed to set default file creation context for %scannot create hard link %s to %s%s: try to overwrite %s, overriding mode %04lo (%s)? failed to restore the default file creation contextfailed to set the security context of %sfailed to preserve ownership for %swarning: source file %s specified more than oncecannot overwrite non-directory %s with directory %swill not overwrite just-created %s with %scannot overwrite directory %s with non-directorycannot move directory onto non-directory: %s -> %sbacking up %s would destroy source; %s not movedbacking up %s would destroy source; %s not copiedwill not copy %s through just-created symlink %scannot copy a directory, %s, into itself, %swill not create hard link %s to directory %scannot move %s to a subdirectory of itself, %sinter-device move failed: %s to %s; unable to remove targetcannot create symbolic link %s to %sskipping file %s, as it was replaced while being copiednot writing through dangling symlink %s%s: failed to get extents infocannot create symbolic link %scannot copy cyclic symbolic link %s%s: can make relative symbolic links only in current directory((unsigned int) (co->backup_type) <= numbered_backups)((co->sparse_mode) == SPARSE_NEVER || (co->sparse_mode) == SPARSE_AUTO || (co->sparse_mode) == SPARSE_ALWAYS)((co->reflink_mode) == REFLINK_NEVER || (co->reflink_mode) == REFLINK_AUTO || (co->reflink_mode) == REFLINK_ALWAYS)!(co->hard_link && co->symbolic_link)! (co->reflink_mode == REFLINK_ALWAYS && co->sparse_mode != SPARSE_AUTO)error reading %scannot lseek %serror writing %s%s -> %s (backup: %s)cannot remove %sremoved %s %s: overwrite %s? security.selinuxclearing permissions for %somitting directory %s%s and %s are the same filecannot backup %scannot move %s to %ssetting permissions for %scannot access %scannot open %s for readingcannot fstat %scannot create regular file %sfailed to clone %s from %s%s: write failedfailed to extend %spreserving times for %spreserving permissions for %sfailed to close %scannot create fifo %scannot create special file %scannot read symbolic link %s%s has unknown file typecannot un-backup %s%s -> %s (unbackup) src/copy.cco != ((void *)0)valid_optionssrc/extent-scan.cfm_extents[i].fe_logical <= ((off_t) (! (! ((off_t) 0 < (off_t) -1)) ? (off_t) -1 : ((((off_t) 1 << (sizeof (off_t) * 8 - 2)) - 1) * 2 + 1))) - fm_extents[i].fe_lengthextent_scan_readerror canonicalizing %sfts_read failedfts_close failed8.22$VERSION_CONTROLnoneoffsimpleneverexistingnilnumbered~error closing file%s: %swrite error# entries: %lu # buckets: %lu max bucket length: %lu # buckets used: %lu (%.2f%%) ?L??=fff?̌??__Y@cannot change owner and permissions of %s#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#6#4$,$$$6#6#$$A NULL argv[0] was passed through an exec system call. /.libs/lt-’"e‘`literalshellshell-alwaysc-maybeescapeclocalep,22@222333/000000//////t/000000000000000000.....-.0...----------------....-0--------------------------.l0-.-.--------------------------....lib/savewd.cwd->val.child == 0(*__errno_location ()) == 4wd->val.child < 0EDEEEEFFGhFFGGGGGsavewd_finishsavewd_restoresavewd_savesavewd_chdirlib/utimens.ctimespecvalidate_timespecunable to display error message%s (%s) %s %s %s (C)Written by %s. Written by %s and %s. Written by %s, %s, and %s. Report bugs to: %s bug-coreutils@gnu.org%s home page: <%s> License GPLv3+: GNU GPL version 3 or later . This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by %s, %s, %s, and %s. Written by %s, %s, %s, %s, and %s. Written by %s, %s, %s, %s, %s, and %s. Written by %s, %s, %s, %s, %s, %s, and %s. Written by %s, %s, %s, %s, %s, %s, %s, and %s. Written by %s, %s, %s, %s, %s, %s, %s, %s, and %s. Written by %s, %s, %s, %s, %s, %s, %s, %s, %s, and others. General help using GNU software: YYY@ZZZ0[[XYCopyright %s %d Free Software Foundation, Inc.memory exhaustedlib/xfts.c(*__errno_location ()) != 22xfts_openlib/xstrtol.c0 <= strtol_base && strtol_base <= 36YdbbdbsdbbbcbcbbcbbbQcbbbbcbbbbbbbbbbbbbsdbbbcbcbbbbbbQcbbbxstrtoul.. @`unlabeledinvalid argument %s for %sambiguous argument %s for %sValid arguments are: - %s, %slib/cycle-check.cstate->magic == 9827862cycle_check/usr/lib64ASCIICHARSETALIASDIR%50s %50sunable to record current working directoryfailed to return to initial working directorylib/chdir-long.c! close_fail0 < len4096 <= len*dir != '/'dir <= dir_endslash - dir < 4096cdb_freechdir_long/proc/self/fd../fd/proc/self/fd/%d/%sl,Lįįįį\ԵįįįLL(NULL) ````h``````(NULL)\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\T\T\\\\\\\\\;i< sd t dd ă|  $ t d<   $ 4 $ 4\ ԓ ĕ Ė< d d   T t  4 d$4D$T4LlT4t,DddLdT4L|T,tL|T 4,L$Td \$4,DDtdtTLddt|4D<\dD,T ,D lT   $<TTtt$T|$Tldt44+,$- D- d-4 -L -d . . t/!/4!0d!40|!D0!T0!d0!0!$1<"41T"D1l"1"2"2"$2"2,#2D#2\#3t#$3#43#D3#T3#5$$$6\$6$7$494%9d%9|%9%9%9%<&>L&>l&?&?&4@ 'D@$'T@<'H'H'I'I (N\(Nt(Q(Q(Q)tV)V)$W)W*dX<*XT*Xt*X*X*4Y*dY*Y*$Z+DZ4+dZT+Z|+Z+Z+D[+t[+[ ,`\,da,b,b,d,-DdL-tdd-d-e-e-$e-4e-de .f\.g.Tg.g.g/ThD/tj/j/dk/k/ll0o0o04y,1$}1~1,24D22$2D2d3<3ċ3$ 4$T4|44đ4ԑ4T55546Tt6d6ė6ԗ 7TT7dl77d77ę7ԙ7 8T488t88Ԡ9D$9t<9t9d9Ģ999D :<:d:::D$;T;Tt;;;t$<<<zRx `y*zRx $` FJ w?;*3$"DyQD0I\@z4Ai|`z4hzGALG0S AAG TAALzBBB B(D0D8JH 8A0A(B BBBD $ BBA C(D04DxiBBB B(A0C8J,|`AAJ AAA @8$0FOR G S4XBAA D@  AABD 4<ЇBLA | ADH A AGA dt8BBE B(D0D8D` 8F0A(B BBBE P 8A0A(B BBBF $AG0 AF $AG AB $D(AG AA 4lЋBAI  ABA AABLHuBLJ D(I0z (A BBDH n (A BBBK <xBBA D(G`z (A ABBH 4X=AL C f4TxBAD _ ABG JABLtT8+XRH+XRXA\ C ؏$Abd$BBB E(D0C8GP' 8A0A(B BBDD } 8A0A(B BBBI p+QY,7AC BEEM H zD@ D p h,pAP$LpjAD0^ AA tUD0E A <yBED I(D0P (A ABBB 8;Y\ A X  P)L$hBBE E(A0K8G   8A0A(B BBBH <tBBA A(J} (A ABBE <8BBD D(D` (A ABBF LBBE B(E0D8F` 8A0A(B BBBA 4DBDD K ABH hAB,|pPBAD EAB|BPL E(A0A8IPc 8A0A(B BBBE R 8D0A(B BBBA O8C0A(B BBBL, 0BEB B(A0A8G 8A0A(B BBBA | FTq -Dd mL hjBBB L(A0A8G 8A0A(B BBBA  ,, AAD  AAJ \ Pt H, @AAD } AAA L BBB A(A0^ (A BBBC { (A BBBF  DN A ,, RACG | DAA <\ PtBBD A(D0E (A ABBH  i +AZ E J  "FN nD` E L, PBBA D(D0M (D ABBM D (A ABBA | VD0L A   x pDN A L pBEE B(D0D8DP 8A0A(B BBBJ L< vBBA A(G0{ (D ABBG O (D ABBA L PvBBA A(G0{ (D ABBG O (D ABBA    $"A[ A dDBEE D(D0Y (A BBEI ` (A BDED k (A BBBF dFBEE B(D0A8D@ 8F0A(B BBBF q8C0A(B BBB,D\tI X<hBBB A(D0 (A BBBV 48SBDD t ADE DAE`BDq A F A 4<dADG K AAA GAAtdL nBEB B(A0A8D@K 8D0A(B BBBA @4h d pBQE E(D0D8D@  8A0A(B BBBH T 8C0A(B BBBH ,tBAD AB,(BAD t DBE 4BAA Gp  AABA < tBBA D(D@X (A ABBE L$dQAG { AD 4BFA G0K  AABA $'ADG RDA %3^T4AOLTBEE E(D0C8G` 8A0A(B BBBD LXeBEE E(A0D8J= 8A0A(B BBBI <x|BAA  ABK 7 ABF $4AOk AA 4\ ~BKA A(Q  ABBK hD{ A |BBE E(D0C8D@n 8F0A(B EBBG n 8F0A(B EBBH g 8C0A(B BBBE 4XdL`BBB G(D0C8D@N 8A0A(B BBBH c 8F0A(B EBBK DPz A <hBGG F(D0Q (D ABBD L8 BEE E(A0A8J 8A0A(B BBBG Ld BEB B(A0A8Gm 8D0A(B BBBB , 2BAD gAB  ( 6,P DX 4Kc A Ddx BLE E(A0A8G`S8A0A(B BBBL BIE E(D0A8G8A0A(B BBBP ,HBND jALD\ t  4WBDC D`@  AABA <ZBED C(Dp| (A ABBA  44LBLD D`  AABA H@ 8 <0BED C(Dp (A ABBA   $<T l   LxiBHE E(D0N8LK 8A0A(B BBBI 4^BED A(G0A(D ABB4<^BED A(G0A(D ABBLtVBEE B(A0A8I^ 8A0A(B BBBG LPBBB B(A0D8D` 8A0A(B BBBA ,JBAA ] DBI DDI\ DIt( L(BEE E(A0D8D@k 8D0A(B BBBF 4hzBDA D0g  AABJ ,An A LLYBGE B(D0A8D` 8A0A(B BBBE  4?BBA A(F0j(C ABB   LBBB B(A0A8J. 8A0A(B BBBD Dl ADD0s AAB \ AAB T ACH !DM G ! L!BBB B(A0D8I 8A0A(B BBBE <P&4TH&>BAA Jl  AABB LP(BEH G(D0s (A BBBL [ (A BBBE ((BBB B(D0D8G 8A0A(B BBBE  8A0A(B BBBB b 8G0A(B BBBV ^ 8G0A(M BBBO b 8P0A(B BBBU  ,  ,Dp} A  -G A  -A}! .8\[4!H.AN A T!H. [l!P.$!H.8DS I M A !`.#^!x.b]!.MH!/AQ"/DN A $4"/(AGG IGA\"/AP|"/8K"8/ODT H "h/."//AU J L"/dBBE B(A0A8D`| 8A0A(B BBBI L<#3LBBB B(D0D8D` 8A0A(B BBBD #4D b J $#@5AK0y AA 4#5VBAC Dp  AABD  $6@DR J [,$6+,D$7eAG N DF CAt$H7$P7 $H7 $@7 $87#L$P7BBD D(G0 (A ABBD U (D ABBA 4<% 8BEK D(D0j(D ABB$t%x89AAG mAA%89Ah G 4%8`ACG e AAF [ AAA ,%8RACG i CAH L$&9BBD E(G0 (A ABBD P (A ABFF $t&:sAo H ] K R&0;cGp I b&;`KC B l&;BBD A(G@w (A ABBC a (A ABBI D (F ABBA D(C ABBLL'0D0U G L'>W BBB B(A0A8J 8A0A(B BBBH | (HBBB B(A0A8F` 8D0A(B BBBC a 8A0A(B BBBE O 8C0A(B BBBE ,(pKqBAD  ABB L(L]BBB B(D0A8GD 8A0A(B BBBF  )T)TTt$)T}BHB D(A0 (A BBBH Z (A BBBG A (E BBBD N (A BBBC )UbDO E )@VAN)@VAN)@VAN|*@V?BBB B(A0A8D`T 8A0A(B BBBD - 8A0A(B BBBI 8A0A(B BBBL*X\BBB B(A0A8I  8A0A(B BBBA D*ZBBE D(C0I 0A(A BBBG $4+[~AL I AA <\+ \BHA A(G (A ABBH +\+\ d+\-BEB B(D0D8D` 8A0A(B BBBG T 8D0A(B BBBA ,4,]sBJD v JBN \d,]BGB E(I0K8D@ 8A0A(B BBBA D8F0A(B BBBL,^mBEE E(G0G8M@N 8A0A(B BBBA <-^NBBB A(A0{(A EBBLT-^BEE B(D0D8J 8A0A(B BBBH ,-`WALF z AAA -`D-`vBAD p ABF W ABF RAB4.`L.`s$d.habAL0N AA .a0.a!.a.a6$.b;Ak D E A L/b5BGB B(A0A8G 8A0A(B BBBA Ld/fBEE E(D0A8I 8A0A(B BBBG /g0A/g0A/gnD`~ F 0h(400hBCA G@|  AABC T0hGWMLSt0hRAp G Y0i0iAS0i8JMB,00i7AHG ] AAA L1@iBBB B(A0D8D`H 8A0A(B BBBA 4l1kxBAA F ABC `AB1lD1lFBBB A(D0G` 0A(A BBBE ,2mAC HD D 42xuD0G E T2؈ILl2V BOE E(D0A8D 8A0A(B BBBG D2 eBEE E(H0H8M@l8A0A(B BBB3H3@G@F@pAbwACAZAdAgAmATAoApAAsəAיASAtޙAvA~A}AAA A&A/A3AǙA?AGAMA˹AZAbAwAiA4@4@.@8 -@ lAh bp bo@@@ f b@@ o@ooV@ b-@-@-@-@-@.@.@&.@6.@F.@V.@f.@v.@.@.@.@.@.@.@.@.@/@/@&/@6/@F/@V/@f/@v/@/@/@/@/@/@/@/@/@0@0@&0@60@F0@V0@f0@v0@0@0@0@0@0@0@0@0@1@1@&1@61@F1@V1@f1@v1@1@1@1@1@1@1@1@1@2@2@&2@62@F2@V2@f2@v2@2@2@2@2@2@2@2@2@3@3@&3@63@F3@V3@f3@v3@3@3@3@3@3@3@3@3@4@4@&4@64@F4@V4@f4@v4@4@4@4@4@4@4@4@4@5@5@&5@65@F5@V5@f5@v5@5@5@5@5@5@5@5@5@6@6@&6@66@F6@V6@f6@v6@6@6@6@6@6@6@6@6@7@7@&7@67@F7@V7@f7@v7@7@7@7@AAE"ֺ?7xҴYDśz]M \q;HheWD+䫨TX>;,9z%N˲l; !-!#1غI]*6 ۆj9đRKV7TaߴLpk)NH}ZdiD{ٲ*O^Xf!y+i -_&sy#)?WS}vTG6z&mXS+fa?km|> `Ƣ_nU,ʮۯ+HJvbMZ@<2Vn!Yn40kI Ȓ3,~_5 ϻcK27!-Y z:H۴X׃?AwU*)}Zo1>l\t񧳝ŤdW>EL1Iq&+T }7hdow{Mf)L::y= g0 hz*V-7C/7{ő0gkv2~/ oɝ9e;~,b)\$ۋ1Q>b+K} hIEGWW!Jr0(|{n6i^~^#l`xpfp"{W)Ӛgfmu-խ]bG7¶Jby\ww.Z0?Y0 b? F8/ Na+lܗ,#yG+nS~ޢۆ!X]fO;kbu>C7mLQ/ԗ"l!DQ.% bA[4UO !. %r&Q.=M2q4ͻ95& =o;Q+ Q{=xe5M ټFB_d;ylP ! Nz|5"(t¯lįa޸BJ'nVXrhew6xڼEvbv{mi >BIQ0{ˌ-Fu0Iyf}B }sDU%wjx ɶ@ F0dI6}w'lVM5݊JWBHL =DQY!Va~l~fp͍_ gyc*<,(\T &|n ]q7r 4(Q+2\wD% 9gkI׳;>s9p !Fؿ^ղ{JB.r(ƋHC{ Ђ >_"rQcFnT[!*XXЉ { 9ɦ yF֌iN_mbB?nKT9nk О%tWGS)1HpbscT3a&ȶ=t Sqd殅fb #m#nvk3<4a7Dtz'MCaZ7un^,H r!Kշ]OA/n:Q" C舋hthVxKe >S&kGlHSljm;ܵ̆GW[B|9I\oE 8eHynOz~V:rc @@*DFr&KF֘hA &2Q l(c |?JHY~|RE} s0w'h;e. 7*4",`m1~f?kBFf|# yɕUg&ʠ=ӆk%w3OJ62ۀaWgW26qi##lqrP #z+:HpgNRgd&}L,D7d~z~G̍G1vXw?mԔ$xx Z&LlLt*a/ҡEX9OgJ]8=Ta O\jJQj`鸈*&ʳ7m}E_*pwnW@i,w v-=G:Tt -) 6on5긹 z 79[6=5[*NkM$ͰW+GdNþ5NB9\`>XC[^O54a!ǜ !`M#S41B \;pTSY' R0`)[P*E1P+P~}fȳKb>Պ0whXp* }W%>G|ڀ]Gl^Z,vXn=Z%LI fQ'Dh=_uɱ*܉*T`u8Q/ɤ수EkU؂8F7__]]Q 䢽òf;R7!.uczkMWݸ@r*(o{ {xATFKXxLB[)[*mp[OvȘ 8dwPutfw\4ϛ, Б e7/`)/Ɵawt]M '~r^ @YfpV"h (Շ-D;G~2Gim|{C?" #= Aj썼 a~*BVȝo>v`߆@8oW\ibwL5t*,oC@+`im5ŵE>nLx0fW8S 7<3_dWb=(}4\Tȧ`dy/}=}n˜(y$7ЫryH eMy^(GUJ"&F~}ؼWQ0 XIơ:%--B% X⨥2ŤhȢ$rM-o#];%Ա\6TW*^'$  WQA9{mF/Lp-V4(s w ?J4fmzhʑNEL,ڇ{$ >%8XjDyΌJڒu>PUxw{=V|vjrD 9Y(Yq㾱gYZ.shstrtab.interp.note.ABI-tag.note.gnu.build-id.gnu.hash.dynsym.dynstr.gnu.version.gnu.version_r.rela.dyn.rela.plt.init.text.fini.rodata.eh_frame_hdr.eh_frame.init_array.fini_array.jcr.data.rel.ro.dynamic.got.got.plt.data.bss.gnu_debuglink.gnu_debugdata 8@8T@T !t@t$4o@`> @F@fNoV@Vj[o@j@tB@~-@-y-@- 7@7_lAl AL, AAd3h bh p bp x bx  b    b bPb b  b&  %index.html000064400000252234147561465640006573 0ustar00 Installing Python Modules — Python 2.7.5 documentation

Navigation

Installing Python Modules

Author:Greg Ward

Abstract

This document describes the Python Distribution Utilities (“Distutils”) from the end-user’s point-of-view, describing how to extend the capabilities of a standard Python installation by building and installing third-party Python modules and extensions.

Introduction

Although Python’s extensive standard library covers many programming needs, there often comes a time when you need to add some new functionality to your Python installation in the form of third-party modules. This might be necessary to support your own programming, or to support an application that you want to use and that happens to be written in Python.

In the past, there has been little support for adding third-party modules to an existing Python installation. With the introduction of the Python Distribution Utilities (Distutils for short) in Python 2.0, this changed.

This document is aimed primarily at the people who need to install third-party Python modules: end-users and system administrators who just need to get some Python application running, and existing Python programmers who want to add some new goodies to their toolbox. You don’t need to know Python to read this document; there will be some brief forays into using Python’s interactive mode to explore your installation, but that’s it. If you’re looking for information on how to distribute your own Python modules so that others may use them, see the Distributing Python Modules manual.

Best case: trivial installation

In the best case, someone will have prepared a special version of the module distribution you want to install that is targeted specifically at your platform and is installed just like any other software on your platform. For example, the module developer might make an executable installer available for Windows users, an RPM package for users of RPM-based Linux systems (Red Hat, SuSE, Mandrake, and many others), a Debian package for users of Debian-based Linux systems, and so forth.

In that case, you would download the installer appropriate to your platform and do the obvious thing with it: run it if it’s an executable installer, rpm --install it if it’s an RPM, etc. You don’t need to run Python or a setup script, you don’t need to compile anything—you might not even need to read any instructions (although it’s always a good idea to do so anyway).

Of course, things will not always be that easy. You might be interested in a module distribution that doesn’t have an easy-to-use installer for your platform. In that case, you’ll have to start with the source distribution released by the module’s author/maintainer. Installing from a source distribution is not too hard, as long as the modules are packaged in the standard way. The bulk of this document is about building and installing modules from standard source distributions.

The new standard: Distutils

If you download a module source distribution, you can tell pretty quickly if it was packaged and distributed in the standard way, i.e. using the Distutils. First, the distribution’s name and version number will be featured prominently in the name of the downloaded archive, e.g. foo-1.0.tar.gz or widget-0.9.7.zip. Next, the archive will unpack into a similarly-named directory: foo-1.0 or widget-0.9.7. Additionally, the distribution will contain a setup script setup.py, and a file named README.txt or possibly just README, which should explain that building and installing the module distribution is a simple matter of running one command from a terminal:

python setup.py install

For Windows, this command should be run from a command prompt window (Start ‣ Accessories):

setup.py install

If all these things are true, then you already know how to build and install the modules you’ve just downloaded: Run the command above. Unless you need to install things in a non-standard way or customize the build process, you don’t really need this manual. Or rather, the above command is everything you need to get out of this manual.

Standard Build and Install

As described in section The new standard: Distutils, building and installing a module distribution using the Distutils is usually one simple command to run from a terminal:

python setup.py install

Platform variations

You should always run the setup command from the distribution root directory, i.e. the top-level subdirectory that the module source distribution unpacks into. For example, if you’ve just downloaded a module source distribution foo-1.0.tar.gz onto a Unix system, the normal thing to do is:

gunzip -c foo-1.0.tar.gz | tar xf -    # unpacks into directory foo-1.0
cd foo-1.0
python setup.py install

On Windows, you’d probably download foo-1.0.zip. If you downloaded the archive file to C:\Temp, then it would unpack into C:\Temp\foo-1.0; you can use either a archive manipulator with a graphical user interface (such as WinZip) or a command-line tool (such as unzip or pkunzip) to unpack the archive. Then, open a command prompt window and run:

cd c:\Temp\foo-1.0
python setup.py install

Splitting the job up

Running setup.py install builds and installs all modules in one run. If you prefer to work incrementally—especially useful if you want to customize the build process, or if things are going wrong—you can use the setup script to do one thing at a time. This is particularly helpful when the build and install will be done by different users—for example, you might want to build a module distribution and hand it off to a system administrator for installation (or do it yourself, with super-user privileges).

For example, you can build everything in one step, and then install everything in a second step, by invoking the setup script twice:

python setup.py build
python setup.py install

If you do this, you will notice that running the install command first runs the build command, which—in this case—quickly notices that it has nothing to do, since everything in the build directory is up-to-date.

You may not need this ability to break things down often if all you do is install modules downloaded off the ‘net, but it’s very handy for more advanced tasks. If you get into distributing your own Python modules and extensions, you’ll run lots of individual Distutils commands on their own.

How building works

As implied above, the build command is responsible for putting the files to install into a build directory. By default, this is build under the distribution root; if you’re excessively concerned with speed, or want to keep the source tree pristine, you can change the build directory with the --build-base option. For example:

python setup.py build --build-base=/path/to/pybuild/foo-1.0

(Or you could do this permanently with a directive in your system or personal Distutils configuration file; see section Distutils Configuration Files.) Normally, this isn’t necessary.

The default layout for the build tree is as follows:

--- build/ --- lib/
or
--- build/ --- lib.<plat>/
               temp.<plat>/

where <plat> expands to a brief description of the current OS/hardware platform and Python version. The first form, with just a lib directory, is used for “pure module distributions”—that is, module distributions that include only pure Python modules. If a module distribution contains any extensions (modules written in C/C++), then the second form, with two <plat> directories, is used. In that case, the temp.plat directory holds temporary files generated by the compile/link process that don’t actually get installed. In either case, the lib (or lib.plat) directory contains all Python modules (pure Python and extensions) that will be installed.

In the future, more directories will be added to handle Python scripts, documentation, binary executables, and whatever else is needed to handle the job of installing Python modules and applications.

How installation works

After the build command runs (whether you run it explicitly, or the install command does it for you), the work of the install command is relatively simple: all it has to do is copy everything under build/lib (or build/lib.plat) to your chosen installation directory.

If you don’t choose an installation directory—i.e., if you just run setup.py install—then the install command installs to the standard location for third-party Python modules. This location varies by platform and by how you built/installed Python itself. On Unix (and Mac OS X, which is also Unix-based), it also depends on whether the module distribution being installed is pure Python or contains extensions (“non-pure”):

Platform Standard installation location Default value Notes
Unix (pure) prefix/lib/pythonX.Y/site-packages /usr/local/lib/pythonX.Y/site-packages (1)
Unix (non-pure) exec-prefix/lib/pythonX.Y/site-packages /usr/local/lib/pythonX.Y/site-packages (1)
Windows prefix\Lib\site-packages C:\PythonXY\Lib\site-packages (2)

Notes:

  1. Most Linux distributions include Python as a standard part of the system, so prefix and exec-prefix are usually both /usr on Linux. If you build Python yourself on Linux (or any Unix-like system), the default prefix and exec-prefix are /usr/local.
  2. The default installation directory on Windows was C:\Program Files\Python under Python 1.6a1, 1.5.2, and earlier.

prefix and exec-prefix stand for the directories that Python is installed to, and where it finds its libraries at run-time. They are always the same under Windows, and very often the same under Unix and Mac OS X. You can find out what your Python installation uses for prefix and exec-prefix by running Python in interactive mode and typing a few simple commands. Under Unix, just type python at the shell prompt. Under Windows, choose Start ‣ Programs ‣ Python X.Y ‣ Python (command line). Once the interpreter is started, you type Python code at the prompt. For example, on my Linux system, I type the three Python statements shown below, and get the output as shown, to find out my prefix and exec-prefix:

Python 2.4 (#26, Aug  7 2004, 17:19:02)
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.prefix
'/usr'
>>> sys.exec_prefix
'/usr'

A few other placeholders are used in this document: X.Y stands for the version of Python, for example 2.7; distname will be replaced by the name of the module distribution being installed. Dots and capitalization are important in the paths; for example, a value that uses python2.7 on UNIX will typically use Python27 on Windows.

If you don’t want to install modules to the standard location, or if you don’t have permission to write there, then you need to read about alternate installations in section Alternate Installation. If you want to customize your installation directories more heavily, see section Custom Installation on custom installations.

Alternate Installation

Often, it is necessary or desirable to install modules to a location other than the standard location for third-party Python modules. For example, on a Unix system you might not have permission to write to the standard third-party module directory. Or you might wish to try out a module before making it a standard part of your local Python installation. This is especially true when upgrading a distribution already present: you want to make sure your existing base of scripts still works with the new version before actually upgrading.

The Distutils install command is designed to make installing module distributions to an alternate location simple and painless. The basic idea is that you supply a base directory for the installation, and the install command picks a set of directories (called an installation scheme) under this base directory in which to install files. The details differ across platforms, so read whichever of the following sections applies to you.

Note that the various alternate installation schemes are mutually exclusive: you can pass --user, or --home, or --prefix and --exec-prefix, or --install-base and --install-platbase, but you can’t mix from these groups.

Alternate installation: the user scheme

This scheme is designed to be the most convenient solution for users that don’t have write permission to the global site-packages directory or don’t want to install into it. It is enabled with a simple option:

python setup.py install --user

Files will be installed into subdirectories of site.USER_BASE (written as userbase hereafter). This scheme installs pure Python modules and extension modules in the same location (also known as site.USER_SITE). Here are the values for UNIX, including Mac OS X:

Type of file Installation directory
modules userbase/lib/pythonX.Y/site-packages
scripts userbase/bin
data userbase
C headers userbase/include/pythonX.Y/distname

And here are the values used on Windows:

Type of file Installation directory
modules userbase\PythonXY\site-packages
scripts userbase\Scripts
data userbase
C headers userbase\PythonXY\Include\distname

The advantage of using this scheme compared to the other ones described below is that the user site-packages directory is under normal conditions always included in sys.path (see site for more information), which means that there is no additional step to perform after running the setup.py script to finalize the installation.

The build_ext command also has a --user option to add userbase/include to the compiler search path for header files and userbase/lib to the compiler search path for libraries as well as to the runtime search path for shared C libraries (rpath).

Alternate installation: the home scheme

The idea behind the “home scheme” is that you build and maintain a personal stash of Python modules. This scheme’s name is derived from the idea of a “home” directory on Unix, since it’s not unusual for a Unix user to make their home directory have a layout similar to /usr/ or /usr/local/. This scheme can be used by anyone, regardless of the operating system they are installing for.

Installing a new module distribution is as simple as

python setup.py install --home=<dir>

where you can supply any directory you like for the --home option. On Unix, lazy typists can just type a tilde (~); the install command will expand this to your home directory:

python setup.py install --home=~

To make Python find the distributions installed with this scheme, you may have to modify Python’s search path or edit sitecustomize (see site) to call site.addsitedir() or edit sys.path.

The --home option defines the installation base directory. Files are installed to the following directories under the installation base as follows:

Type of file Installation directory
modules home/lib/python
scripts home/bin
data home
C headers home/include/python/distname

(Mentally replace slashes with backslashes if you’re on Windows.)

Changed in version 2.4: The --home option used to be supported only on Unix.

Alternate installation: Unix (the prefix scheme)

The “prefix scheme” is useful when you wish to use one Python installation to perform the build/install (i.e., to run the setup script), but install modules into the third-party module directory of a different Python installation (or something that looks like a different Python installation). If this sounds a trifle unusual, it is—that’s why the user and home schemes come before. However, there are at least two known cases where the prefix scheme will be useful.

First, consider that many Linux distributions put Python in /usr, rather than the more traditional /usr/local. This is entirely appropriate, since in those cases Python is part of “the system” rather than a local add-on. However, if you are installing Python modules from source, you probably want them to go in /usr/local/lib/python2.X rather than /usr/lib/python2.X. This can be done with

/usr/bin/python setup.py install --prefix=/usr/local

Another possibility is a network filesystem where the name used to write to a remote directory is different from the name used to read it: for example, the Python interpreter accessed as /usr/local/bin/python might search for modules in /usr/local/lib/python2.X, but those modules would have to be installed to, say, /mnt/@server/export/lib/python2.X. This could be done with

/usr/local/bin/python setup.py install --prefix=/mnt/@server/export

In either case, the --prefix option defines the installation base, and the --exec-prefix option defines the platform-specific installation base, which is used for platform-specific files. (Currently, this just means non-pure module distributions, but could be expanded to C libraries, binary executables, etc.) If --exec-prefix is not supplied, it defaults to --prefix. Files are installed as follows:

Type of file Installation directory
Python modules prefix/lib/pythonX.Y/site-packages
extension modules exec-prefix/lib/pythonX.Y/site-packages
scripts prefix/bin
data prefix
C headers prefix/include/pythonX.Y/distname

There is no requirement that --prefix or --exec-prefix actually point to an alternate Python installation; if the directories listed above do not already exist, they are created at installation time.

Incidentally, the real reason the prefix scheme is important is simply that a standard Unix installation uses the prefix scheme, but with --prefix and --exec-prefix supplied by Python itself as sys.prefix and sys.exec_prefix. Thus, you might think you’ll never use the prefix scheme, but every time you run python setup.py install without any other options, you’re using it.

Note that installing extensions to an alternate Python installation has no effect on how those extensions are built: in particular, the Python header files (Python.h and friends) installed with the Python interpreter used to run the setup script will be used in compiling extensions. It is your responsibility to ensure that the interpreter used to run extensions installed in this way is compatible with the interpreter used to build them. The best way to do this is to ensure that the two interpreters are the same version of Python (possibly different builds, or possibly copies of the same build). (Of course, if your --prefix and --exec-prefix don’t even point to an alternate Python installation, this is immaterial.)

Alternate installation: Windows (the prefix scheme)

Windows has no concept of a user’s home directory, and since the standard Python installation under Windows is simpler than under Unix, the --prefix option has traditionally been used to install additional packages in separate locations on Windows.

python setup.py install --prefix="\Temp\Python"

to install modules to the \Temp\Python directory on the current drive.

The installation base is defined by the --prefix option; the --exec-prefix option is not supported under Windows, which means that pure Python modules and extension modules are installed into the same location. Files are installed as follows:

Type of file Installation directory
modules prefix\Lib\site-packages
scripts prefix\Scripts
data prefix
C headers prefix\Include\distname

Custom Installation

Sometimes, the alternate installation schemes described in section Alternate Installation just don’t do what you want. You might want to tweak just one or two directories while keeping everything under the same base directory, or you might want to completely redefine the installation scheme. In either case, you’re creating a custom installation scheme.

To create a custom installation scheme, you start with one of the alternate schemes and override some of the installation directories used for the various types of files, using these options:

Type of file Override option
Python modules --install-purelib
extension modules --install-platlib
all modules --install-lib
scripts --install-scripts
data --install-data
C headers --install-headers

These override options can be relative, absolute, or explicitly defined in terms of one of the installation base directories. (There are two installation base directories, and they are normally the same— they only differ when you use the Unix “prefix scheme” and supply different --prefix and --exec-prefix options; using --install-lib will override values computed or given for --install-purelib and --install-platlib, and is recommended for schemes that don’t make a difference between Python and extension modules.)

For example, say you’re installing a module distribution to your home directory under Unix—but you want scripts to go in ~/scripts rather than ~/bin. As you might expect, you can override this directory with the --install-scripts option; in this case, it makes most sense to supply a relative path, which will be interpreted relative to the installation base directory (your home directory, in this case):

python setup.py install --home=~ --install-scripts=scripts

Another Unix example: suppose your Python installation was built and installed with a prefix of /usr/local/python, so under a standard installation scripts will wind up in /usr/local/python/bin. If you want them in /usr/local/bin instead, you would supply this absolute directory for the --install-scripts option:

python setup.py install --install-scripts=/usr/local/bin

(This performs an installation using the “prefix scheme,” where the prefix is whatever your Python interpreter was installed with— /usr/local/python in this case.)

If you maintain Python on Windows, you might want third-party modules to live in a subdirectory of prefix, rather than right in prefix itself. This is almost as easy as customizing the script installation directory —you just have to remember that there are two types of modules to worry about, Python and extension modules, which can conveniently be both controlled by one option:

python setup.py install --install-lib=Site

The specified installation directory is relative to prefix. Of course, you also have to ensure that this directory is in Python’s module search path, such as by putting a .pth file in a site directory (see site). See section Modifying Python’s Search Path to find out how to modify Python’s search path.

If you want to define an entire installation scheme, you just have to supply all of the installation directory options. The recommended way to do this is to supply relative paths; for example, if you want to maintain all Python module-related files under python in your home directory, and you want a separate directory for each platform that you use your home directory from, you might define the following installation scheme:

python setup.py install --home=~ \
                        --install-purelib=python/lib \
                        --install-platlib=python/lib.$PLAT \
                        --install-scripts=python/scripts
                        --install-data=python/data

or, equivalently,

python setup.py install --home=~/python \
                        --install-purelib=lib \
                        --install-platlib='lib.$PLAT' \
                        --install-scripts=scripts
                        --install-data=data

$PLAT is not (necessarily) an environment variable—it will be expanded by the Distutils as it parses your command line options, just as it does when parsing your configuration file(s).

Obviously, specifying the entire installation scheme every time you install a new module distribution would be very tedious. Thus, you can put these options into your Distutils config file (see section Distutils Configuration Files):

[install]
install-base=$HOME
install-purelib=python/lib
install-platlib=python/lib.$PLAT
install-scripts=python/scripts
install-data=python/data

or, equivalently,

[install]
install-base=$HOME/python
install-purelib=lib
install-platlib=lib.$PLAT
install-scripts=scripts
install-data=data

Note that these two are not equivalent if you supply a different installation base directory when you run the setup script. For example,

python setup.py install --install-base=/tmp

would install pure modules to /tmp/python/lib in the first case, and to /tmp/lib in the second case. (For the second case, you probably want to supply an installation base of /tmp/python.)

You probably noticed the use of $HOME and $PLAT in the sample configuration file input. These are Distutils configuration variables, which bear a strong resemblance to environment variables. In fact, you can use environment variables in config files on platforms that have such a notion but the Distutils additionally define a few extra variables that may not be in your environment, such as $PLAT. (And of course, on systems that don’t have environment variables, such as Mac OS 9, the configuration variables supplied by the Distutils are the only ones you can use.) See section Distutils Configuration Files for details.

Modifying Python’s Search Path

When the Python interpreter executes an import statement, it searches for both Python code and extension modules along a search path. A default value for the path is configured into the Python binary when the interpreter is built. You can determine the path by importing the sys module and printing the value of sys.path.

$ python
Python 2.2 (#11, Oct  3 2002, 13:31:27)
[GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['', '/usr/local/lib/python2.3', '/usr/local/lib/python2.3/plat-linux2',
 '/usr/local/lib/python2.3/lib-tk', '/usr/local/lib/python2.3/lib-dynload',
 '/usr/local/lib/python2.3/site-packages']
>>>

The null string in sys.path represents the current working directory.

The expected convention for locally installed packages is to put them in the .../site-packages/ directory, but you may want to install Python modules into some arbitrary directory. For example, your site may have a convention of keeping all software related to the web server under /www. Add-on Python modules might then belong in /www/python, and in order to import them, this directory must be added to sys.path. There are several different ways to add the directory.

The most convenient way is to add a path configuration file to a directory that’s already on Python’s path, usually to the .../site-packages/ directory. Path configuration files have an extension of .pth, and each line must contain a single path that will be appended to sys.path. (Because the new paths are appended to sys.path, modules in the added directories will not override standard modules. This means you can’t use this mechanism for installing fixed versions of standard modules.)

Paths can be absolute or relative, in which case they’re relative to the directory containing the .pth file. See the documentation of the site module for more information.

A slightly less convenient way is to edit the site.py file in Python’s standard library, and modify sys.path. site.py is automatically imported when the Python interpreter is executed, unless the -S switch is supplied to suppress this behaviour. So you could simply edit site.py and add two lines to it:

import sys
sys.path.append('/www/python/')

However, if you reinstall the same major version of Python (perhaps when upgrading from 2.2 to 2.2.2, for example) site.py will be overwritten by the stock version. You’d have to remember that it was modified and save a copy before doing the installation.

There are two environment variables that can modify sys.path. PYTHONHOME sets an alternate value for the prefix of the Python installation. For example, if PYTHONHOME is set to /www/python, the search path will be set to ['', '/www/python/lib/pythonX.Y/', '/www/python/lib/pythonX.Y/plat-linux2', ...].

The PYTHONPATH variable can be set to a list of paths that will be added to the beginning of sys.path. For example, if PYTHONPATH is set to /www/python:/opt/py, the search path will begin with ['/www/python', '/opt/py']. (Note that directories must exist in order to be added to sys.path; the site module removes paths that don’t exist.)

Finally, sys.path is just a regular Python list, so any Python application can modify it by adding or removing entries.

Distutils Configuration Files

As mentioned above, you can use Distutils configuration files to record personal or site preferences for any Distutils options. That is, any option to any command can be stored in one of two or three (depending on your platform) configuration files, which will be consulted before the command-line is parsed. This means that configuration files will override default values, and the command-line will in turn override configuration files. Furthermore, if multiple configuration files apply, values from “earlier” files are overridden by “later” files.

Location and names of config files

The names and locations of the configuration files vary slightly across platforms. On Unix and Mac OS X, the three configuration files (in the order they are processed) are:

Type of file Location and filename Notes
system prefix/lib/pythonver/distutils/distutils.cfg (1)
personal $HOME/.pydistutils.cfg (2)
local setup.cfg (3)

And on Windows, the configuration files are:

Type of file Location and filename Notes
system prefix\Lib\distutils\distutils.cfg (4)
personal %HOME%\pydistutils.cfg (5)
local setup.cfg (3)

On all platforms, the “personal” file can be temporarily disabled by passing the –no-user-cfg option.

Notes:

  1. Strictly speaking, the system-wide configuration file lives in the directory where the Distutils are installed; under Python 1.6 and later on Unix, this is as shown. For Python 1.5.2, the Distutils will normally be installed to prefix/lib/python1.5/site-packages/distutils, so the system configuration file should be put there under Python 1.5.2.
  2. On Unix, if the HOME environment variable is not defined, the user’s home directory will be determined with the getpwuid() function from the standard pwd module. This is done by the os.path.expanduser() function used by Distutils.
  3. I.e., in the current directory (usually the location of the setup script).
  4. (See also note (1).) Under Python 1.6 and later, Python’s default “installation prefix” is C:\Python, so the system configuration file is normally C:\Python\Lib\distutils\distutils.cfg. Under Python 1.5.2, the default prefix was C:\Program Files\Python, and the Distutils were not part of the standard library—so the system configuration file would be C:\Program Files\Python\distutils\distutils.cfg in a standard Python 1.5.2 installation under Windows.
  5. On Windows, if the HOME environment variable is not defined, USERPROFILE then HOMEDRIVE and HOMEPATH will be tried. This is done by the os.path.expanduser() function used by Distutils.

Syntax of config files

The Distutils configuration files all have the same syntax. The config files are grouped into sections. There is one section for each Distutils command, plus a global section for global options that affect every command. Each section consists of one option per line, specified as option=value.

For example, the following is a complete config file that just forces all commands to run quietly by default:

[global]
verbose=0

If this is installed as the system config file, it will affect all processing of any Python module distribution by any user on the current system. If it is installed as your personal config file (on systems that support them), it will affect only module distributions processed by you. And if it is used as the setup.cfg for a particular module distribution, it affects only that distribution.

You could override the default “build base” directory and make the build* commands always forcibly rebuild all files with the following:

[build]
build-base=blib
force=1

which corresponds to the command-line arguments

python setup.py build --build-base=blib --force

except that including the build command on the command-line means that command will be run. Including a particular command in config files has no such implication; it only means that if the command is run, the options in the config file will apply. (Or if other commands that derive values from it are run, they will use the values in the config file.)

You can find out the complete list of options for any command using the --help option, e.g.:

python setup.py build --help

and you can find out the complete list of global options by using --help without a command:

python setup.py --help

See also the “Reference” section of the “Distributing Python Modules” manual.

Building Extensions: Tips and Tricks

Whenever possible, the Distutils try to use the configuration information made available by the Python interpreter used to run the setup.py script. For example, the same compiler and linker flags used to compile Python will also be used for compiling extensions. Usually this will work well, but in complicated situations this might be inappropriate. This section discusses how to override the usual Distutils behaviour.

Tweaking compiler/linker flags

Compiling a Python extension written in C or C++ will sometimes require specifying custom flags for the compiler and linker in order to use a particular library or produce a special kind of object code. This is especially true if the extension hasn’t been tested on your platform, or if you’re trying to cross-compile Python.

In the most general case, the extension author might have foreseen that compiling the extensions would be complicated, and provided a Setup file for you to edit. This will likely only be done if the module distribution contains many separate extension modules, or if they often require elaborate sets of compiler flags in order to work.

A Setup file, if present, is parsed in order to get a list of extensions to build. Each line in a Setup describes a single module. Lines have the following structure:

module ... [sourcefile ...] [cpparg ...] [library ...]

Let’s examine each of the fields in turn.

  • module is the name of the extension module to be built, and should be a valid Python identifier. You can’t just change this in order to rename a module (edits to the source code would also be needed), so this should be left alone.
  • sourcefile is anything that’s likely to be a source code file, at least judging by the filename. Filenames ending in .c are assumed to be written in C, filenames ending in .C, .cc, and .c++ are assumed to be C++, and filenames ending in .m or .mm are assumed to be in Objective C.
  • cpparg is an argument for the C preprocessor, and is anything starting with -I, -D, -U or -C.
  • library is anything ending in .a or beginning with -l or -L.

If a particular platform requires a special library on your platform, you can add it by editing the Setup file and running python setup.py build. For example, if the module defined by the line

foo foomodule.c

must be linked with the math library libm.a on your platform, simply add -lm to the line:

foo foomodule.c -lm

Arbitrary switches intended for the compiler or the linker can be supplied with the -Xcompiler arg and -Xlinker arg options:

foo foomodule.c -Xcompiler -o32 -Xlinker -shared -lm

The next option after -Xcompiler and -Xlinker will be appended to the proper command line, so in the above example the compiler will be passed the -o32 option, and the linker will be passed -shared. If a compiler option requires an argument, you’ll have to supply multiple -Xcompiler options; for example, to pass -x c++ the Setup file would have to contain -Xcompiler -x -Xcompiler c++.

Compiler flags can also be supplied through setting the CFLAGS environment variable. If set, the contents of CFLAGS will be added to the compiler flags specified in the Setup file.

Using non-Microsoft compilers on Windows

Borland/CodeGear C++

This subsection describes the necessary steps to use Distutils with the Borland C++ compiler version 5.5. First you have to know that Borland’s object file format (OMF) is different from the format used by the Python version you can download from the Python or ActiveState Web site. (Python is built with Microsoft Visual C++, which uses COFF as the object file format.) For this reason you have to convert Python’s library python25.lib into the Borland format. You can do this as follows:

coff2omf python25.lib python25_bcpp.lib

The coff2omf program comes with the Borland compiler. The file python25.lib is in the Libs directory of your Python installation. If your extension uses other libraries (zlib, ...) you have to convert them too.

The converted files have to reside in the same directories as the normal libraries.

How does Distutils manage to use these libraries with their changed names? If the extension needs a library (eg. foo) Distutils checks first if it finds a library with suffix _bcpp (eg. foo_bcpp.lib) and then uses this library. In the case it doesn’t find such a special library it uses the default name (foo.lib.) [1]

To let Distutils compile your extension with Borland C++ you now have to type:

python setup.py build --compiler=bcpp

If you want to use the Borland C++ compiler as the default, you could specify this in your personal or system-wide configuration file for Distutils (see section Distutils Configuration Files.)

See also

C++Builder Compiler
Information about the free C++ compiler from Borland, including links to the download pages.
Creating Python Extensions Using Borland’s Free Compiler
Document describing how to use Borland’s free command-line C++ compiler to build Python.

GNU C / Cygwin / MinGW

This section describes the necessary steps to use Distutils with the GNU C/C++ compilers in their Cygwin and MinGW distributions. [2] For a Python interpreter that was built with Cygwin, everything should work without any of these following steps.

Not all extensions can be built with MinGW or Cygwin, but many can. Extensions most likely to not work are those that use C++ or depend on Microsoft Visual C extensions.

To let Distutils compile your extension with Cygwin you have to type:

python setup.py build --compiler=cygwin

and for Cygwin in no-cygwin mode [3] or for MinGW type:

python setup.py build --compiler=mingw32

If you want to use any of these options/compilers as default, you should consider writing it in your personal or system-wide configuration file for Distutils (see section Distutils Configuration Files.)

Older Versions of Python and MinGW

The following instructions only apply if you’re using a version of Python inferior to 2.4.1 with a MinGW inferior to 3.0.0 (with binutils-2.13.90-20030111-1).

These compilers require some special libraries. This task is more complex than for Borland’s C++, because there is no program to convert the library. First you have to create a list of symbols which the Python DLL exports. (You can find a good program for this task at http://www.emmestech.com/software/pexports-0.43/download_pexports.html).

pexports python25.dll >python25.def

The location of an installed python25.dll will depend on the installation options and the version and language of Windows. In a “just for me” installation, it will appear in the root of the installation directory. In a shared installation, it will be located in the system directory.

Then you can create from these information an import library for gcc.

/cygwin/bin/dlltool --dllname python25.dll --def python25.def --output-lib libpython25.a

The resulting library has to be placed in the same directory as python25.lib. (Should be the libs directory under your Python installation directory.)

If your extension uses other libraries (zlib,...) you might have to convert them too. The converted files have to reside in the same directories as the normal libraries do.

See also

Building Python modules on MS Windows platform with MinGW
Information about building the required libraries for the MinGW environment.

Footnotes

[1]This also means you could replace all existing COFF-libraries with OMF-libraries of the same name.
[2]Check http://sources.redhat.com/cygwin/ and http://www.mingw.org/ for more information
[3]Then you have no POSIX emulation available, but you also don’t need cygwin1.dll.

Table Of Contents

Previous topic

10. API Reference

Next topic

Python HOWTOs

This Page

Navigation

© Copyright 1990-2019, Python Software Foundation.
The Python Software Foundation is a non-profit corporation. Please donate.
Last updated on Jul 03, 2019. Found a bug?
Created using Sphinx 1.1.3.
index.txt000064400000137710147563006120006431 0ustar00.. highlightlang:: none .. _install-index: ***************************** Installing Python Modules ***************************** :Author: Greg Ward .. TODO: Fill in XXX comments .. The audience for this document includes people who don't know anything about Python and aren't about to learn the language just in order to install and maintain it for their users, i.e. system administrators. Thus, I have to be sure to explain the basics at some point: sys.path and PYTHONPATH at least. Should probably give pointers to other docs on "import site", PYTHONSTARTUP, PYTHONHOME, etc. Finally, it might be useful to include all the material from my "Care and Feeding of a Python Installation" talk in here somewhere. Yow! .. topic:: Abstract This document describes the Python Distribution Utilities ("Distutils") from the end-user's point-of-view, describing how to extend the capabilities of a standard Python installation by building and installing third-party Python modules and extensions. .. _inst-intro: Introduction ============ Although Python's extensive standard library covers many programming needs, there often comes a time when you need to add some new functionality to your Python installation in the form of third-party modules. This might be necessary to support your own programming, or to support an application that you want to use and that happens to be written in Python. In the past, there has been little support for adding third-party modules to an existing Python installation. With the introduction of the Python Distribution Utilities (Distutils for short) in Python 2.0, this changed. This document is aimed primarily at the people who need to install third-party Python modules: end-users and system administrators who just need to get some Python application running, and existing Python programmers who want to add some new goodies to their toolbox. You don't need to know Python to read this document; there will be some brief forays into using Python's interactive mode to explore your installation, but that's it. If you're looking for information on how to distribute your own Python modules so that others may use them, see the :ref:`distutils-index` manual. .. _inst-trivial-install: Best case: trivial installation ------------------------------- In the best case, someone will have prepared a special version of the module distribution you want to install that is targeted specifically at your platform and is installed just like any other software on your platform. For example, the module developer might make an executable installer available for Windows users, an RPM package for users of RPM-based Linux systems (Red Hat, SuSE, Mandrake, and many others), a Debian package for users of Debian-based Linux systems, and so forth. In that case, you would download the installer appropriate to your platform and do the obvious thing with it: run it if it's an executable installer, ``rpm --install`` it if it's an RPM, etc. You don't need to run Python or a setup script, you don't need to compile anything---you might not even need to read any instructions (although it's always a good idea to do so anyway). Of course, things will not always be that easy. You might be interested in a module distribution that doesn't have an easy-to-use installer for your platform. In that case, you'll have to start with the source distribution released by the module's author/maintainer. Installing from a source distribution is not too hard, as long as the modules are packaged in the standard way. The bulk of this document is about building and installing modules from standard source distributions. .. _inst-new-standard: The new standard: Distutils --------------------------- If you download a module source distribution, you can tell pretty quickly if it was packaged and distributed in the standard way, i.e. using the Distutils. First, the distribution's name and version number will be featured prominently in the name of the downloaded archive, e.g. :file:`foo-1.0.tar.gz` or :file:`widget-0.9.7.zip`. Next, the archive will unpack into a similarly-named directory: :file:`foo-1.0` or :file:`widget-0.9.7`. Additionally, the distribution will contain a setup script :file:`setup.py`, and a file named :file:`README.txt` or possibly just :file:`README`, which should explain that building and installing the module distribution is a simple matter of running one command from a terminal:: python setup.py install For Windows, this command should be run from a command prompt window (:menuselection:`Start --> Accessories`):: setup.py install If all these things are true, then you already know how to build and install the modules you've just downloaded: Run the command above. Unless you need to install things in a non-standard way or customize the build process, you don't really need this manual. Or rather, the above command is everything you need to get out of this manual. .. _inst-standard-install: Standard Build and Install ========================== As described in section :ref:`inst-new-standard`, building and installing a module distribution using the Distutils is usually one simple command to run from a terminal:: python setup.py install .. _inst-platform-variations: Platform variations ------------------- You should always run the setup command from the distribution root directory, i.e. the top-level subdirectory that the module source distribution unpacks into. For example, if you've just downloaded a module source distribution :file:`foo-1.0.tar.gz` onto a Unix system, the normal thing to do is:: gunzip -c foo-1.0.tar.gz | tar xf - # unpacks into directory foo-1.0 cd foo-1.0 python setup.py install On Windows, you'd probably download :file:`foo-1.0.zip`. If you downloaded the archive file to :file:`C:\\Temp`, then it would unpack into :file:`C:\\Temp\\foo-1.0`; you can use either a archive manipulator with a graphical user interface (such as WinZip) or a command-line tool (such as :program:`unzip` or :program:`pkunzip`) to unpack the archive. Then, open a command prompt window and run:: cd c:\Temp\foo-1.0 python setup.py install .. _inst-splitting-up: Splitting the job up -------------------- Running ``setup.py install`` builds and installs all modules in one run. If you prefer to work incrementally---especially useful if you want to customize the build process, or if things are going wrong---you can use the setup script to do one thing at a time. This is particularly helpful when the build and install will be done by different users---for example, you might want to build a module distribution and hand it off to a system administrator for installation (or do it yourself, with super-user privileges). For example, you can build everything in one step, and then install everything in a second step, by invoking the setup script twice:: python setup.py build python setup.py install If you do this, you will notice that running the :command:`install` command first runs the :command:`build` command, which---in this case---quickly notices that it has nothing to do, since everything in the :file:`build` directory is up-to-date. You may not need this ability to break things down often if all you do is install modules downloaded off the 'net, but it's very handy for more advanced tasks. If you get into distributing your own Python modules and extensions, you'll run lots of individual Distutils commands on their own. .. _inst-how-build-works: How building works ------------------ As implied above, the :command:`build` command is responsible for putting the files to install into a *build directory*. By default, this is :file:`build` under the distribution root; if you're excessively concerned with speed, or want to keep the source tree pristine, you can change the build directory with the :option:`--build-base` option. For example:: python setup.py build --build-base=/path/to/pybuild/foo-1.0 (Or you could do this permanently with a directive in your system or personal Distutils configuration file; see section :ref:`inst-config-files`.) Normally, this isn't necessary. The default layout for the build tree is as follows:: --- build/ --- lib/ or --- build/ --- lib./ temp./ where ```` expands to a brief description of the current OS/hardware platform and Python version. The first form, with just a :file:`lib` directory, is used for "pure module distributions"---that is, module distributions that include only pure Python modules. If a module distribution contains any extensions (modules written in C/C++), then the second form, with two ```` directories, is used. In that case, the :file:`temp.{plat}` directory holds temporary files generated by the compile/link process that don't actually get installed. In either case, the :file:`lib` (or :file:`lib.{plat}`) directory contains all Python modules (pure Python and extensions) that will be installed. In the future, more directories will be added to handle Python scripts, documentation, binary executables, and whatever else is needed to handle the job of installing Python modules and applications. .. _inst-how-install-works: How installation works ---------------------- After the :command:`build` command runs (whether you run it explicitly, or the :command:`install` command does it for you), the work of the :command:`install` command is relatively simple: all it has to do is copy everything under :file:`build/lib` (or :file:`build/lib.{plat}`) to your chosen installation directory. If you don't choose an installation directory---i.e., if you just run ``setup.py install``\ ---then the :command:`install` command installs to the standard location for third-party Python modules. This location varies by platform and by how you built/installed Python itself. On Unix (and Mac OS X, which is also Unix-based), it also depends on whether the module distribution being installed is pure Python or contains extensions ("non-pure"): .. tabularcolumns:: |l|l|l|l| +-----------------+-----------------------------------------------------+--------------------------------------------------+-------+ | Platform | Standard installation location | Default value | Notes | +=================+=====================================================+==================================================+=======+ | Unix (pure) | :file:`{prefix}/lib/python{X.Y}/site-packages` | :file:`/usr/local/lib/python{X.Y}/site-packages` | \(1) | +-----------------+-----------------------------------------------------+--------------------------------------------------+-------+ | Unix (non-pure) | :file:`{exec-prefix}/lib/python{X.Y}/site-packages` | :file:`/usr/local/lib/python{X.Y}/site-packages` | \(1) | +-----------------+-----------------------------------------------------+--------------------------------------------------+-------+ | Windows | :file:`{prefix}\\Lib\\site-packages` | :file:`C:\\Python{XY}\\Lib\\site-packages` | \(2) | +-----------------+-----------------------------------------------------+--------------------------------------------------+-------+ Notes: (1) Most Linux distributions include Python as a standard part of the system, so :file:`{prefix}` and :file:`{exec-prefix}` are usually both :file:`/usr` on Linux. If you build Python yourself on Linux (or any Unix-like system), the default :file:`{prefix}` and :file:`{exec-prefix}` are :file:`/usr/local`. (2) The default installation directory on Windows was :file:`C:\\Program Files\\Python` under Python 1.6a1, 1.5.2, and earlier. :file:`{prefix}` and :file:`{exec-prefix}` stand for the directories that Python is installed to, and where it finds its libraries at run-time. They are always the same under Windows, and very often the same under Unix and Mac OS X. You can find out what your Python installation uses for :file:`{prefix}` and :file:`{exec-prefix}` by running Python in interactive mode and typing a few simple commands. Under Unix, just type ``python`` at the shell prompt. Under Windows, choose :menuselection:`Start --> Programs --> Python X.Y --> Python (command line)`. Once the interpreter is started, you type Python code at the prompt. For example, on my Linux system, I type the three Python statements shown below, and get the output as shown, to find out my :file:`{prefix}` and :file:`{exec-prefix}`:: Python 2.4 (#26, Aug 7 2004, 17:19:02) Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.prefix '/usr' >>> sys.exec_prefix '/usr' A few other placeholders are used in this document: :file:`{X.Y}` stands for the version of Python, for example ``2.7``; :file:`{distname}` will be replaced by the name of the module distribution being installed. Dots and capitalization are important in the paths; for example, a value that uses ``python2.7`` on UNIX will typically use ``Python27`` on Windows. If you don't want to install modules to the standard location, or if you don't have permission to write there, then you need to read about alternate installations in section :ref:`inst-alt-install`. If you want to customize your installation directories more heavily, see section :ref:`inst-custom-install` on custom installations. .. _inst-alt-install: Alternate Installation ====================== Often, it is necessary or desirable to install modules to a location other than the standard location for third-party Python modules. For example, on a Unix system you might not have permission to write to the standard third-party module directory. Or you might wish to try out a module before making it a standard part of your local Python installation. This is especially true when upgrading a distribution already present: you want to make sure your existing base of scripts still works with the new version before actually upgrading. The Distutils :command:`install` command is designed to make installing module distributions to an alternate location simple and painless. The basic idea is that you supply a base directory for the installation, and the :command:`install` command picks a set of directories (called an *installation scheme*) under this base directory in which to install files. The details differ across platforms, so read whichever of the following sections applies to you. Note that the various alternate installation schemes are mutually exclusive: you can pass ``--user``, or ``--home``, or ``--prefix`` and ``--exec-prefix``, or ``--install-base`` and ``--install-platbase``, but you can't mix from these groups. .. _inst-alt-install-user: Alternate installation: the user scheme --------------------------------------- This scheme is designed to be the most convenient solution for users that don't have write permission to the global site-packages directory or don't want to install into it. It is enabled with a simple option:: python setup.py install --user Files will be installed into subdirectories of :data:`site.USER_BASE` (written as :file:`{userbase}` hereafter). This scheme installs pure Python modules and extension modules in the same location (also known as :data:`site.USER_SITE`). Here are the values for UNIX, including Mac OS X: =============== =========================================================== Type of file Installation directory =============== =========================================================== modules :file:`{userbase}/lib/python{X.Y}/site-packages` scripts :file:`{userbase}/bin` data :file:`{userbase}` C headers :file:`{userbase}/include/python{X.Y}/{distname}` =============== =========================================================== And here are the values used on Windows: =============== =========================================================== Type of file Installation directory =============== =========================================================== modules :file:`{userbase}\\Python{XY}\\site-packages` scripts :file:`{userbase}\\Scripts` data :file:`{userbase}` C headers :file:`{userbase}\\Python{XY}\\Include\\{distname}` =============== =========================================================== The advantage of using this scheme compared to the other ones described below is that the user site-packages directory is under normal conditions always included in :data:`sys.path` (see :mod:`site` for more information), which means that there is no additional step to perform after running the :file:`setup.py` script to finalize the installation. The :command:`build_ext` command also has a ``--user`` option to add :file:`{userbase}/include` to the compiler search path for header files and :file:`{userbase}/lib` to the compiler search path for libraries as well as to the runtime search path for shared C libraries (rpath). .. _inst-alt-install-home: Alternate installation: the home scheme --------------------------------------- The idea behind the "home scheme" is that you build and maintain a personal stash of Python modules. This scheme's name is derived from the idea of a "home" directory on Unix, since it's not unusual for a Unix user to make their home directory have a layout similar to :file:`/usr/` or :file:`/usr/local/`. This scheme can be used by anyone, regardless of the operating system they are installing for. Installing a new module distribution is as simple as :: python setup.py install --home= where you can supply any directory you like for the :option:`--home` option. On Unix, lazy typists can just type a tilde (``~``); the :command:`install` command will expand this to your home directory:: python setup.py install --home=~ To make Python find the distributions installed with this scheme, you may have to :ref:`modify Python's search path ` or edit :mod:`sitecustomize` (see :mod:`site`) to call :func:`site.addsitedir` or edit :data:`sys.path`. The :option:`--home` option defines the installation base directory. Files are installed to the following directories under the installation base as follows: =============== =========================================================== Type of file Installation directory =============== =========================================================== modules :file:`{home}/lib/python` scripts :file:`{home}/bin` data :file:`{home}` C headers :file:`{home}/include/python/{distname}` =============== =========================================================== (Mentally replace slashes with backslashes if you're on Windows.) .. versionchanged:: 2.4 The :option:`--home` option used to be supported only on Unix. .. _inst-alt-install-prefix-unix: Alternate installation: Unix (the prefix scheme) ------------------------------------------------ The "prefix scheme" is useful when you wish to use one Python installation to perform the build/install (i.e., to run the setup script), but install modules into the third-party module directory of a different Python installation (or something that looks like a different Python installation). If this sounds a trifle unusual, it is---that's why the user and home schemes come before. However, there are at least two known cases where the prefix scheme will be useful. First, consider that many Linux distributions put Python in :file:`/usr`, rather than the more traditional :file:`/usr/local`. This is entirely appropriate, since in those cases Python is part of "the system" rather than a local add-on. However, if you are installing Python modules from source, you probably want them to go in :file:`/usr/local/lib/python2.{X}` rather than :file:`/usr/lib/python2.{X}`. This can be done with :: /usr/bin/python setup.py install --prefix=/usr/local Another possibility is a network filesystem where the name used to write to a remote directory is different from the name used to read it: for example, the Python interpreter accessed as :file:`/usr/local/bin/python` might search for modules in :file:`/usr/local/lib/python2.{X}`, but those modules would have to be installed to, say, :file:`/mnt/{@server}/export/lib/python2.{X}`. This could be done with :: /usr/local/bin/python setup.py install --prefix=/mnt/@server/export In either case, the :option:`--prefix` option defines the installation base, and the :option:`--exec-prefix` option defines the platform-specific installation base, which is used for platform-specific files. (Currently, this just means non-pure module distributions, but could be expanded to C libraries, binary executables, etc.) If :option:`--exec-prefix` is not supplied, it defaults to :option:`--prefix`. Files are installed as follows: ================= ========================================================== Type of file Installation directory ================= ========================================================== Python modules :file:`{prefix}/lib/python{X.Y}/site-packages` extension modules :file:`{exec-prefix}/lib/python{X.Y}/site-packages` scripts :file:`{prefix}/bin` data :file:`{prefix}` C headers :file:`{prefix}/include/python{X.Y}/{distname}` ================= ========================================================== There is no requirement that :option:`--prefix` or :option:`--exec-prefix` actually point to an alternate Python installation; if the directories listed above do not already exist, they are created at installation time. Incidentally, the real reason the prefix scheme is important is simply that a standard Unix installation uses the prefix scheme, but with :option:`--prefix` and :option:`--exec-prefix` supplied by Python itself as ``sys.prefix`` and ``sys.exec_prefix``. Thus, you might think you'll never use the prefix scheme, but every time you run ``python setup.py install`` without any other options, you're using it. Note that installing extensions to an alternate Python installation has no effect on how those extensions are built: in particular, the Python header files (:file:`Python.h` and friends) installed with the Python interpreter used to run the setup script will be used in compiling extensions. It is your responsibility to ensure that the interpreter used to run extensions installed in this way is compatible with the interpreter used to build them. The best way to do this is to ensure that the two interpreters are the same version of Python (possibly different builds, or possibly copies of the same build). (Of course, if your :option:`--prefix` and :option:`--exec-prefix` don't even point to an alternate Python installation, this is immaterial.) .. _inst-alt-install-prefix-windows: Alternate installation: Windows (the prefix scheme) --------------------------------------------------- Windows has no concept of a user's home directory, and since the standard Python installation under Windows is simpler than under Unix, the :option:`--prefix` option has traditionally been used to install additional packages in separate locations on Windows. :: python setup.py install --prefix="\Temp\Python" to install modules to the :file:`\\Temp\\Python` directory on the current drive. The installation base is defined by the :option:`--prefix` option; the :option:`--exec-prefix` option is not supported under Windows, which means that pure Python modules and extension modules are installed into the same location. Files are installed as follows: =============== ========================================================== Type of file Installation directory =============== ========================================================== modules :file:`{prefix}\\Lib\\site-packages` scripts :file:`{prefix}\\Scripts` data :file:`{prefix}` C headers :file:`{prefix}\\Include\\{distname}` =============== ========================================================== .. _inst-custom-install: Custom Installation =================== Sometimes, the alternate installation schemes described in section :ref:`inst-alt-install` just don't do what you want. You might want to tweak just one or two directories while keeping everything under the same base directory, or you might want to completely redefine the installation scheme. In either case, you're creating a *custom installation scheme*. To create a custom installation scheme, you start with one of the alternate schemes and override some of the installation directories used for the various types of files, using these options: ====================== ======================= Type of file Override option ====================== ======================= Python modules ``--install-purelib`` extension modules ``--install-platlib`` all modules ``--install-lib`` scripts ``--install-scripts`` data ``--install-data`` C headers ``--install-headers`` ====================== ======================= These override options can be relative, absolute, or explicitly defined in terms of one of the installation base directories. (There are two installation base directories, and they are normally the same--- they only differ when you use the Unix "prefix scheme" and supply different ``--prefix`` and ``--exec-prefix`` options; using ``--install-lib`` will override values computed or given for ``--install-purelib`` and ``--install-platlib``, and is recommended for schemes that don't make a difference between Python and extension modules.) For example, say you're installing a module distribution to your home directory under Unix---but you want scripts to go in :file:`~/scripts` rather than :file:`~/bin`. As you might expect, you can override this directory with the :option:`--install-scripts` option; in this case, it makes most sense to supply a relative path, which will be interpreted relative to the installation base directory (your home directory, in this case):: python setup.py install --home=~ --install-scripts=scripts Another Unix example: suppose your Python installation was built and installed with a prefix of :file:`/usr/local/python`, so under a standard installation scripts will wind up in :file:`/usr/local/python/bin`. If you want them in :file:`/usr/local/bin` instead, you would supply this absolute directory for the :option:`--install-scripts` option:: python setup.py install --install-scripts=/usr/local/bin (This performs an installation using the "prefix scheme," where the prefix is whatever your Python interpreter was installed with--- :file:`/usr/local/python` in this case.) If you maintain Python on Windows, you might want third-party modules to live in a subdirectory of :file:`{prefix}`, rather than right in :file:`{prefix}` itself. This is almost as easy as customizing the script installation directory ---you just have to remember that there are two types of modules to worry about, Python and extension modules, which can conveniently be both controlled by one option:: python setup.py install --install-lib=Site The specified installation directory is relative to :file:`{prefix}`. Of course, you also have to ensure that this directory is in Python's module search path, such as by putting a :file:`.pth` file in a site directory (see :mod:`site`). See section :ref:`inst-search-path` to find out how to modify Python's search path. If you want to define an entire installation scheme, you just have to supply all of the installation directory options. The recommended way to do this is to supply relative paths; for example, if you want to maintain all Python module-related files under :file:`python` in your home directory, and you want a separate directory for each platform that you use your home directory from, you might define the following installation scheme:: python setup.py install --home=~ \ --install-purelib=python/lib \ --install-platlib=python/lib.$PLAT \ --install-scripts=python/scripts --install-data=python/data or, equivalently, :: python setup.py install --home=~/python \ --install-purelib=lib \ --install-platlib='lib.$PLAT' \ --install-scripts=scripts --install-data=data ``$PLAT`` is not (necessarily) an environment variable---it will be expanded by the Distutils as it parses your command line options, just as it does when parsing your configuration file(s). Obviously, specifying the entire installation scheme every time you install a new module distribution would be very tedious. Thus, you can put these options into your Distutils config file (see section :ref:`inst-config-files`):: [install] install-base=$HOME install-purelib=python/lib install-platlib=python/lib.$PLAT install-scripts=python/scripts install-data=python/data or, equivalently, :: [install] install-base=$HOME/python install-purelib=lib install-platlib=lib.$PLAT install-scripts=scripts install-data=data Note that these two are *not* equivalent if you supply a different installation base directory when you run the setup script. For example, :: python setup.py install --install-base=/tmp would install pure modules to :file:`/tmp/python/lib` in the first case, and to :file:`/tmp/lib` in the second case. (For the second case, you probably want to supply an installation base of :file:`/tmp/python`.) You probably noticed the use of ``$HOME`` and ``$PLAT`` in the sample configuration file input. These are Distutils configuration variables, which bear a strong resemblance to environment variables. In fact, you can use environment variables in config files on platforms that have such a notion but the Distutils additionally define a few extra variables that may not be in your environment, such as ``$PLAT``. (And of course, on systems that don't have environment variables, such as Mac OS 9, the configuration variables supplied by the Distutils are the only ones you can use.) See section :ref:`inst-config-files` for details. .. XXX need some Windows examples---when would custom installation schemes be needed on those platforms? .. XXX Move this to Doc/using .. _inst-search-path: Modifying Python's Search Path ------------------------------ When the Python interpreter executes an :keyword:`import` statement, it searches for both Python code and extension modules along a search path. A default value for the path is configured into the Python binary when the interpreter is built. You can determine the path by importing the :mod:`sys` module and printing the value of ``sys.path``. :: $ python Python 2.2 (#11, Oct 3 2002, 13:31:27) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.path ['', '/usr/local/lib/python2.3', '/usr/local/lib/python2.3/plat-linux2', '/usr/local/lib/python2.3/lib-tk', '/usr/local/lib/python2.3/lib-dynload', '/usr/local/lib/python2.3/site-packages'] >>> The null string in ``sys.path`` represents the current working directory. The expected convention for locally installed packages is to put them in the :file:`{...}/site-packages/` directory, but you may want to install Python modules into some arbitrary directory. For example, your site may have a convention of keeping all software related to the web server under :file:`/www`. Add-on Python modules might then belong in :file:`/www/python`, and in order to import them, this directory must be added to ``sys.path``. There are several different ways to add the directory. The most convenient way is to add a path configuration file to a directory that's already on Python's path, usually to the :file:`.../site-packages/` directory. Path configuration files have an extension of :file:`.pth`, and each line must contain a single path that will be appended to ``sys.path``. (Because the new paths are appended to ``sys.path``, modules in the added directories will not override standard modules. This means you can't use this mechanism for installing fixed versions of standard modules.) Paths can be absolute or relative, in which case they're relative to the directory containing the :file:`.pth` file. See the documentation of the :mod:`site` module for more information. A slightly less convenient way is to edit the :file:`site.py` file in Python's standard library, and modify ``sys.path``. :file:`site.py` is automatically imported when the Python interpreter is executed, unless the :option:`-S` switch is supplied to suppress this behaviour. So you could simply edit :file:`site.py` and add two lines to it:: import sys sys.path.append('/www/python/') However, if you reinstall the same major version of Python (perhaps when upgrading from 2.2 to 2.2.2, for example) :file:`site.py` will be overwritten by the stock version. You'd have to remember that it was modified and save a copy before doing the installation. There are two environment variables that can modify ``sys.path``. :envvar:`PYTHONHOME` sets an alternate value for the prefix of the Python installation. For example, if :envvar:`PYTHONHOME` is set to ``/www/python``, the search path will be set to ``['', '/www/python/lib/pythonX.Y/', '/www/python/lib/pythonX.Y/plat-linux2', ...]``. The :envvar:`PYTHONPATH` variable can be set to a list of paths that will be added to the beginning of ``sys.path``. For example, if :envvar:`PYTHONPATH` is set to ``/www/python:/opt/py``, the search path will begin with ``['/www/python', '/opt/py']``. (Note that directories must exist in order to be added to ``sys.path``; the :mod:`site` module removes paths that don't exist.) Finally, ``sys.path`` is just a regular Python list, so any Python application can modify it by adding or removing entries. .. _inst-config-files: Distutils Configuration Files ============================= As mentioned above, you can use Distutils configuration files to record personal or site preferences for any Distutils options. That is, any option to any command can be stored in one of two or three (depending on your platform) configuration files, which will be consulted before the command-line is parsed. This means that configuration files will override default values, and the command-line will in turn override configuration files. Furthermore, if multiple configuration files apply, values from "earlier" files are overridden by "later" files. .. _inst-config-filenames: Location and names of config files ---------------------------------- The names and locations of the configuration files vary slightly across platforms. On Unix and Mac OS X, the three configuration files (in the order they are processed) are: +--------------+----------------------------------------------------------+-------+ | Type of file | Location and filename | Notes | +==============+==========================================================+=======+ | system | :file:`{prefix}/lib/python{ver}/distutils/distutils.cfg` | \(1) | +--------------+----------------------------------------------------------+-------+ | personal | :file:`$HOME/.pydistutils.cfg` | \(2) | +--------------+----------------------------------------------------------+-------+ | local | :file:`setup.cfg` | \(3) | +--------------+----------------------------------------------------------+-------+ And on Windows, the configuration files are: +--------------+-------------------------------------------------+-------+ | Type of file | Location and filename | Notes | +==============+=================================================+=======+ | system | :file:`{prefix}\\Lib\\distutils\\distutils.cfg` | \(4) | +--------------+-------------------------------------------------+-------+ | personal | :file:`%HOME%\\pydistutils.cfg` | \(5) | +--------------+-------------------------------------------------+-------+ | local | :file:`setup.cfg` | \(3) | +--------------+-------------------------------------------------+-------+ On all platforms, the "personal" file can be temporarily disabled by passing the `--no-user-cfg` option. Notes: (1) Strictly speaking, the system-wide configuration file lives in the directory where the Distutils are installed; under Python 1.6 and later on Unix, this is as shown. For Python 1.5.2, the Distutils will normally be installed to :file:`{prefix}/lib/python1.5/site-packages/distutils`, so the system configuration file should be put there under Python 1.5.2. (2) On Unix, if the :envvar:`HOME` environment variable is not defined, the user's home directory will be determined with the :func:`getpwuid` function from the standard :mod:`pwd` module. This is done by the :func:`os.path.expanduser` function used by Distutils. (3) I.e., in the current directory (usually the location of the setup script). (4) (See also note (1).) Under Python 1.6 and later, Python's default "installation prefix" is :file:`C:\\Python`, so the system configuration file is normally :file:`C:\\Python\\Lib\\distutils\\distutils.cfg`. Under Python 1.5.2, the default prefix was :file:`C:\\Program Files\\Python`, and the Distutils were not part of the standard library---so the system configuration file would be :file:`C:\\Program Files\\Python\\distutils\\distutils.cfg` in a standard Python 1.5.2 installation under Windows. (5) On Windows, if the :envvar:`HOME` environment variable is not defined, :envvar:`USERPROFILE` then :envvar:`HOMEDRIVE` and :envvar:`HOMEPATH` will be tried. This is done by the :func:`os.path.expanduser` function used by Distutils. .. _inst-config-syntax: Syntax of config files ---------------------- The Distutils configuration files all have the same syntax. The config files are grouped into sections. There is one section for each Distutils command, plus a ``global`` section for global options that affect every command. Each section consists of one option per line, specified as ``option=value``. For example, the following is a complete config file that just forces all commands to run quietly by default:: [global] verbose=0 If this is installed as the system config file, it will affect all processing of any Python module distribution by any user on the current system. If it is installed as your personal config file (on systems that support them), it will affect only module distributions processed by you. And if it is used as the :file:`setup.cfg` for a particular module distribution, it affects only that distribution. You could override the default "build base" directory and make the :command:`build\*` commands always forcibly rebuild all files with the following:: [build] build-base=blib force=1 which corresponds to the command-line arguments :: python setup.py build --build-base=blib --force except that including the :command:`build` command on the command-line means that command will be run. Including a particular command in config files has no such implication; it only means that if the command is run, the options in the config file will apply. (Or if other commands that derive values from it are run, they will use the values in the config file.) You can find out the complete list of options for any command using the :option:`--help` option, e.g.:: python setup.py build --help and you can find out the complete list of global options by using :option:`--help` without a command:: python setup.py --help See also the "Reference" section of the "Distributing Python Modules" manual. .. _inst-building-ext: Building Extensions: Tips and Tricks ==================================== Whenever possible, the Distutils try to use the configuration information made available by the Python interpreter used to run the :file:`setup.py` script. For example, the same compiler and linker flags used to compile Python will also be used for compiling extensions. Usually this will work well, but in complicated situations this might be inappropriate. This section discusses how to override the usual Distutils behaviour. .. _inst-tweak-flags: Tweaking compiler/linker flags ------------------------------ Compiling a Python extension written in C or C++ will sometimes require specifying custom flags for the compiler and linker in order to use a particular library or produce a special kind of object code. This is especially true if the extension hasn't been tested on your platform, or if you're trying to cross-compile Python. In the most general case, the extension author might have foreseen that compiling the extensions would be complicated, and provided a :file:`Setup` file for you to edit. This will likely only be done if the module distribution contains many separate extension modules, or if they often require elaborate sets of compiler flags in order to work. A :file:`Setup` file, if present, is parsed in order to get a list of extensions to build. Each line in a :file:`Setup` describes a single module. Lines have the following structure:: module ... [sourcefile ...] [cpparg ...] [library ...] Let's examine each of the fields in turn. * *module* is the name of the extension module to be built, and should be a valid Python identifier. You can't just change this in order to rename a module (edits to the source code would also be needed), so this should be left alone. * *sourcefile* is anything that's likely to be a source code file, at least judging by the filename. Filenames ending in :file:`.c` are assumed to be written in C, filenames ending in :file:`.C`, :file:`.cc`, and :file:`.c++` are assumed to be C++, and filenames ending in :file:`.m` or :file:`.mm` are assumed to be in Objective C. * *cpparg* is an argument for the C preprocessor, and is anything starting with :option:`-I`, :option:`-D`, :option:`-U` or :option:`-C`. * *library* is anything ending in :file:`.a` or beginning with :option:`-l` or :option:`-L`. If a particular platform requires a special library on your platform, you can add it by editing the :file:`Setup` file and running ``python setup.py build``. For example, if the module defined by the line :: foo foomodule.c must be linked with the math library :file:`libm.a` on your platform, simply add :option:`-lm` to the line:: foo foomodule.c -lm Arbitrary switches intended for the compiler or the linker can be supplied with the :option:`-Xcompiler` *arg* and :option:`-Xlinker` *arg* options:: foo foomodule.c -Xcompiler -o32 -Xlinker -shared -lm The next option after :option:`-Xcompiler` and :option:`-Xlinker` will be appended to the proper command line, so in the above example the compiler will be passed the :option:`-o32` option, and the linker will be passed :option:`-shared`. If a compiler option requires an argument, you'll have to supply multiple :option:`-Xcompiler` options; for example, to pass ``-x c++`` the :file:`Setup` file would have to contain ``-Xcompiler -x -Xcompiler c++``. Compiler flags can also be supplied through setting the :envvar:`CFLAGS` environment variable. If set, the contents of :envvar:`CFLAGS` will be added to the compiler flags specified in the :file:`Setup` file. .. _inst-non-ms-compilers: Using non-Microsoft compilers on Windows ---------------------------------------- .. sectionauthor:: Rene Liebscher Borland/CodeGear C++ ^^^^^^^^^^^^^^^^^^^^ This subsection describes the necessary steps to use Distutils with the Borland C++ compiler version 5.5. First you have to know that Borland's object file format (OMF) is different from the format used by the Python version you can download from the Python or ActiveState Web site. (Python is built with Microsoft Visual C++, which uses COFF as the object file format.) For this reason you have to convert Python's library :file:`python25.lib` into the Borland format. You can do this as follows: .. Should we mention that users have to create cfg-files for the compiler? .. see also http://community.borland.com/article/0,1410,21205,00.html :: coff2omf python25.lib python25_bcpp.lib The :file:`coff2omf` program comes with the Borland compiler. The file :file:`python25.lib` is in the :file:`Libs` directory of your Python installation. If your extension uses other libraries (zlib, ...) you have to convert them too. The converted files have to reside in the same directories as the normal libraries. How does Distutils manage to use these libraries with their changed names? If the extension needs a library (eg. :file:`foo`) Distutils checks first if it finds a library with suffix :file:`_bcpp` (eg. :file:`foo_bcpp.lib`) and then uses this library. In the case it doesn't find such a special library it uses the default name (:file:`foo.lib`.) [#]_ To let Distutils compile your extension with Borland C++ you now have to type:: python setup.py build --compiler=bcpp If you want to use the Borland C++ compiler as the default, you could specify this in your personal or system-wide configuration file for Distutils (see section :ref:`inst-config-files`.) .. seealso:: `C++Builder Compiler `_ Information about the free C++ compiler from Borland, including links to the download pages. `Creating Python Extensions Using Borland's Free Compiler `_ Document describing how to use Borland's free command-line C++ compiler to build Python. GNU C / Cygwin / MinGW ^^^^^^^^^^^^^^^^^^^^^^ This section describes the necessary steps to use Distutils with the GNU C/C++ compilers in their Cygwin and MinGW distributions. [#]_ For a Python interpreter that was built with Cygwin, everything should work without any of these following steps. Not all extensions can be built with MinGW or Cygwin, but many can. Extensions most likely to not work are those that use C++ or depend on Microsoft Visual C extensions. To let Distutils compile your extension with Cygwin you have to type:: python setup.py build --compiler=cygwin and for Cygwin in no-cygwin mode [#]_ or for MinGW type:: python setup.py build --compiler=mingw32 If you want to use any of these options/compilers as default, you should consider writing it in your personal or system-wide configuration file for Distutils (see section :ref:`inst-config-files`.) Older Versions of Python and MinGW """""""""""""""""""""""""""""""""" The following instructions only apply if you're using a version of Python inferior to 2.4.1 with a MinGW inferior to 3.0.0 (with binutils-2.13.90-20030111-1). These compilers require some special libraries. This task is more complex than for Borland's C++, because there is no program to convert the library. First you have to create a list of symbols which the Python DLL exports. (You can find a good program for this task at http://www.emmestech.com/software/pexports-0.43/download_pexports.html). .. I don't understand what the next line means. --amk .. (inclusive the references on data structures.) :: pexports python25.dll >python25.def The location of an installed :file:`python25.dll` will depend on the installation options and the version and language of Windows. In a "just for me" installation, it will appear in the root of the installation directory. In a shared installation, it will be located in the system directory. Then you can create from these information an import library for gcc. :: /cygwin/bin/dlltool --dllname python25.dll --def python25.def --output-lib libpython25.a The resulting library has to be placed in the same directory as :file:`python25.lib`. (Should be the :file:`libs` directory under your Python installation directory.) If your extension uses other libraries (zlib,...) you might have to convert them too. The converted files have to reside in the same directories as the normal libraries do. .. seealso:: `Building Python modules on MS Windows platform with MinGW `_ Information about building the required libraries for the MinGW environment. .. rubric:: Footnotes .. [#] This also means you could replace all existing COFF-libraries with OMF-libraries of the same name. .. [#] Check http://sources.redhat.com/cygwin/ and http://www.mingw.org/ for more information .. [#] Then you have no POSIX emulation available, but you also don't need :file:`cygwin1.dll`.