Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 10/10] toolchain-external: on SuperH, use Sourcery CodeBench 2011.09 by default
Date: Wed, 6 Jun 2012 22:00:28 +0200	[thread overview]
Message-ID: <20120606220028.478baaf9@skate> (raw)
In-Reply-To: <87ehpvsejt.fsf@macbook.be.48ers.dk>

Le Mon, 04 Jun 2012 09:48:38 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> 
>  Thomas> The 2012.03 version of the x86 toolchain uses glibc 2.15, which
>  Thomas> doesn't provide RPC functions. This breaks most packages for now,
>  Thomas> until we package TI-RPC properly.
> 
> Seems like cut'n'paste from patch 9.

Yes :)

> "Most packages" is probably somewhat exaggerated - We have very few
> packages depending on BR2_INET_RPC:
> 
> git grep -l BR2_INET_RPC package/**/Config.in
> package/lmbench/Config.in
> package/netkitbase/Config.in
> package/netkittelnet/Config.in
> package/nfs-utils/Config.in
> package/portmap/Config.in
> 
> Or have you found other packages where we're missing the BR2_INET_RPC
> annotation?

There are some packages that do not depend on BR2_INET_RPC, but that
enable stuff when BR2_INET_RPC is enable. Take for example
package/busybox :-)

For the moment, the external toolchain code assumes that if the
external toolchain uses (e)glibc, then it has RPC support, so it always
enables BR2_INET_RPC. Obviously, this is what is broken, but I'd prefer
to add proper support for TI-RPC to not leave users using modern
toolchains with absolutely no solution for RPC support.

For now, if you choose one of those toolchains, even Busybox does not
build (complains that rpc.h doesn't exist), which explains why I
preferred to not make those toolchains the default ones, until I find
the time to work on TI-RPC integration.

Regards,

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

  reply	other threads:[~2012-06-06 20:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-03 14:04 [Buildroot] [pull request] Pull request for branch for-2012.08/ext-toolchain-updates Thomas Petazzoni
2012-06-03 14:04 ` [Buildroot] [PATCH 01/10] toolchain-external: add Linaro 2012.05 Thomas Petazzoni
2012-06-03 14:04 ` [Buildroot] [PATCH 02/10] toolchain-external: adjust logic to support " Thomas Petazzoni
2012-06-03 14:04 ` [Buildroot] [PATCH 03/10] toolchain-external: add Sourcery CodeBench SuperH 2012.03 Thomas Petazzoni
2012-06-04  7:44   ` Peter Korsgaard
2012-06-06 20:01     ` Thomas Petazzoni
2012-06-05 19:45   ` Thomas De Schampheleire
2012-06-03 14:04 ` [Buildroot] [PATCH 04/10] toolchain-external: add Sourcery CodeBench x86 2012.03 Thomas Petazzoni
2012-06-03 14:04 ` [Buildroot] [PATCH 05/10] toolchain-external: add Blackfin toolchain 2012R1-BETA1 Thomas Petazzoni
2012-06-03 14:04 ` [Buildroot] [PATCH 06/10] toolchain-external: add Sourcery CodeBench MIPS 2011.09 Thomas Petazzoni
2012-06-05 19:43   ` Thomas De Schampheleire
2012-06-03 14:04 ` [Buildroot] [PATCH 07/10] toolchain-external: remove Sourcery CodeBench ARM 2009q3 Thomas Petazzoni
2012-06-05 19:44   ` Thomas De Schampheleire
2012-06-03 14:04 ` [Buildroot] [PATCH 08/10] toolchain-external: remove Linaro 2012.01 Thomas Petazzoni
2012-06-03 14:04 ` [Buildroot] [PATCH 09/10] toolchain-external: on i386/x86_64, use Sourcery CodeBench 2011.09 by default Thomas Petazzoni
2012-06-03 14:04 ` [Buildroot] [PATCH 10/10] toolchain-external: on SuperH, " Thomas Petazzoni
2012-06-04  7:48   ` Peter Korsgaard
2012-06-06 20:00     ` Thomas Petazzoni [this message]
2012-07-22 16:24 ` [Buildroot] [pull request] Pull request for branch for-2012.08/ext-toolchain-updates Thomas Petazzoni

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=20120606220028.478baaf9@skate \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox