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

[Mumit Khan <khan at nanotech dot wisc dot edu>]

"M. R. Brown" <marcusb@csd.uwm.edu> writes:
> 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...

A long long time ago, I had sent patches to get collect2 working on 
Mingw, but it was not pretty and had retracted it. It doesn't help 
that collect2 is a mess either.  I'm *hoping* that it's still in
the old egcs email archives, otherwise I'll have to start from scratch 
and have to relive the uglyness involved.

What I don't understand is why collect2 is being built at all for
xi86-mingw32 target. I'll look into that.

I agree with Jeff that it's in general wrong to change things just to
make a port work, but in this particular case, that's the only workaround.
Fortunately, collect2 is not currently needed to handle ctor/dtor and EH 
on x86-win32, but that's definitely going to change once we move to
DWARF2 based EH instead of the current SJLJ based EH.

Regards,
Mumit


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