config/companion_libs/libelf.in
author Daniel Price <daniel.price@gmail.com>
Tue Nov 20 16:59:17 2012 -0800 (2012-11-20)
changeset 3126 333d3e40cbd1
parent 1873 4477403726db
permissions -rw-r--r--
scripts: refine static linking check to better guide the user

The current mechanism to check if static linking is possible, and the mesage
displayed on failure, can be puzzling to the unsuspecting user.

Also, the current implementation is not using the existing infrastructure,
and is thus difficult to enhance with new tests.

So, switch to using the standard CT_DoExecLog infra, and use four tests to
check for the host compiler:
- check we can run it
- check it can build a trivial program
- check it can statically link that program
- check if it statically link with libstdc++

That should cover most of the problems. Hopefully.

(At the same time, fix a typo in a comment)

Signed-off-by: Daniel Price <daniel.price@gmail.com>
[yann.morin.1998@free.fr: split original patch for self-contained changes]
[yann.morin.1998@free.fr: use steps to better see gcc's output]
[yann.morin.1998@free.fr: commit log]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <163f86b5216fc08c672a.1353459722@nipigon.dssd.com>
Patchwork-Id: 200536
yann@245
     1
# libelf config file
yann@245
     2
yann@245
     3
choice
yann@245
     4
    bool
yann@245
     5
    prompt "libelf version"
yann@1535
     6
# Don't remove next line
yann@1535
     7
# CT_INSERT_VERSION_BELOW
yann@245
     8
yann@1873
     9
config LIBELF_V_0_8_13
yann@1873
    10
    bool
yann@1873
    11
    prompt "0.8.13"
yann@1873
    12
yann@1562
    13
config LIBELF_V_0_8_12
yann@1562
    14
    bool
yann@1562
    15
    prompt "0.8.12"
yann@1562
    16
yann@245
    17
endchoice
yann@245
    18
yann@245
    19
config LIBELF_VERSION
yann@245
    20
    string
yann@1535
    21
# Don't remove next line
yann@1535
    22
# CT_INSERT_VERSION_STRING_BELOW
yann@1873
    23
    default "0.8.13" if LIBELF_V_0_8_13
yann@1562
    24
    default "0.8.12" if LIBELF_V_0_8_12