From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] pppd breaks build without libutils
Date: Wed, 28 Sep 2016 18:34:39 +0200 [thread overview]
Message-ID: <20160928163439.GA3622@free.fr> (raw)
In-Reply-To: <20160928105900.55310907@free-electrons.com>
Thomas, All,
On 2016-09-28 10:59 +0200, Thomas Petazzoni spake thusly:
> On Tue, 27 Sep 2016 23:43:25 +0200, Yann E. MORIN wrote:
>
> > Which suddenly rings a bell here: the latest uClibc-ng version, 1.0.18,
> > now is one-lib, i.e. everything merged into libc.so like musl is, so
> > we could get external toolchains which will lack libutil.so because
> > there is no longer such a library now.
> >
> > If uClibc-ng does like musl does, there will be a lot of empty static
> > versions of the libraries, libutil.a, libcrypt.a and so on, but there
> > will no longer be shared variants.
> >
> > We'll have to account for that in our external toolchain handling.
>
> I'm not sure what needs to be handled. We already support musl that
> does this, and it works fine. It should be perfectly transparent to the
> external toolchain handling (except the copying of the shared libraries
> to the target, of course).
That's exactly what I meant: currently, we copy anexplicit set of shared
libraries from external uClibc-based toolchains:
66 ifeq ($(BR2_TOOLCHAIN_EXTERNAL_GLIBC)$(BR2_TOOLCHAIN_EXTERNAL_UCLIBC),y)
67 TOOLCHAIN_EXTERNAL_LIBS += libatomic.so.* libc.so.* libcrypt.so.*
libdl.so.* libgcc_s.so.* libm.so.* libnsl.so.* libresolv.so.*
librt.so.* libutil.so.*
68 ifeq ($(BR2_TOOLCHAIN_EXTERNAL_GLIBC)$(BR2_ARM_EABIHF),yy)
69 TOOLCHAIN_EXTERNAL_LIBS += ld-linux-armhf.so.*
70 else
71 TOOLCHAIN_EXTERNAL_LIBS += ld*.so.*
72 endif
73 ifeq ($(BR2_TOOLCHAIN_HAS_THREADS),y)
74 TOOLCHAIN_EXTERNAL_LIBS += libpthread.so.*
75 ifneq ($(BR2_PACKAGE_GDB)$(BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY),)
76 TOOLCHAIN_EXTERNAL_LIBS += libthread_db.so.*
77 endif # gdbserver
78 endif # ! no threads
79 endif
Now, old uClibc-based toolchains will have those libs, while newer ones
will only have libc.so.* .
This is that which we need to account for.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-09-28 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 16:53 [Buildroot] pppd breaks build without libutils Cassiano Martin
2016-09-25 18:58 ` Thomas Petazzoni
2016-09-25 23:39 ` Cassiano Martin
2016-09-27 21:33 ` Arnout Vandecappelle
2016-09-27 21:43 ` Yann E. MORIN
2016-09-28 8:59 ` Thomas Petazzoni
2016-09-28 16:34 ` Yann E. MORIN [this message]
2016-09-28 16:41 ` Waldemar Brodkorb
2016-09-28 16:47 ` Yann E. MORIN
2016-09-29 9:41 ` Arnout Vandecappelle
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=20160928163439.GA3622@free.fr \
--to=yann.morin.1998@free.fr \
--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