From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] install_copy_toolchain_lib: libnsl.so not found
Date: Wed, 7 Oct 2020 08:37:55 -0400 [thread overview]
Message-ID: <CAMwGMjzs6xf2Ma1CFtVgcBNXtTFYO6y24xrSAZqHx3Ag64pXug@mail.gmail.com> (raw)
In-Reply-To: <20201007070449.GN11021@pengutronix.de>
On Wed, Oct 7, 2020 at 3:05 AM Michael Olbrich <m.olbrich@pengutronix.de> wrote:
>
> On Tue, Oct 06, 2020 at 10:33:00PM -0400, Jon Ringle wrote:
> > On Tue, Oct 6, 2020 at 10:03 PM Jon Ringle <jon@ringle.org> wrote:
> > > On Tue, Oct 6, 2020 at 9:54 PM Jon Ringle <jon@ringle.org> wrote:
> > > >
> > > > I ran into this issue while updating our BSP to ptxdist-2020.09.0 with
> > > > OSELAS.Toolchain-2020.08.0 that I'm not sure how to resolve.
> > > >
> > > [...]
> > > > lib - /opt/OSELAS.Toolchain-2020.08.0/arm-v5te-linux-gnueabi/gcc-10.2.1-glibc-2.32-binutils-2.35-kernel-5.8-sanitized/sysroot-arm-v5te-linux-gnueabi/lib/libresolv-2.32.so
> > > > install_copy_toolchain_lib: libnsl.so not found
> > >
> > > Funny thing is is that the files are there...
> > > [ptx] jringle@-arm-v5te-linux-gnueabi:/opt/OSELAS.Toolchain-2020.08.0/arm-v5te-linux-gnueabi/gcc-10.2.1-glibc-2.32-binutils-2.35-kernel-5.8-sanitized/sysroot-arm-v5te-linux-gnueabi/lib$
> > > ls -l libnsl*
> > > -rwxr-xr-x 1 root root 467220 Oct 2 22:18 libnsl-2.32.so
> > > lrwxrwxrwx 1 root root 14 Oct 2 22:18 libnsl.so.1 -> libnsl-2.32.so
> >
> > >From at `ptxdist bash` shell I get the following:
> > [ptx] jringle@-arm-v5te-linux-gnueabi:~$ arm-v5te-linux-gnueabi-gcc
> > -print-file-name=libresolv.so
> > /opt/OSELAS.Toolchain-2020.08.0/arm-v5te-linux-gnueabi/gcc-10.2.1-glibc-2.32-binutils-2.35-kernel-5.8-sanitized/sysroot-arm-v5te-linux-gnueabi/usr/lib/libresolv.so
> > [ptx] jringle@-arm-v5te-linux-gnueabi:~$ arm-v5te-linux-gnueabi-gcc
> > -print-file-name=libnsl.so
> > libnsl.so
>
> I think that file only exists for binary backwards compatibility. From the
> glibc changelog:
>
> * Remove configure option --enable-obsolete-nsl. libnsl is only built
> as shared library for backward compatibility and the NSS modules "nis"
> and "nisplus" are not built at all and libnsl's headers aren't
> installed. This compatibility is kept only for architectures and ABIs
> that have been added in or before version 2.28. Replacement
> implementations based on TI-RPC, which additionally support IPv6, are
> available from <https://github.com/thkukuk/>. This change does not
> affect the "compat" NSS module, which does not depended on libnsl
> since 2.27 and thus can be used without NIS.
>
> So we need to fix all the packages that still select LIBC_NSL.
>
There are only a few packages that select LIBC_NSL:
jring-t580-gns3 ~/git/ptxdist/rules$ grep -P "\tselect LIBC_NSL" *.in
gpsd.in: select LIBC_NSL
inetutils.in: select LIBC_NSL if INETUTILS_PING
libosip2.in: select LIBC_NSL
lrzsz.in: select LIBC_NSL
portmap.in: select LIBC_NSL
samba.in: select LIBC_NSL
smtpclient.in: select LIBC_NSL
ssmtp.in: select LIBC_NSL
syslogng.in: select LIBC_NSL
Is this simply just a matter of removing these lines?
jring-t580-gns3 ~/git/ptxdist/rules$ sed -i '/\tselect LIBC_NSL/d' *.in
-Jon
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-10-07 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 1:54 Jon Ringle
2020-10-07 2:03 ` Jon Ringle
2020-10-07 2:33 ` Jon Ringle
2020-10-07 7:04 ` Michael Olbrich
2020-10-07 12:37 ` Jon Ringle [this message]
2020-10-28 7:14 ` Michael Olbrich
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=CAMwGMjzs6xf2Ma1CFtVgcBNXtTFYO6y24xrSAZqHx3Ag64pXug@mail.gmail.com \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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