This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Sun, Sep 6, 2009 at 9:06 AM, Yann E. MORIN<yann.morin.1998@anciens.enib.fr> wrote: > >> (*) I then couldn't withstand the temptation to actually run a >> statically compiled binary on a Ubuntu 8.10 machine with a x86_64 >> 2.6.27 kernel. This triggered a "FATAL: Kernel too old" error in >> __libc_start_main. It used to be that Linux provided binary >> compatibility for static binaries; but those days are long past, it >> seems. Or is there a way to tell ct-ng to build a compiler/library >> whose static binaries will run on all kernels? Going through >> menuconfig, it appears you had to decide on a kernel version? > > Look at the option: > ?C-library ?--> > ?Minimum supported kernel version ?--> > ? ?( ) Let ./configure decide > ? ?(X) Same as kernel headers (default) > ? ?( ) Specific kernel version > > This means that glibc is configured at build-time to enable (or disable) > support for old kernels, by including (or ommiting) certain functions > and/or code paths. By default, crosstool-NG configure glibc to not include > support for kernels older than the version of the headers being used to > build the toolchain. You can override this by choosing one of the two other > options, above. > Can you clarify what you mean by "one of the two others options"? Choosing "Let ./configure decide" and "Specific kernel version" will enable support for older kernels? That's not intuitive. - Godmar -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |