This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more infromation.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: use of fork,pipe and kill in collect2 of cross gcc


I had a similiar situation and someone helped me out on this list :)

Just remove the collect2 assignment in gcc/Makefile after you've
configured:

$(COLLECT2) =

Or something like that, it might be $(USE_COLLECT2) instead.

Does anyone know the purpose of collect2?  If it's removed as a target, it
doesn't break anything, but opting it out of configure.in still adds it to
the makefile...why?

Marcus

On Sat, 6 Nov 1999, Jose Fonseca wrote:

> I'm trying to build a canadian gcc-2.95 cross compiler hosted on mingw32,
> targeted to m68k, on redhat 6.0 linux. The binutils went fine, but the gcc
> fails due to the use of fork and pipe on collect2 (functions not
> available on mingw32).
> Since collect2 is related to the c++ constructor and destructor table,
> isn't possible to build a C-only compiler without it?
> 
>  
> Thanx,
> 	Jose' Fonseca
> 
> 
> ------
> Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
> 
> 
> 



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]