Add support for building toolchains with gcc-4.4 snapshots.
Initial patch by Dmitry PLOTNIKOV: http://sourceware.org/ml/crossgcc/2009-03/msg00053.html
It [the toolchain] uses current ct-ng (nightly snapshot 20090324, latest
release 1.3.2 work also), glibc 2.9 (from CVS), binutils 2.19 and latest
snapshot of GCC 4.4.0 (as of March 20, 2009).
We have successfully built linux kernel 2.6.29 and a lot of other stuff
with this toolchain.
Here's the patch that adds GCC 4.4.0 to the ct-ng menu and enables it to
download a 4.4.0 snapshot from ftp.
Patch was adpated by me, mostly to better fit the configuration layout.
/trunk/scripts/build/cc/gcc.sh | 34 22 12 0 ++++++++++++++++++++++------------
/trunk/config/cc/gcc.in | 35 30 5 0 ++++++++++++++++++++++++++++++-----
2 files changed, 52 insertions(+), 17 deletions(-)
1 # Options specific to crosstool-NG overall behavior
3 comment "crosstool-NG behavior"
7 prompt "Use obsolete features"
10 If you set this to Y, you will be able to select obsolete features.
12 Such obsolete features are the use of old kernel headers, old
17 prompt "Try features marked as EXPERIMENTAL"
20 If you set this to Y, then you will be able to try very experimental
23 Experimental features can be one of:
24 - working, in which case you should tell me it is!
25 - buggy, in which case you could try patching and send me the result
26 - unfinished, in which case you could try hacking it and send me the result
27 - non-existant, in which case you could also try hacking it in and send me
32 prompt "Debug crosstool-NG"
35 Say 'y' here to get some debugging options
39 config DEBUG_PAUSE_STEPS
41 prompt "Pause between every steps"
44 Say 'y' if you intend to attend the build, and want to investigate
45 the result of each steps before running the next one.
47 config DEBUG_CT_SAVE_STEPS
49 prompt "Save intermediate steps"
52 If you say 'y' here, then you will be able to restart crosstool-NG at
55 It is not currently possible to restart at any of the debug facility.
56 They are treated as a whole.
58 See docs/overview.txt for the list of steps.
60 config DEBUG_CT_SAVE_STEPS_GZIP
62 prompt "gzip saved states"
64 depends on DEBUG_CT_SAVE_STEPS
66 If you are tight on space, then you can ask to gzip the saved states
67 tarballs. On the other hand, this takes some longer time...
69 To lose as less time as possible, the gzip process is done with a low
70 compression ratio (-3), which gives roughly 70% gain in size. Going
71 further doesn't gain much, and takes far more time (believe me, I've
72 got figures here! :-) ).
74 config NO_OVERIDE_LC_MESSAGES
76 prompt "Do *not* overide LC_MESSAGES (EXPERIMENTAL)"
77 depends on EXPERIMENTAL
80 By default, crosstool-NG sets and exports LC_ALL=C so that the
81 build.log file contains english messages, that can be read by
82 people most likely to help interpret the logs. If you say N here,
83 and your locale is not an english language, then dissecting your
84 log file will be difficult for most people but you.
86 If you say Y here, then your current locale settings will be used
87 to print messages, instead of plain english.