From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] libintl static linking issues - yet another spin
Date: Mon, 3 Apr 2017 14:30:44 +0200 [thread overview]
Message-ID: <20170403123044.GI5361@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170403141147.0376b102@free-electrons.com>
Hi,
Thomas Petazzoni wrote,
> Hello,
>
> On Mon, 3 Apr 2017 13:25:11 +0200, Arnout Vandecappelle wrote:
>
> > Would the libintl from uClibc make it easier to do static linking, i.e. is it
> > in libc or in a separate libintl library?
>
> It is in libc I believe, since uClibc now has everything in libc. So it
> does make things a *lot* easier for static linking.
Yes, it is included in libc when activated.
It was added to allow packages which use libintl to at least
be usable in a limited way (as stub.)
It might help in some cases, but surely not in all cases.
gru?
Waldemar
next prev parent reply other threads:[~2017-04-03 12:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 21:53 [Buildroot] Patchwork cleanup, 10 patches to look at Thomas Petazzoni
2017-03-27 12:35 ` Arnout Vandecappelle
2017-03-27 13:43 ` Andrey Smirnov
2017-03-28 20:25 ` Thomas Petazzoni
2017-04-03 10:42 ` [Buildroot] libintl static linking issues - yet another spin Arnout Vandecappelle
2017-04-03 11:01 ` Thomas Petazzoni
2017-04-03 11:25 ` Arnout Vandecappelle
2017-04-03 12:11 ` Thomas Petazzoni
2017-04-03 12:30 ` Waldemar Brodkorb [this message]
2017-04-03 12:45 ` Arnout Vandecappelle
2017-04-03 13:02 ` Thomas Petazzoni
2017-04-03 14:12 ` Arnout Vandecappelle
2017-04-01 16:52 ` [Buildroot] Patchwork cleanup, 10 patches to look at Thomas Petazzoni
2017-04-02 3:04 ` Carlos Santos
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=20170403123044.GI5361@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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