From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] package/exim: remove libnsl linking and fix native tools build
Date: Thu, 17 May 2018 22:19:51 +0200 [thread overview]
Message-ID: <20180517221951.5f101b52@windsurf> (raw)
In-Reply-To: <20180517072140.6432-1-romain.naour@gmail.com>
Hello,
On Thu, 17 May 2018 09:21:39 +0200, Romain Naour wrote:
> glibc now considers its built-in libnsl as being obsolete, and requires
> passing --enable-obsolete-libnsl to have it built and installed. libnsl
> is now provided as a separate project [1], but it isn't packaged yet in
> Buildroot.
>
> In preparation for dropping --enable-obsolete-libnsl from the glibc
> package, this commit ensures that exim doesn't use libnsl. It was
> already the case for uclibc and musl toolchains, so this commit simply
> extends that to make sure libnsl is also not used with glibc toolchains.
>
> Only Exim's nis.so and nisplus.so lookup modules require libnsl,
> but they are not build by default. So we can safely remove -lnsl
> from the Makefile-Linux. If someone want these modules, a new libnsl
> package must be added first to provide nsl library.
>
> This also fixes the following build error on recent distributions where
> libnsl is not installed (e.g. Fedora 28 which has switched to the new
> libnsl library that brings IPV6 support. [2]):
>
> /bin/sh ../scripts/Configure-os.c
> /usr/bin/gcc buildconfig.c
> /usr/bin/ld: cannot find -lnsl
> collect2: error: ld returned 1 exit status
I don't really agree that this patch is the good solution for this
specific problem. The good approach is to not use $(LIBS) at all when
building the buildconfig host program. I've committed this:
https://git.buildroot.org/buildroot/commit/?id=b872d829d092059ae8d5e86115d1515164d01a74
That being said, I believe your change is still useful, but doing it as
a patch to exim like Baruch proposed is a better solution.
Could you rework your patch, and its commit log, according to this ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-05-17 20:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 7:21 [Buildroot] [PATCH v3 1/2] package/exim: remove libnsl linking and fix native tools build Romain Naour
2018-05-17 7:21 ` [Buildroot] [PATCH v3 2/2] Revert "glibc: install the obsolete libnsl" Romain Naour
2018-05-17 7:26 ` [Buildroot] [PATCH v3 1/2] package/exim: remove libnsl linking and fix native tools build Baruch Siach
2018-05-19 19:01 ` Romain Naour
2018-05-17 20:19 ` 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=20180517221951.5f101b52@windsurf \
--to=thomas.petazzoni@bootlin.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