From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Insufficient RPC options for crosstool-ng toolchain
Date: Tue, 5 Feb 2013 00:49:38 +0100 [thread overview]
Message-ID: <20130205004938.09cc877e@skate> (raw)
In-Reply-To: <511046BF.1070902@gmail.com>
Dear Shawn J. Goff,
On Mon, 04 Feb 2013 18:39:43 -0500, Shawn J. Goff wrote:
> No problems, it just that when I started down the path, I thought it
> would be just an option, but there turned out to be this whole
> toolchain-checked thing behind it, so I wanted to make sure that is
> what's wanted before I do it.
Yann will confirm or infirm, but since the glibc version selection is
not done in Buildroot, but directly inside Crosstool-NG, there is no
way for Buildroot to automatically now if the glibc of the toolchain
will have RPC support or not. Therefore, the only practical solution is
to have an option similar to the one we have in external toolchain,
where we leave it to the user to say whether the toolchain generated by
Crosstool-NG will have RPC support or not.
However, I haven't thought in detail about the detailed impact on the
implementation.
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:[~2013-02-04 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 22:36 [Buildroot] Insufficient RPC options for crosstool-ng toolchain Shawn J. Goff
2013-02-04 23:32 ` Thomas Petazzoni
2013-02-04 23:39 ` Shawn J. Goff
2013-02-04 23:49 ` Thomas Petazzoni [this message]
2013-02-06 22:06 ` Yann E. MORIN
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=20130205004938.09cc877e@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