Brian Cameron-san wrote (02/18/09 02:52 AM): > > Is this a bug in libproxy, or a bug in Python itself? I'd make > sure to file a bug in bugster about this issue so it gets fixed. > It seems a fairly serious compatibility issue, so I'd make sure > the bug is P2 or higher.
I think it's a bug in Python2.6 and libproxy-04-py-find-lib.diff is a workaround. I think it's better to have the internal patch until it will be upstreamed because it depends on Solaris and the util.py already includes several 'if sys.platform' parts. > > Brian > > > Takao Fujiwara - Tokyo S/W Center wrote: >> Ke Wang-san wrote (02/17/09 08:03 PM): >>> Hi, >>> >>> I find where the problem is. >>> >>> ctypes.util.find_library uses following command to find the library >>> name: >>> >>> gcc -Wl,-t -o xxx -lxxx >>> >>> I tested this on Ubuntu, it will output some messages including library >>> names. But on Solaris, it does not. >>> >>> The reason is that gcc on Solaris actually does not use GNU ld as the >>> linker. Instead, it uses SUN ld. >> >> I also noticed the part doesn't work but I think the main issue is >> ldconfig. >> Most Linux machine has ldconfig so this program doesn't run gcc in >> most cases. >> >> Solaris doesn't have ldconfig so it's better to think another solution. >> I think running gcc/cc would not be the best way to find libraries but >> could be a kind of workaround. >> >> fujiwara >> >>> >>> Different linker generates different messages, this makes find_library >>> does not work correctly. >>> >>> Regards, >>> >>> Ke >>> > >
