Building collect2 for C?
E. Weddington
eric@ecentral.com
Tue Mar 16 13:31:00 GMT 2004
According to the Internals manual, collect2 "works by linking the program once and looking
through the linker output file for symbols with particular names indicating they are constructor
functions."
In my mind, this implies that collect2 is only necessary for compiling C++, and not necessary
for C. Is this correct?
And if that is correct, is there any real reason why collect2 is attempting to be built when
configuring with?:
../gcc-$version/configure --prefix=$mixedinstalldir --host=mingw32 \
--build=mingw32 --target=m68k-elf \
--enable-languages=c --without-headers --with-newlib --disable-shared --disable-threads \
--with-local-prefix=$mixedinstalldir/m68k-elf
(i.e., configuring with no C++, just C.)
I would also strongly postulate that this happens when --target=avr as well.
This is related to PR #14316:
<http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14316>
because the build fails on collect2.
So, if collect2 really has nothing to do with C, should the fact that it's attempting to be built for
C be considered a bug?
Thanks
Eric Weddington
More information about the Gcc
mailing list