Bug#475971: This is caused by LDFLAGS being set in the environment (by dpkg-buildpacakge)

2008-04-21 Thread Josselin Mouette
Le dimanche 20 avril 2008 à 21:00 +0200, Adeodato Simó a écrit : Python's distutils honour LDFLAGS, and when building the python extension passes -z,defs to the linker, and the build obviously bombs. I guess the solution is to accept LDFLAGS is to be exported, and to make the part that

Bug#475971: This is caused by LDFLAGS being set in the environment (by dpkg-buildpacakge)

2008-04-20 Thread Adeodato Simó
After a bit of inspection, the root of this FTBFS seems to be dpkg-buildpackage having set LDFLAGS in the environment (even to an empty value, mind you). The generated Makefiles set 'LDFLAGS = -z,defs', and as LDFLAGS was previously in the environment, this new value is exported to processes

Bug#475971: This is caused by LDFLAGS being set in the environment (by dpkg-buildpacakge)

2008-04-20 Thread Bernd Zeimetz
Adeodato Simó wrote: After a bit of inspection, the root of this FTBFS seems to be dpkg-buildpackage having set LDFLAGS in the environment (even to an empty value, mind you). Two of my packages were affected by this uglyness, too. If you use LDFLAGS as _make_ variable to build up the linker

Bug#475971: This is caused by LDFLAGS being set in the environment (by dpkg-buildpacakge)

2008-04-20 Thread Adeodato Simó
* Bernd Zeimetz [Sun, 20 Apr 2008 22:03:54 +0200]: Adeodato Simó wrote: After a bit of inspection, the root of this FTBFS seems to be dpkg-buildpackage having set LDFLAGS in the environment (even to an empty value, mind you). If you use LDFLAGS as _make_ variable to build up the linker