Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/wvstreams: add argp-standalone as optionnal dependency
Date: Sat, 2 May 2015 10:30:03 +0200	[thread overview]
Message-ID: <20150502103003.4fb7370d@free-electrons.com> (raw)
In-Reply-To: <5543FC55.2040203@openwide.fr>

Dear Romain Naour,

On Sat, 02 May 2015 00:21:09 +0200, Romain Naour wrote:

> 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.
> 
> I can do the change if you want.

That would be nice.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2015-05-02  8:30 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
2015-05-02  8:30       ` Thomas Petazzoni [this message]

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=20150502103003.4fb7370d@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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