From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/clamav: fix build with uClibc
Date: Sun, 16 Nov 2014 23:07:59 +0100 [thread overview]
Message-ID: <87389ier40.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141116215017.GD10840@free.fr> (Yann E. MORIN's message of "Sun, 16 Nov 2014 22:50:17 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Thomas, All,
> On 2014-11-16 22:02 +0100, Thomas Petazzoni spake thusly:
>> On Sun, 16 Nov 2014 18:21:04 +0100, Bernd Kuhls wrote:
>>
>> > Please add the upstream bugtracker URL to your patch:
>> > https://bugzilla.clamav.net/show_bug.cgi?id=11170
>>
>> I believe Yann's patch is not an appropriate upstream solution, and a
>> configure.ac check should be added instead.
> That's what I think, too. But see what Peter had to say about that (as
> pointed out by Bernd):
> http://patchwork.ozlabs.org/patch/406336/
> Now, upstream has both patches in their bug tracker: the original from
> Bernd that adds a check in ./configure (well, rather in
> m4/reorganization/headers.m4, but that gives a configure-time check),
> and my patch, does just slightly expands the current test to recognise
> uClibc.
Just to clarify - I don't object against a configure script, my comment
on http://patchwork.ozlabs.org/patch/406336/ was simply that the
existing HAVE_BACKTRACE check didn't work for uClibc and it made more
sense to fix that than add an additional HAVE_EXECINFO_H check.
> But back to Buildroot: we need a fix before the release, and that patch
> is what Peter asked for.
Yeah, and I've committed it. When upstream decides (and perhaps makes a
new release) we can update and get rid of the patch.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-11-16 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 16:34 [Buildroot] [PATCH] package/clamav: fix build with uClibc Yann E. MORIN
2014-11-16 17:21 ` Bernd Kuhls
2014-11-16 17:31 ` Yann E. MORIN
2014-11-16 21:02 ` Thomas Petazzoni
2014-11-16 21:50 ` Yann E. MORIN
2014-11-16 22:07 ` Peter Korsgaard [this message]
2014-11-16 22:01 ` Peter Korsgaard
2014-11-16 22:03 ` Peter Korsgaard
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=87389ier40.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.