From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/wvstreams: add argp-standalone as optionnal dependency
Date: Sat, 02 May 2015 08:57:35 +0200 [thread overview]
Message-ID: <87383fv540.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <5543FC55.2040203@openwide.fr> (Romain Naour's message of "Sat, 02 May 2015 00:21:09 +0200")
>>>>> "Romain" == Romain Naour <romain.naour@openwide.fr> writes:
Hi,
>> I wonder if we shouldn't make the argp-standalone package only
>> available on !glibc builds, since glibc provides its own argp
>> implementation.
> I'm agree, most of packages which uses argp.h select argp-standalone only when a
> uClibc toolchain is used.
> Except libpthsem package which select argp-standalone unconditionally.
> However, I built successfully libpthsem with a glibc toolchain and without
> argp-standalone installed.
> It appears that argp.h from glibc is more up to date should be preferred to
> argp-standalone one.
Yes, sounds sensible.
> I can do the change if you want.
Please do - Thanks!
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-05-02 6:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 16:44 [Buildroot] [PATCH 1/3] package/argp-standalone: format patches to git patches Romain Naour
2015-05-01 16:44 ` [Buildroot] [PATCH 2/3] package/argp-standalone: add missing limits.h Romain Naour
2015-05-01 17:29 ` Max Filippov
2015-05-01 20:48 ` Thomas Petazzoni
2015-05-01 21:40 ` Romain Naour
2015-05-01 16:44 ` [Buildroot] [PATCH 3/3] package/wvstreams: add argp-standalone as optionnal dependency Romain Naour
2015-05-01 21:04 ` Thomas Petazzoni
2015-05-01 22:21 ` Romain Naour
2015-05-02 6:57 ` Peter Korsgaard [this message]
2015-05-02 8:30 ` Thomas Petazzoni
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=87383fv540.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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