This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug build/13717] New: ../configure --enable-kernel=2.0.0 shouldn't be possible
- From: "ttk448 at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Mon, 20 Feb 2012 23:31:14 +0000
- Subject: [Bug build/13717] New: ../configure --enable-kernel=2.0.0 shouldn't be possible
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13717
Bug #: 13717
Summary: ../configure --enable-kernel=2.0.0 shouldn't be
possible
Product: glibc
Version: 2.14
Status: NEW
Severity: minor
Priority: P2
Component: build
AssignedTo: unassigned@sourceware.org
ReportedBy: ttk448@gmail.com
CC: carlos@systemhalted.org
Classification: Unclassified
Ignoring the advice in README and trying to enable support for very old kernel
versions, it appears to work:
../configure --prefix=/usr/local/glibc_32 \
--enable-kernel=2.0.0 \
--with-cpu=i486 --host=i486-linux-gnu \
CC="gcc -m32 -march=i486" CXX="g++ -m32 -march=i486"
[...]
WARNING: minimum kernel version reset to 2.0.10
[...]
However, when a test programme is statically linked against this glibc and
executed on an old kernel (2.2.x) it fails:
user@newsystem:~ $ file ./prog
./prog: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linked, for GNU/Linux 2.0.10, not stripped
user@oldsystem:~ $ ./prog
set_thread_area failed when setting up thread-local storage
Segmentation fault
So instead I guess ./configure should do something like
WARNING: minimum kernel version reset to 2.6.0
so that the normal "FATAL: kernel too old" error message appears when executed
on any older kernel?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.