From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 20/20] external-toolchain: add Sourcery CodeBench ARM 2012.03
Date: Wed, 22 Aug 2012 15:51:22 +0200 [thread overview]
Message-ID: <20120822155122.2cf57b60@skate> (raw)
In-Reply-To: <CAHkwnC8sEW3NSwCKpfMwbGWbJgVQ_zKKga5kRduutvFUnPKNqg@mail.gmail.com>
Le Wed, 22 Aug 2012 10:46:49 +0200,
Fabio Porcedda <fabio.porcedda@gmail.com> a ?crit :
> I've discovered only today that this toolchain has already the rpc library...
> so the test fail because the rpc/rpc.h header it's present.
>
> getting-started.pdf:
> A.1.1. Changes in Sourcery CodeBench Lite 2012.03-57
> ...
> RPC library functions. GLIBC has been changed so that programs may
> again be built to use its
> RPC library functions. The ability to build programs using these
> functions had previously been dis-
> abled.
Argh, so they brought back RPC support into glibc... sigh.
> IMHO there are two solutions:
> a) update this patch to enable the BR2_TOOLCHAIN_HAS_NATIVE_RPC
> b) apply as is directly on the next branch and change accordingly the commit:
> commit 80f89c34315be739c52935f1b0606dc5531e6eb3
> Author: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Date: Sat Aug 11 18:50:42 2012 +0200
>
> toolchain-external: improve glibc support to test availability of RPC
>
> Let me know which one solution you prefer.
I'm a bit hesitant here. If newer glibc toolchains re-include the RPC
support, is it worth supporting libtirpc and do all the changes I had
proposed? Or should we just give up and say we only support
glibc toolchains that include RPC support? Maybe not nice, since
libtirpc brings quite a few features compared to in-toolchain RPC
support.
Comments from others?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-08-22 13:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 17:40 [Buildroot] [RFC v1] Rework of RPC support to handle glibc >= 2.14 and libtirpc Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 01/20] uClibc: use the Buildroot toolchain options instead of the hidden common options Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 02/20] toolchain-crosstool-ng: use the Crosstool-ng config options instead of the common hidden ones Thomas Petazzoni
2012-08-12 15:05 ` Yann E. MORIN
2012-08-12 15:26 ` Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 03/20] Rename BR2_INET_RPC to BR2_TOOLCHAIN_HAS_NATIVE_RPC Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 04/20] toolchain-external: improve glibc support to test availability of RPC Thomas Petazzoni
2012-08-12 15:18 ` Yann E. MORIN
2012-08-22 8:20 ` Fabio Porcedda
2012-08-22 14:00 ` Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 05/20] libtirpc: new package Thomas Petazzoni
2012-08-12 15:43 ` Yann E. MORIN
2012-08-28 17:34 ` Arnout Vandecappelle
2012-08-28 17:39 ` Arnout Vandecappelle
2012-08-11 17:40 ` [Buildroot] [PATCH 06/20] busybox: add support to link against libtirpc when available Thomas Petazzoni
2012-08-12 15:51 ` Yann E. MORIN
2012-08-28 17:51 ` Arnout Vandecappelle
2012-08-11 17:40 ` [Buildroot] [PATCH 07/20] netkitbase: convert to the generic-package infrastructure Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 08/20] netkitbase: mark as deprecated Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 09/20] netkittelnet: convert to generic-package infrastructure Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 10/20] netkittelnet: mark as deprecated Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 11/20] lmbench: add support to use libtirpc when available Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 12/20] nfs-utils: add support to use RPC support from libtirpc Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 13/20] rpcbind: new package Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 14/20] portmap: mention that rpcbind is the project that superseds portmap Thomas Petazzoni
2012-08-12 15:55 ` Yann E. MORIN
2012-08-13 17:35 ` Thomas Petazzoni
2012-08-13 18:26 ` Gustavo Zacarias
2012-08-11 17:40 ` [Buildroot] [PATCH 15/20] quota: add support to use RPC support from libtirpc Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 16/20] samba: unconditionally enable --with-sys-quotas Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 17/20] xinetd: add support to use RPC support from libtirpc Thomas Petazzoni
2012-08-12 15:58 ` Yann E. MORIN
2012-08-14 13:07 ` Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 18/20] toolchain-external: add Sourcery CodeBench SuperH 2012.03 Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 19/20] toolchain-external: add Sourcery CodeBench x86 2012.03 Thomas Petazzoni
2012-08-28 18:15 ` Arnout Vandecappelle
2012-08-28 20:55 ` Thomas Petazzoni
2012-08-11 17:40 ` [Buildroot] [PATCH 20/20] external-toolchain: add Sourcery CodeBench ARM 2012.03 Thomas Petazzoni
2012-08-22 8:46 ` Fabio Porcedda
2012-08-22 13:51 ` Thomas Petazzoni [this message]
2012-08-22 14:36 ` Yann E. MORIN
2012-08-28 22:45 ` Arnout Vandecappelle
2012-08-29 9:37 ` Yann E. MORIN
2012-08-28 22:34 ` [Buildroot] [RFC v1] Rework of RPC support to handle glibc >= 2.14 and libtirpc Arnout Vandecappelle
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=20120822155122.2cf57b60@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 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.