This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH - ping] Don't unlink /dev/null on darwin

Hopefully, libgcc will be split out to its own directory in the 4.1
cycle, and will grow its own  The check can then go in
there and will not need to use -o /dev/null.  If you're interested in
helping with this, talk to Paolo Bonzini (cc:ed).

Ouch! :-) I don't think I have enough familiarity with multilibs and the like to split libgcc into its own toplevel directory... It is not like libcpp and fixincludes, surely. Not to mention modifications to the GCC driver that are probably needed for that.

Surely moving libgcc to the toplevel would be a worthwhile goal on its own, and would enable in turn moving multilibbing to the toplevel which is another favorite cleanup of mine. But while toplevel bootstrap could be a first step in that direction, you'd have *target* bootstrapped modules which are not yet supported.

My plans for configury work in 4.1 mostly involved the creation of a common aclocal library in the toplevel's config directory, also to remove the hack whereby fixincludes just uses gcc's aclocal.m4 file.


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