config/kernel/bare-metal.in
author Anthony Foiani <anthony.foiani@gmail.com>
Thu Oct 07 22:37:06 2010 +0200 (2010-10-07)
changeset 2138 2242d87c5404
parent 890 6227df6bbb79
child 2444 896cb0d36c1a
permissions -rw-r--r--
scripts: always create lib32 and lib64 symlinks

Unconditionally create the lib32 -> lib/ and lib64 -> lib/ symlinks.

This is reportedly a fix to build a toolchain for a 32-bit target on
a 'pure' 64-bit host (eg. on Fedora FC12, host libs are in lib64/,
and there is no lib -> lib64 symlink, as we can see on other distors,
as Debian). As gcc only puts static host lib in lib64/ (along with
target files in subdirs), we can safely create the symlinks.

Also note that the symlinks are summarily removed at the end
of the build.

Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
[Yann E. MORIN: fix a comment, rephrase the commit log]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@861
     1
# Bare metal config options
yann@861
     2
yann@861
     3
config KERNEL_bare_metal
yann@861
     4
    select BARE_METAL
yann@861
     5
    help
yann@883
     6
      'Bare metal' refers to those programs that run without any kernel.
yann@861
     7
      
yann@861
     8
      You probably want to say 'y' here if you plan to use your compiler
yann@883
     9
      to build bootloaders. It is not yet suitable to build Linux kernels,
yann@883
    10
      though, because the APCI stuff relies on the target C library headers
yann@883
    11
      being available?!?!...