Building collect2 for C?
Ian Lance Taylor
ian@wasabisystems.com
Tue Mar 16 14:59:00 GMT 2004
"E. Weddington" <eric@ecentral.com> writes:
> In my mind, this implies that collect2 is only necessary for compiling C++, and not necessary
> for C. Is this correct?
Yes.
> 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.)
Building collect2 is independent of --enable-languages. I suppose the
Makefile machinery could be changed to not build collect2 when
--enable-languages=c is used. That would probably lead to some other
set of problems, though.
> 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?
I don't think that is the real bug here.
Ian
More information about the Gcc
mailing list