This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
"random" "Link tests are not allowed after GCC_NO_EXECUTABLES"
- From: Jay <jay dot krell at cornell dot edu>
- To: <gcc at gcc dot gnu dot org>
- Date: Wed, 27 Aug 2008 08:30:29 +0000
- Subject: "random" "Link tests are not allowed after GCC_NO_EXECUTABLES"
gcc 4.3.1 with small patches... (merged tree with binutils 2.18/gmp/mpfr, also slightly patched)
build=i686-pc-cygwin
host=i686-pc-cygwin
target=i686-pc-mingw32
configure: /obj/gcc.1/i686-pc-cygwin/i686-pc-mingw32/i686-pc-mingw32/libstdc++-v
3/../libgomp/omp.h not found
checking for parallel mode support... no
checking for extra compiler flags for building...
checking for thread model used by GCC... win32
checking for atomic builtins... no
checking for g++ that supports -ffunction-sections -fdata-sections... yes
checking for sys/types.h... (cached) yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking float.h usability... yes
checking float.h presence... yes
checking for float.h... yes
checking for ld version... 21800
checking for ld that supports -Wl,--gc-sections... configure: error: Link tests
are not allowed after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libstdc++-v3] Error 1
make[1]: Leaving directory `/obj/gcc.1/i686-pc-cygwin/i686-pc-mingw32'
make: *** [all] Error 2
I hit this "Link tests are not allowed after GCC_NO_EXECUTABLES."
for target=djgpp too, though in that case, I know I skipped
their wrapper scripts which "preconfigure" some stuff
via environment variables. I'll come back to this much later (days/weeks/months).
I searched the web here some.
It seems in general either:
a merged gcc/newlib or gcc/glibc tree works well
anything else, not to much, but sometimes
e.g. I have built cygwin and solaris targets, with no libc source
or maybe it depends on having a complete sysroot?
Something seems to be off in general though for cross builds. ?
This seems to be a FAQ with no answer. ?
Like, there are too many link tests in configure?
I'll try to just make install w/o completing make, so I get the compiler at least.
I just need mingwin cc1 to make progress building cygwin1.dll with gcc 4.3.1.
Could be my mingwin sys-root is bad. I have something kind of complicated in order to get this far,
and I had to copy the cygwin winsup into the gcc tree, at least for w32api.
Anyway, this is just a random report, like "cross building is a little too difficult".
Perhaps the way to go is bootstrap with
CC='gcc -mno-cygwin -V 3.4.4'
since that has a full mingwin environment.
- Jay