Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/exim: remove libnsl linking with Glibc.
Date: Tue, 1 May 2018 22:37:46 +0200	[thread overview]
Message-ID: <20180501223746.1ed2eddf@windsurf.home> (raw)
In-Reply-To: <8328c7c8-4c79-20d7-6e7c-425fe3d9fcf7@gmail.com>

Hello,

On Tue, 1 May 2018 22:19:13 +0200, Romain Naour wrote:

> Le 01/05/2018 ? 22:12, Thomas Petazzoni a ?crit?:
> > Hello,
> > 
> > On Tue,  1 May 2018 22:05:07 +0200, Romain Naour wrote:  
> >> libnsl has been deprecated from Glibc and no other libc provide it.
> >> Also there is no libnsl package in Buildroot yet, so remove -lnsl for
> >> all toolchains.
> >>
> >> libnsl is now a library that can be packaged later if needed. [1]
> >>
> >> Note: Fedora 28 has switched to the new libnsl library that bring
> >> IPV6 support. [2]
> >>
> >> [1] https://github.com/thkukuk/libnsl.git
> >> [2] https://fedoraproject.org/wiki/Changes/NISIPv6  
> > 
> > This commit log doesn't really explain the motivation for the change.
> > What is the ultimate goal here ?  
> 
> The motivation is to remove libnsl provided by Glibc. Since the new libnsl is
> not packaged in Buildroot. Remove -lnsl from the exim Makefile.

I think the explanation in the commit log should be improved then.

Perhaps something like:

""""
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, 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.
""""

Does this capture the problem properly ?

Remains some questions though: why is exim linking with libnsl in the
first place ? Doesn't it use symbols from this library ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-05-01 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 20:05 [Buildroot] [PATCH 1/2] package/exim: remove libnsl linking with Glibc Romain Naour
2018-05-01 20:05 ` [Buildroot] [PATCH 2/2] Revert "glibc: install the obsolete libnsl" Romain Naour
2018-05-01 20:09   ` Romain Naour
2018-05-01 20:12 ` [Buildroot] [PATCH 1/2] package/exim: remove libnsl linking with Glibc Thomas Petazzoni
2018-05-01 20:19   ` Romain Naour
2018-05-01 20:37     ` Thomas Petazzoni [this message]
2018-05-04 20:54       ` Romain Naour

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=20180501223746.1ed2eddf@windsurf.home \
    --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