Quote:
Originally Posted by NiLuJe
@knc1: Ooh, poisoning LDFLAGS with a specific pattern is indeed a nice idea to detect wonky buildsystems :].
- - -
|
After a decent nap, I discovered what you where writing about.
The highlighted line in the screenshot had an extra space in it.
But I lucked out, the build still blew up early, with something I can use to track back through the system with:
Added: "\" and ## comment for readablity:
Code:
configure:3218: checking whether the C compiler works
configure:3240: /var2/k2-work/k2-rel/./host/usr/bin/arm-linux-gcc \
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 \
-Wl, -I/mnt/base-us/esys/lib/ld-linux-armhf.so.3 \ ## <= from TARGET_GCCFLAGS
-DGQ \
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 \
-I/mnt/base-us/esys/lib/ld-2.21.so \ ## <= from TARGET_LDFLAGS
conftest.c >&5
Now, after my tweaking of the build system, TARGET_LDFLAGS should **only** be passed to *-linux-ld
I grep'd the build repository, there are only 160 occurances of LDFLAGS to be checked.
