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: Jeffrey A Law <law at cygnus dot com>
Subject: Re: use of fork,pipe and kill in collect2 of cross gcc
From: "M. R. Brown" <marcusb at csd dot uwm dot edu>
Date: Mon, 8 Nov 1999 12:02:18 -0600 (CST)
cc: Jose Fonseca <em96115 at fe dot up dot pt>, crossgcc at sourceware dot cygnus dot com

I was responding to the question of the _mingw32_ target, which doesn't
support fork, etc.  The question I asked was also in reference to the
_mingw32_ target, sorry for any misunderstanding.  I only "suggested" it
because right now the only way to build a native mingw32 gcc is to
remove the collect2 target.  If you have another way, enlighten me :)
This has come up before...

Marcus

On Mon, 8 Nov 1999, Jeffrey A Law wrote:

> 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: Mumit Khan

References:
- Re: use of fork,pipe and kill in collect2 of cross gcc
  - From: Jeffrey A Law

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