Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libpthsem: remove argp-standalone dependency
Date: Sun, 03 May 2015 18:59:45 +0200	[thread overview]
Message-ID: <55465401.4080207@openwide.fr> (raw)
In-Reply-To: <5544C15E.9060103@mind.be>

Hi Arnout, All

Le 02/05/2015 14:21, Arnout Vandecappelle a ?crit :
> On 02/05/15 12:28, Romain Naour wrote:
>> argp-standalone provide libargp.a and argp.h which are
>> never used in libpthsem.
>>
>> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> 
> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
>  Build-test with and without the _COMPAT option, and checked that there is no
> reference to argp in the source.
> 
>  Adding the original submitter of this package in Cc for final verification.
> Gregory, do you remember why you added the argp-standalone dependency?
> 
Peter find why argp-standalone was added to libpthsem:
http://git.buildroot.net/buildroot/commit/?id=25206d6e26dc4ce9c272e68876f31d0ca7d30e67

Gregory is also the original submitter of bcusdk package and it seems that he
added argp-standalone dependency to libpthsem instead of bcusdk.

Thank you Arnout for your review and test.

Best regards,
Romain

>  Regards,
>  Arnout
> 

  reply	other threads:[~2015-05-03 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-02 10:28 [Buildroot] [PATCH 1/2] package/libpthsem: remove argp-standalone dependency Romain Naour
2015-05-02 10:28 ` [Buildroot] [PATCH 2/2] package/argp-standalone: is useless for (e)glibc toolchains Romain Naour
2015-05-03 17:21   ` Peter Korsgaard
2015-05-02 12:21 ` [Buildroot] [PATCH 1/2] package/libpthsem: remove argp-standalone dependency Arnout Vandecappelle
2015-05-03 16:59   ` Romain Naour [this message]
2015-05-02 12:52 ` 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=55465401.4080207@openwide.fr \
    --to=romain.naour@openwide.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