ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-18 20:37:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

libc/glibc: move some options around

Browse Source
This commit is contained in:
Yann E. MORIN" 2009-12-13 22:53:36 +01:00
parent c5462c814f
commit 5280cd71be
1 changed files with 28 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
config/libc/glibc.in
View File

@ -8,6 +8,34 @@ config LIBC_glibc
The de-facto standard for Linux distributions.
Feature-rich, but large... Most usefull for desktop-like systems.
choice
bool
prompt "Retrieval method"
default LIBC_GLIBC_TARBALL
config LIBC_GLIBC_TARBALL
bool
prompt "Released tarball"
help
Until end of Februrary 2009, there was no tarball for glibc releases
2.8 and later. This was intentional.
Then, all of a sudden, tarballs for those releases have appeared at the
traditional download place (ftp.gnu.org).
Some of the glibc people argue that fixes are committed to the maintenance
branch, and thus it is the best plac e to retrieve the glibc from.
On the other hand, it might be preferable to always generate a toolchain
using a known code-base, so the toolchain can be reproducible.
For version prior to 2.8, tarballs were readily available.
If you want your toolchain to really be reproducible, say 'Y' here.
If you can live with a moving code-base, look at the other choice
entries, below.
endchoice
choice
bool
prompt "glibc version"
@ -85,31 +113,3 @@ config LIBC_VERSION
default "2.5.1" if LIBC_V_2_5_1
default "2.5" if LIBC_V_2_5
default "2.3.6" if LIBC_V_2_3_6
choice
bool
prompt "Retrieval method"
default LIBC_GLIBC_TARBALL
config LIBC_GLIBC_TARBALL
bool
prompt "Released tarball"
help
Until end of Februrary 2009, there was no tarball for glibc releases
2.8 and later. This was intentional.
Then, all of a sudden, tarballs for those releases have appeared at the
traditional download place (ftp.gnu.org).
Some of the glibc people argue that fixes are committed to the maintenance
branch, and thus it is the best plac e to retrieve the glibc from.
On the other hand, it might be preferable to always generate a toolchain
using a known code-base, so the toolchain can be reproducible.
For version prior to 2.8, tarballs were readily available.
If you want your toolchain to really be reproducible, say 'Y' here.
If you can live with a moving code-base, look at the other choice
entries, below.
endchoice