From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/RFC 1/1] package/libglob: new package
Date: Tue, 02 Aug 2016 19:15:18 +0200 [thread overview]
Message-ID: <62177dxtet.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 1470083347.4303.12.camel@embedded.rocks
Hi J?rg,
Am Mon, 01 Aug 2016 22:29:07 +0200 schrieb J?rg Krause:
> Hi,
>
> On So, 2016-07-31 at 18:29 +0200, Bernd Kuhls wrote:
>> Needed for packages which need GLOB_BRACE & GLOB_NOMAGIC. These
>> defines
>> are not provided by musl toolchains.
>>
>> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
>
> sorry, I didn't noticed you already submitted a patch to add libglob. I
> submitted a similar patch, too:?http://lists.busybox.net/pipermail/buil
> droot/2016-August/168908.html.
yes, but your patch is better because it takes the static-only scenario
into account. Therefore I closed my patch in patchworks.
Regards, Bernd
prev parent reply other threads:[~2016-08-02 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 16:29 [Buildroot] [PATCH/RFC 1/1] package/libglob: new package Bernd Kuhls
2016-08-01 20:29 ` Jörg Krause
2016-08-02 17:15 ` Bernd Kuhls [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=62177dxtet.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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