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] RPC support for modern (e)glibc toolchains
Date: Wed, 27 Jun 2012 10:25:51 +0200	[thread overview]
Message-ID: <20120627102551.173d9347@skate> (raw)
In-Reply-To: <20120627000701.506f534e@skate>

Le Wed, 27 Jun 2012 00:07:01 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :

> However, this status has changes since (e)glibc 2.14 (released in May
> 2011) and its subsequent version 2.15 (released in March 2012). The
> RPC support has been completely removed from (e)glibc, and the
> developers recommend to use the tirpc library instead. Apparently,
> tirpc offers additional benefits over the traditional RPC support that
> was part of (e)glibc, such as improved IPv6 support.
> 
> Since quite a while, Crosstool-NG allows to produce toolchains with
> (e)glibc 2.14/2.15, and since 2012.03, Sourcery CodeBench toolchains
> are also using (e)glibc 2.15. None of those toolchains have RPC
> support, but Buildroot for the moment assumes that they do since they
> are glibc-based.

Just to add a quick bit of information on this: glibc 2.16 should be
released early July, and they did some changes related to the RPC mess.
According to the glibc NEWS file, for version 2.16:

  73 * New configure option --enable-obsolete-rpc makes the deprecated RPC
  74   headers and functions available at compile time as they were before
  75   version 2.14.  This option will be removed at some time in the future
  76   after the TI-RPC library becomes fully sufficient for the needs of
  77   existing applications.

So it means that from now on, we will probably have some glibc
toolchains with RPC support included, and some other glibc toolchains
without RPC support included.

Best regards,

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

  parent reply	other threads:[~2012-06-27  8:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 22:07 [Buildroot] RPC support for modern (e)glibc toolchains Thomas Petazzoni
2012-06-27  2:55 ` [Buildroot] RPC and Busybox Michael J. Hammel
2012-06-27  7:18   ` Thomas Petazzoni
2012-06-27  8:25 ` Thomas Petazzoni [this message]
2012-06-27 11:00 ` [Buildroot] RPC support for modern (e)glibc toolchains Gustavo Zacarias
2012-06-27 12:53   ` Thomas Petazzoni
2012-06-28 11:51     ` Gustavo Zacarias
2012-06-28 11:57       ` Thomas Petazzoni
2012-06-28 12:06         ` Gustavo Zacarias
2012-06-30 12:24     ` Arnout Vandecappelle
2012-07-03 19:48       ` Thomas Petazzoni
2012-07-03 20:37         ` 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=20120627102551.173d9347@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