[PATCH] Re: How to disable toplevel fixincludes?

[Aaron W. LaFramboise]

Paolo Bonzini wrote:

>>With the recent fixincludes reorganization, bootstrap now attempts to
>>build fixincludes on i686-pc-mingw32.  Like collect2, fixincludes
>>contains some fairly unrepetant Unixisms, and can not be trivially
>>changed to build on Windows.
> 
> Is this true for two-process fixincludes too?  (Can you try "make 
> twoprocess" from the fixincludes directory?)

I have attached a patch that fixes some obvious portability problems
with fixincludes.  However, both the normal build and the two-process
build of fixincludes seem to require fork(), something that Windows just
doesn't have.  Someone (?) is working on adding process chaining of some
sort to libiberty to be used by collect2, and I would guess that is also
the proper thing to use here.

Aaron W. LaFramboise

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gcc-mainline-20040912-fixincludes.patch
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20040914/0fa01bdd/attachment.ksh>