All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Simple glibc-based external toolchain support
Date: Wed, 15 Apr 2009 16:03:14 +0200	[thread overview]
Message-ID: <20090415160314.1de1229f@surf> (raw)
In-Reply-To: <20090413221219.0819d500@surf>

Hi,

Any opinion on this ? I'm adding Grant Likely to the Cc: list because
he showed interest in having support for external Glibc toolchains in
Buildroot.

Sincerly,

Thomas

Le Mon, 13 Apr 2009 22:12:19 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :

> xSimple glibc-based external toolchain support
> 
> The current Buildroot works just well with sysrootable glibc
> toolchains, using the external toolchain feature. The only thing that
> needs to be customized is the set of libraries that must be compiled
> to the target.
> 
> The following patch takes a simple approach to making it easier for
> users to use glibc toolchains. It just adds a uClibc/glibc choice in
> the external toolchain menu. Then, depending on that selection, the
> configuration system will choose a sane default value for the library
> files list.
> 
> The other advantage of having a uClibc/glibc choice is that in the
> future, we'll be able to add checks verifying that the external
> toolchain configuration matches the features selected in Buildroot (in
> terms of IPv6, RPC, locales or large file support).
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
>  toolchain/external-toolchain/Config.in |   22 ++++++++++++++++++++--
>  1 file changed, 20 insertions(+), 2 deletions(-)
> 
> Index: buildroot/toolchain/external-toolchain/Config.in
> ===================================================================
> --- buildroot.orig/toolchain/external-toolchain/Config.in
> +++ buildroot/toolchain/external-toolchain/Config.in
> @@ -1,9 +1,24 @@
>  #
>  
>  if BR2_TOOLCHAIN_EXTERNAL
> +choice
> +	prompt "External toolchain C library"
> +	default BR2_TOOLCHAIN_EXTERNAL_UCLIBC
> +
> +config BR2_TOOLCHAIN_EXTERNAL_UCLIBC
> +	bool "uClibc"
> +
> +config BR2_TOOLCHAIN_EXTERNAL_GLIBC
> +	bool "glibc"
> +
> +endchoice
> +
> +menu "Library files"
> +
>  config BR2_TOOLCHAIN_EXTERNAL_LIB_C
>  	string "The core C library from the external toolchain"
> -	default "libc.so.0"
> +	default "libc.so.0" if BR2_TOOLCHAIN_EXTERNAL_UCLIBC
> +	default "libc.so.6" if BR2_TOOLCHAIN_EXTERNAL_GLIBC
>  	help
>  	  Specify the core C shared library found in the external
>  	  toolchain. This is required in addition to any other
> @@ -11,13 +26,16 @@
>  
>  config BR2_TOOLCHAIN_EXTERNAL_LIBS
>  	string "Libraries to copy from the external toolchain"
> -	default "ld-uClibc.so.0 libcrypt.so.0 libdl.so.0 libgcc_s.so
> libm.so.0 libnsl.so.0 libpthread.so.0 libresolv.so.0 librt.so.0
> libutil.so.0"
> +	default "ld-uClibc.so.0 libcrypt.so.0 libdl.so.0 libgcc_s.so
> libm.so.0 libnsl.so.0 libpthread.so.0 libresolv.so.0 librt.so.0
> libutil.so.0" if BR2_TOOLCHAIN_EXTERNAL_UCLIBC
> +	default "ld-linux.so.3 libcrypt.so.1 libdl.so.2
> libgcc_s.so.1 libm.so.6 libnsl.so.1 libpthread.so.0 libresolv.so.2
> librt.so.1 libutil.so.1 libnss_files.so.2" if
> BR2_TOOLCHAIN_EXTERNAL_GLIBC help A space separated list of the
> shared libraries to be copied from the external toolchain into the
> root filesystem. Only the top-level name is needed, i.e. libc.so,
> libpthread.so as the actual shared library symlinked to will be
> copied also. +endmenu
> +
>  config BR2_TOOLCHAIN_EXTERNAL_STRIP
>          bool
>          default y
> 
> 


-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2009-04-15 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 20:12 [Buildroot] Simple glibc-based external toolchain support Thomas Petazzoni
2009-04-15 14:03 ` Thomas Petazzoni [this message]
2009-04-15 14:13   ` Peter Korsgaard
2009-04-15 14:23     ` Thomas Petazzoni
2009-04-15 14:38       ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090415160314.1de1229f@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.