diff options
author | Mike Frysinger <vapier@gentoo.org> | 2022-02-07 12:57:29 +0300 |
---|---|---|
committer | Mike Frysinger <vapier@gentoo.org> | 2022-02-10 04:23:12 +0300 |
commit | 462d6942f6be6addbf0a977af366b421810738bb (patch) | |
tree | ecf5203b15f077233a9fd4c688342576d998a6be /newlib/README | |
parent | 492e5fe8b0863e15ffd5a269e42b60fabfc5f5db (diff) |
newlib: drop i?86-pc-linux-* target support
This was added 20+ years ago. It seems to have very few (or no users)
as it only works on 32-bit x86 GNU/Linux (i.e. glibc) systems, and even
then only with old versions of glibc. It hasn't compiled in at least 5
years, but most likely been broken for more like 15 years -- it relies
on internal glibc APIs (like linuxthreads), and that code has changed
and been deleted significantly since.
This single target ends up dragging in a lot of non-trivial code that is
hard to keep working, and currently impossible to verify -- the libtool
and iconvdata and sys/linux/ code isn't used by anything else, but ends
up touching just about every build file in the tree. Punt the target so
we can start stripping out all these unique code paths.
This commit by itself just disables the target. We'll start deleting the
individual unused pieces in followups.
Diffstat (limited to 'newlib/README')
-rw-r--r-- | newlib/README | 34 |
1 files changed, 0 insertions, 34 deletions
diff --git a/newlib/README b/newlib/README index c025cb38d..aa48b246f 100644 --- a/newlib/README +++ b/newlib/README @@ -508,40 +508,6 @@ need to add the other targets you're testing to the case statement. Now type make check-target-newlib in the top-level build directory to run the testsuite. -Shared newlib -============= - -newlib uses libtool when it is being compiled natively (with ---target=i[34567]86-pc-linux-gnu) on an i[34567]86-pc-linux-gnu -host. This allows newlib to be compiled as a shared library. - -To configure newlib, do the following from your build directory: - -$(source_dir)/src/configure --with-newlib --prefix=$(install_dir) - -configure will recognize that host == target == -i[34567]86-pc-linux-gnu, so it will tell newlib to compile itself using -libtool. By default, libtool will build shared and static versions of -newlib. - -To compile a program against shared newlib, do the following (where -target_install_dir = $(install_dir)/i[34567]86-pc-linux-gnu): - -gcc -nostdlib $(target_install_dir)/lib/crt0.o progname.c -I $(target_install_dir)/include -L $(target_install_dir)/lib -lc -lm -lgcc - -To run the program, make sure that $(target_install_dir)/lib is listed -in the LD_LIBRARY_PATH environment variable. - -To create a static binary linked against newlib, do the following: - -gcc -nostdlib -static $(target_install_dir)/lib/crt0.o progname.c -I $(target_install_dir)/include -L $(target_install_dir)/lib -lc -lm - -libtool can be instructed to produce only static libraries. To build -newlib as a static library only, do the following from your build -directory: - -$(source_dir)/src/configure --with-newlib --prefix=$(install_dir) --disable-shared - Regenerating Configuration Files ================================ |