From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/exim: fix build error with external arc toolchain due to missing libnsl
Date: Sun, 29 Mar 2015 14:16:52 +0200 [thread overview]
Message-ID: <20150329141652.7e3fcf79@free-electrons.com> (raw)
In-Reply-To: <1427574832-20384-1-git-send-email-bernd.kuhls@t-online.de>
Bernd, Alexey,
On Sat, 28 Mar 2015 21:33:52 +0100, Bernd Kuhls wrote:
> Fixes
> http://autobuild.buildroot.net/results/331/331ed781b422448205fb9e7c9730ec0c438d6306/
> http://autobuild.buildroot.net/results/402/402d64965ac7ac6e1d4e1990080394958802fe8c/
> http://autobuild.buildroot.net/results/960/9605bac2972d3e3d3fb91947ae6921e89210247b/
> http://autobuild.buildroot.net/results/6b6/6b61ea80a3a6dcead233c4b408eba8b8d647e841/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/exim/exim.mk | 8 ++++++++
> 1 file changed, 8 insertions(+)
Applied, thanks.
Alexey, could you please enable UCLIBC_HAS_LIBNSL_STUB=y in the uClibc
configuration used for the ARC external toolchains? Generally speaking,
if you could have a look at the differences between the uClibc
configuration you're using, and the default Buildroot one, it would be
useful. We cannot support all the little variations of the uClibc
configuration, so if you could use a configuration that is at least a
super-set of the features enabled in the uClibc configuration used by
default in Buildroot, it would really make things easier.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-03-29 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 20:33 [Buildroot] [PATCH 1/1] package/exim: fix build error with external arc toolchain due to missing libnsl Bernd Kuhls
2015-03-29 12:16 ` Thomas Petazzoni [this message]
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=20150329141652.7e3fcf79@free-electrons.com \
--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