config/kernel.in
author Zoltan Devai <zdevai@gmail.com>
Wed Oct 28 12:03:38 2009 +0100 (2009-10-28)
branch1.5
changeset 1645 01d01185eb18
parent 1499 ff1f40a8f9c1
child 1870 a4c4e51aa541
permissions -rw-r--r--
libc/uClibc: fix building on system with recent glibc

While trying to build a toolchain with ct-ng 1.5.0,
arm-unknown-linux-uclibcgnueabi target,
I get the following error:

[INFO ] Installing C library headers
[EXTRA] Copying sources to build dir
[EXTRA] Applying configuration
[EXTRA] Building headers
[EXTRA] Installing headers
[ERROR] extra/scripts/unifdef.c:209: error: conflicting types for 'getline'
[ERROR] make[2]: *** [extra/scripts/unifdef] Error 1
[ERROR] Build failed in step 'Installing C library headers'

The following patch solves the problem.
(It's a backport of this uClibc commit:
http://git.uclibc.org/uClibc/commit/?id=49e81cada73616864b9b31df0aeb6961c30f5a6e
)

[--SNIP from another mail--]
AFAIK this is a problem since glibc 2.10.
(transplanted from 1ba79f2126df8bd89120899a58f2d0bcc2e9c771)
     1 # Kernel options
     2 
     3 menu "Operating System"
     4 
     5 # Config option used throughout the config and code to determine wether
     6 # we have a kernel or not (there might be different bare metal stuff)...
     7 config BARE_METAL
     8     bool
     9     default n
    10 
    11 # Each target OS (aka kernel) that support shared libraries can select
    12 # this, so the user can decide whether or not to build a shared library
    13 # enabled toolchain
    14 config KERNEL_SUPPORTS_SHARED_LIBS
    15     bool
    16     default n
    17 
    18 config KERNEL
    19     string
    20 
    21 config KERNEL_VERSION
    22     string
    23 
    24 source config.gen/kernel.in
    25 
    26 comment "Common kernel options"
    27 
    28 config SHARED_LIBS
    29     bool
    30     prompt "Build shared libraries"
    31     depends on KERNEL_SUPPORTS_SHARED_LIBS
    32     default y
    33     help
    34       Say 'y' here, unless you don't want shared libraries.
    35       
    36       You might not want shared libraries if you're building for a target that
    37       don't support it (maybe some nommu targets, for example, or bare metal).
    38 
    39 endmenu