Get rid of the proxy settings, once and for all.
They have nothing to do in here, just let the user
configure his/her system appropriately.
-------- diffstat follows --------
/trunk/scripts/build/libc/eglibc.sh | 1 0 1 0 -
/trunk/scripts/functions | 100 0 100 0 -----------------------------
/trunk/config/global/download.in | 148 0 148 0 -------------------------------------------
3 files changed, 249 deletions(-)
2 # depends on ! BARE_METAL
5 select LIBC_SUPPORT_NPTL
6 select LIBC_SUPPORT_LINUXTHREADS
8 The de-facto standard for Linux distributions.
9 Feature-rich, but large... Most usefull for desktop-like systems.
13 prompt "glibc version"
17 prompt "2.3.6 (OBSOLETE)"
48 # CT_INSERT_VERSION_ABOVE
49 # Don't remove above line!
53 prompt "'latest' snapshot (EXPERIMENTAL)"
54 depends on EXPERIMENTAL
58 prompt "<specific date> (EXPERIMENTAL)"
59 depends on EXPERIMENTAL
65 prompt "Enter date (YYYYMMDD)" if LIBC_V_date
66 default "latest" if LIBC_V_LATEST
67 default "2.3.6" if LIBC_V_2_3_6
68 default "2.4" if LIBC_V_2_4
69 default "2.5" if LIBC_V_2_5
70 default "2.5.1" if LIBC_V_2_5_1
71 default "2.6" if LIBC_V_2_6
72 default "2.6.1" if LIBC_V_2_6_1
73 default "2.7" if LIBC_V_2_7
74 default "2.8" if LIBC_V_2_8
75 default "2.9" if LIBC_V_2_9
76 # CT_INSERT_VERSION_STRING_ABOVE
77 # Don't remove above line!
81 prompt "Retrieval method"
82 default LIBC_GLIBC_TARBALL
84 config LIBC_GLIBC_TARBALL
86 prompt "Released tarball"
88 Until end of Februrary 2009, there was no tarball for glibc releases
89 2.8 and later. This was intentional.
91 Then, all of a sudden, tarballs for those releases have appeared at the
92 traditional download place (ftp.gnu.org).
94 Some of the glibc people argue that fixes are committed to the maintenance
95 branch, and thus it is the best plac e to retrieve the glibc from.
96 On the other hand, it might be preferable to always generate a toolchain
97 using a known code-base, so the toolchain can be reproducible.
99 For version prior to 2.8, tarballs were readily available.
101 If you want your toolchain to really be reproducible, say 'Y' here.
102 If you can live with a moving code-base, look at the other choice
105 config LIBC_GLIBC_CVS
107 prompt "CVS checkout"
109 See the help for the entry "Released tarball", above.
111 If you can live with a moving code-base, say 'Y' here.
112 If you want your toolchain to really be reproducible, look at the
113 choice entry "Released tarball from FTP", above.
117 config LIBC_GLIBC_CVS_date
119 prompt "checkout as of date"
122 The date, in ISO-8601 format, at which to check out the repository.
124 endif # LIBC_GLIBC_CVS
126 #config LIBC_GLIBC_SNAPSHOT
128 # prompt "Use latest nightly snapshot"
130 # See the help for the entry "Released tarball", above.
132 # If you can live with a moving code-base, say 'Y' here.
133 # If you want your toolchain to really be reproducible, look at the
134 # choice entry "Released tarball from FTP", above.