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

To: "M. R. Brown" <marcusb at csd dot uwm dot edu>
Subject: Re: use of fork,pipe and kill in collect2 of cross gcc
From: Jeffrey A Law <law at cygnus dot com>
Date: Mon, 08 Nov 1999 07:28:32 -0700
cc: Jose Fonseca <em96115 at fe dot up dot pt>, crossgcc at sourceware dot cygnus dot com
Reply-To: law at cygnus dot com

  In message <Pine.OSF.3.96.991108081825.6842A-100000@alpha3.csd.uwm.edu>you wr
ite:
  > 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?
Yes it will break things..   It's there for a reason.  In particular removing
it is likely to break exception handling, and ctors/dtors on some targets.

Please don't ever suggest removing something when you do not understand wha
its purpose is.

jeff


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

Follow-Ups:
- Re: use of fork,pipe and kill in collect2 of cross gcc
  - From: M. R. Brown

References:
- Re: use of fork,pipe and kill in collect2 of cross gcc
  - From: M. R. Brown

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