ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-20 05:17:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
88c8168763
crosstool-ng/config/libc/glibc.in

128 lines
3.0 KiB
Plaintext
Raw Normal View History

Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
# glibc options
kernel: add mingw Add the option to build a cross-compiler for kernel type 'mingw'. The resulting cross-compiler can be used to build applications on a Linux host that can be run on a Windows target. Compiler is build using the mingwrt and w32-api packages aviable from the MinGW project (http://sourceforge.net/projects/mingw). The windows headers (w32-api package) are extracting with the kernel_headers step The libraries and other headers from both packages are build and installed in the various steps of libc Signed-off-by: Bart vdr Meulen <bartvdrmeulen@gmail.com> [yann.morin.1998@anciens.enib.fr: fix kernel headers comment, don't "return 0"] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-07-11 19:36:20 +00:00
# depends on ! MINGW32 && ! BARE_METAL && ARCH_USE_MMU
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
Generate the choice menu for C libraries, the same way arch and kernels are generated. /trunk/kconfig/kconfig.mk | 10 8 2 0 ++++++-- /trunk/scripts/build/libc/glibc.sh | 2 1 1 0 +- /trunk/config/libc/glibc.in | 22 6 16 0 +++++------------- /trunk/config/libc/uClibc.in | 7 6 1 0 +++++- /trunk/config/libc/eglibc.in | 12 11 1 0 +++++++++- /trunk/config/libc.in | 53 4 49 0 +++----------------------------------------- 6 files changed, 36 insertions(+), 70 deletions(-)
2008-10-13 11:23:51 +00:00
config LIBC_glibc
select LIBC_SUPPORT_NPTL
select LIBC_SUPPORT_LINUXTHREADS
help
The de-facto standard for Linux distributions.
Feature-rich, but large... Most usefull for desktop-like systems.
Enhance setting the minimum kernel version glibc will run against. Ideally, eglibc should also benefit for that, but the current code does not set it. /trunk/scripts/build/libc/glibc.sh | 38 33 5 0 +++++++++++++++--- /trunk/config/libc/glibc.in | 4 2 2 0 +- /trunk/config/libc/uClibc.in | 2 2 0 0 + /trunk/config/libc/eglibc.in | 4 2 2 0 +- /trunk/config/libc/glibc-eglibc-common.in | 80 68 12 0 +++++++++++++++++++++++++++++++------ /trunk/config/libc.in | 69 38 31 0 ++++++++++++++++++-------------- 6 files changed, 145 insertions(+), 52 deletions(-)
2008-09-14 18:09:36 +00:00
libc/glibc: move some options around
2009-12-13 21:53:36 +00:00
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
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
choice
bool
prompt "glibc version"
scripts: add new version at top of choice Add new versions at the top of the choice menu, not at the bottom.
2009-09-13 16:38:06 +00:00
# Don't remove next line
# CT_INSERT_VERSION_BELOW
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
libc/glibc: add 2.12.1 and 2.12.2 Signed-off-by: Heiko Zuerker <heiko@zuerker.org>
2010-12-29 18:34:53 +00:00
config LIBC_GLIBC_V_2_12_2
bool
prompt "2.12.2 (EXPERIMENTAL)"
depends on EXPERIMENTAL
config LIBC_GLIBC_V_2_12_1
bool
prompt "2.12.1 (EXPERIMENTAL)"
depends on EXPERIMENTAL
libc/glibc: add 2.11 and 2.11.1
2010-01-30 10:43:12 +00:00
config LIBC_GLIBC_V_2_11_1
bool
prompt "2.11.1 (EXPERIMENTAL)"
depends on EXPERIMENTAL
config LIBC_GLIBC_V_2_11
bool
prompt "2.11 (EXPERIMENTAL)"
depends on EXPERIMENTAL
libc/glibc: add 2.10.1 Woo... It seems the glibc guys finally decided that tarballs were not deprecated, in fact. The patchset was vampirised from Gentoo (kudos, guys!), and applies to glibc+ports, so that's why it's been added as a patchset against ports, not against glibc.
2009-11-13 20:37:18 +00:00
config LIBC_V_2_10_1
bool
prompt "2.10.1 (EXPERIMENTAL)"
depends on EXPERIMENTAL
select LIBC_GLIBC_USE_PORTS
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
config LIBC_V_2_9
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
bool
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
prompt "2.9"
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
config LIBC_V_2_8
Add glibc: 2.5.1 - 2.6 - 2.6.1. Apply the same patches as glibc 2.5: they apply without any problem (except for ridiculously small offsets).
2007-08-11 10:57:18 +00:00
bool
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
prompt "2.8"
Add glibc: 2.5.1 - 2.6 - 2.6.1. Apply the same patches as glibc 2.5: they apply without any problem (except for ridiculously small offsets).
2007-08-11 10:57:18 +00:00
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
config LIBC_V_2_7
Add glibc: 2.5.1 - 2.6 - 2.6.1. Apply the same patches as glibc 2.5: they apply without any problem (except for ridiculously small offsets).
2007-08-11 10:57:18 +00:00
bool
config: mark now old versions as being OBSOLETE These versions are kept for the upcoming release, but they will be removed from the next release if they are not used.
2009-10-28 18:15:50 +00:00
prompt "2.7 (OBSOLETE)"
depends on OBSOLETE
Add glibc: 2.5.1 - 2.6 - 2.6.1. Apply the same patches as glibc 2.5: they apply without any problem (except for ridiculously small offsets).
2007-08-11 10:57:18 +00:00
config LIBC_V_2_6_1
bool
config: mark now old versions as being OBSOLETE These versions are kept for the upcoming release, but they will be removed from the next release if they are not used.
2009-10-28 18:15:50 +00:00
prompt "2.6.1 (OBSOLETE)"
depends on OBSOLETE
Add glibc: 2.5.1 - 2.6 - 2.6.1. Apply the same patches as glibc 2.5: they apply without any problem (except for ridiculously small offsets).
2007-08-11 10:57:18 +00:00
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
config LIBC_V_2_6
Add EXPERIMENTAL glibc-2.7.
2007-10-30 19:18:45 +00:00
bool
config: mark now old versions as being OBSOLETE These versions are kept for the upcoming release, but they will be removed from the next release if they are not used.
2009-10-28 18:15:50 +00:00
prompt "2.6 (OBSOLETE)"
depends on OBSOLETE
Add EXPERIMENTAL glibc-2.7.
2007-10-30 19:18:45 +00:00
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
config LIBC_V_2_5_1
Enable using glibc post 2.8: - retrieve tarballs from FTP/HTTP for glibc 2.7 and older - checkout from CVS for glibc 2.8 and later - add config options for glibc-2_8 and glibc-2_9 /trunk/scripts/build/libc/glibc.sh | 50 39 11 0 ++++++++++++++++++++++++++++++++++---------- /trunk/config/libc/glibc.in | 49 49 0 0 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 88 insertions(+), 11 deletions(-)
2009-01-04 12:46:13 +00:00
bool
config: mark now old versions as being OBSOLETE These versions are kept for the upcoming release, but they will be removed from the next release if they are not used.
2009-10-28 18:15:50 +00:00
prompt "2.5.1 (OBSOLETE)"
depends on OBSOLETE
Enable using glibc post 2.8: - retrieve tarballs from FTP/HTTP for glibc 2.7 and older - checkout from CVS for glibc 2.8 and later - add config options for glibc-2_8 and glibc-2_9 /trunk/scripts/build/libc/glibc.sh | 50 39 11 0 ++++++++++++++++++++++++++++++++++---------- /trunk/config/libc/glibc.in | 49 49 0 0 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 88 insertions(+), 11 deletions(-)
2009-01-04 12:46:13 +00:00
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
config LIBC_V_2_5
Enable using glibc post 2.8: - retrieve tarballs from FTP/HTTP for glibc 2.7 and older - checkout from CVS for glibc 2.8 and later - add config options for glibc-2_8 and glibc-2_9 /trunk/scripts/build/libc/glibc.sh | 50 39 11 0 ++++++++++++++++++++++++++++++++++---------- /trunk/config/libc/glibc.in | 49 49 0 0 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 88 insertions(+), 11 deletions(-)
2009-01-04 12:46:13 +00:00
bool
config: mark now old versions as being OBSOLETE These versions are kept for the upcoming release, but they will be removed from the next release if they are not used.
2009-10-28 18:15:50 +00:00
prompt "2.5 (OBSOLETE)"
depends on OBSOLETE
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
config LIBC_V_2_3_6
bool
prompt "2.3.6 (OBSOLETE)"
depends on OBSOLETE
Enable using glibc post 2.8: - retrieve tarballs from FTP/HTTP for glibc 2.7 and older - checkout from CVS for glibc 2.8 and later - add config options for glibc-2_8 and glibc-2_9 /trunk/scripts/build/libc/glibc.sh | 50 39 11 0 ++++++++++++++++++++++++++++++++++---------- /trunk/config/libc/glibc.in | 49 49 0 0 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 88 insertions(+), 11 deletions(-)
2009-01-04 12:46:13 +00:00
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
endchoice
config LIBC_VERSION
string
scripts: add new version at top of choice Add new versions at the top of the choice menu, not at the bottom.
2009-09-13 16:38:06 +00:00
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
libc/glibc: add 2.12.1 and 2.12.2 Signed-off-by: Heiko Zuerker <heiko@zuerker.org>
2010-12-29 18:34:53 +00:00
default "2.12.2" if LIBC_GLIBC_V_2_12_2
default "2.12.1" if LIBC_GLIBC_V_2_12_1
libc/glibc: add 2.11 and 2.11.1
2010-01-30 10:43:12 +00:00
default "2.11.1" if LIBC_GLIBC_V_2_11_1
default "2.11" if LIBC_GLIBC_V_2_11
libc/glibc: add 2.10.1 Woo... It seems the glibc guys finally decided that tarballs were not deprecated, in fact. The patchset was vampirised from Gentoo (kudos, guys!), and applies to glibc+ports, so that's why it's been added as a patchset against ports, not against glibc.
2009-11-13 20:37:18 +00:00
default "2.10.1" if LIBC_V_2_10_1
Sanitise using glibc cvs exports: - recently, tarballs for glibc 2.8 and 2.9 have appeared on the GNU ftp site - always use a dot in version strings (eg. 2.9, not 2_9) /trunk/scripts/build/libc/glibc.sh | 135 76 59 0 +++++++++++++++++++++++++------------------- /trunk/config/libc/glibc.in | 71 45 26 0 +++++++++++++++-------- 2 files changed, 121 insertions(+), 85 deletions(-)
2009-03-15 20:50:40 +00:00
default "2.9" if LIBC_V_2_9
config: re-order menu entries so that latest versions are at the top It makes better sense to have latest versions at the top of the choice entries.
2009-09-13 15:51:33 +00:00
default "2.8" if LIBC_V_2_8
default "2.7" if LIBC_V_2_7
default "2.6.1" if LIBC_V_2_6_1
default "2.6" if LIBC_V_2_6
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
Reference in New Issue Copy Permalink