|
osdir.com mailing list archive |
|
Subject: Re: GCC 4.3.0 build? - msg#00007List: linux.lfs.clfs.develI had to switch to using a sysroot-style toolchain build; and I skipped most of the specs adjustments, trusting that the sysroot machinery would take care of ensuring that the cross-toolchain is building and linking things properly. I'm not sure that's a good thing to trust. My questions at this point are: (a) is anyone interested in details of how I did it, either to reproduce the work or review it for correctness? (b) would it be worthwhile to prepare patches to the CLFS book based on these changes? And, if so, what's the most appropriate way to submit them? Cheers, bn -- Brett Neumeier (bneumeier@xxxxxxxxx) _______________________________________________ Clfs-dev mailing list Clfs-dev@xxxxxxxxxxxxxxxxxxx http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org Thread at a glance:
Previous Message by Date: click to view message previewRe: GCC 4.3.0 build?once you've figured out the solution can you please post in this thread what the problem and the solution are? I'm interested in gcc-4.3.0 but don't have the time to join irc. Sure. Here's the deal (and thank you again tooly for your assistance!).There are two changes to section 5.7 (cross gcc static) needed for GCC 4.3.0.First -- the cross_search_paths patch is no longer needed, since it is incorporated into upstream GCC now; and the branch_update patch from 4.2.2 is also unneeded. Second -- in 4.3.0, the gcc developers switched from autoconf 2.13 (or something like that) to autoconf 2.59. As a result, the configure command should specify --build=$CLFS_HOST instead of --host=$CLFS_HOST.The specs and posix patches also need to be respun for 4.3.0 but that is not particularly challenging. (If anyone is interested I can post the patches I used, here or elsewhere). Cheers,bn-- Brett Neumeier (bneumeier@xxxxxxxxx) _______________________________________________ Clfs-dev mailing list Clfs-dev@xxxxxxxxxxxxxxxxxxx http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org Previous Message by Thread: click to view message previewRe: GCC 4.3.0 build?once you've figured out the solution can you please post in this thread what the problem and the solution are? I'm interested in gcc-4.3.0 but don't have the time to join irc. Sure. Here's the deal (and thank you again tooly for your assistance!).There are two changes to section 5.7 (cross gcc static) needed for GCC 4.3.0.First -- the cross_search_paths patch is no longer needed, since it is incorporated into upstream GCC now; and the branch_update patch from 4.2.2 is also unneeded. Second -- in 4.3.0, the gcc developers switched from autoconf 2.13 (or something like that) to autoconf 2.59. As a result, the configure command should specify --build=$CLFS_HOST instead of --host=$CLFS_HOST.The specs and posix patches also need to be respun for 4.3.0 but that is not particularly challenging. (If anyone is interested I can post the patches I used, here or elsewhere). Cheers,bn-- Brett Neumeier (bneumeier@xxxxxxxxx) _______________________________________________ Clfs-dev mailing list Clfs-dev@xxxxxxxxxxxxxxxxxxx http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org Loading Comments...
|
|
