This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, 2005-09-28 at 11:55 -0400, Robert P. J. Day wrote:
brand new gcc-4.0.2 and, from cursory examination of the patches from gcc-4.0.1 and the source code, it looks like:
fix-fixincl.patch Carry forward
Hi, is there a GCC PR for this one?
gcc: * added patches/gcc-4.0.1/fix-fixincl.patch, patches/gcc-gcc-4.1-200507{02,09,16}/fix-fixincl.patch to fix PATH_MAX problem. See http://gcc.gnu.org/PR22541
but not yet in the patch itself, I'll fix that. The problem with it is it might break the ability to move the toolchain after installing it (without using my little app to fix embedded paths).
pr20815-fix.patch Carry forward
According to the GCC bugzilla discussion log: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20815 GCC developpers have been waiting for feedback since 2005-05-18, is there any reason why crossgcc people didn't acknowledge the patch as okay: problem known elsewhere, other...?
No problem, I just haven't gotten around to verifying the fix works. (Haven't been doing much feedback-driven optimization.) - Dan
-- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |