[issue640553] Misuse of /usr/local/in setup.py

[Sébastien Sablé]

Sébastien Sablé sa...@users.sourceforge.net added the comment:

This bug is still present in Python 2.7.1. I have also just been beaten by it 
on solaris.

I have libintl.so.1 in /usr/lib and libintl.so.8 in /usr/local/lib.

I have never specified that I wanted to use /usr/local/lib anywhere, but the 
compilation scripts insist on linking _locale.so with libintl.so.8, which may 
not be available on the platforms where I will deploy my python binaries.

/usr/local/lib should only be used if it is explicitly specified in LDFLAGS in 
my opinion.

--
nosy: +sable
versions: +Python 2.5, Python 2.6, Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue640553
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue640553] Misuse of /usr/local/in setup.py

[Sébastien Sablé]

Sébastien Sablé sa...@users.sourceforge.net added the comment:

I can only bypass this by explicitly specifying -L/usr/lib so that it will take 
precedence over -L/usr/local/lib.

But this behavior is still broken...
Explicit is better than implicit.
I can see no reason why /usr/local should be implicitly added; people that 
really need it can always do export LDFLAGS=$LDFLAGS -L/usr/local/lib

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue640553
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com