Subject: Python modules won't compile
To: None <tech-pkg@NetBSD.org>
From: D'Arcy J.M. Cain <darcy@NetBSD.org>
List: tech-pkg
Date: 08/24/2005 07:56:56
I suddenly see the following error when I try to build a Python module
package.

building '_xmlplus.parsers.pyexpat' extension
cc -pthread -shared ${LDFLAGS} -L/usr/lib -Wl,-R/usr/lib
-Wl,-R/usr/pkg/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib
-Wl,-R/usr/lib -L/usr/pkg/lib/python2.4/config
-Wl,-R/usr/pkg/lib/python2.4/config -O2 -I/usr/pkg/include
-I/usr/include -I/usr/pkg/include/python2.4 -I/usr/pkg/include
-I/usr/include -I/usr/pkg/include/python2.4
build/temp.netbsd-3.99.7-i386-2.4/extensions/pyexpat.o
-L/usr/obj/textproc/py-xml/work.i386/.buildlink/lib -lexpat -o
build/lib.netbsd-3.99.7-i386-2.4/_xmlplus/parsers/pyexpat.so
-Wl,-R/usr/pkg/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib
-Wl,-R/usr/lib -L/usr/pkg/lib/python2.4/config
-Wl,-R/usr/pkg/lib/python2.4/config gcc: ${LDFLAGS}: No such file or
directory error: command 'cc' failed with exit status 1 *** Error code 1

It seems to happen building any Python module.  I tried looking at all
the files included in the build and I even rebuilt libtool but still
the same.  This comes just after I committed a change to Python to fix
the weakref bug but I can't see how my changes could have triggered
this.  Does anyone have any idea what might be feeding "${LDFLAGS}" to
cc rather than evaluating it?

Thanks.

-- 
D'Arcy J.M. Cain <darcy@NetBSD.org>
http://www.NetBSD.org/