From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] syslog-ng: fix builds with static libc
Date: Tue, 29 Jan 2019 23:03:26 +0100 [thread overview]
Message-ID: <20190129230326.32c51889@windsurf> (raw)
In-Reply-To: <20190128072934.12788-1-judge.packham@gmail.com>
Hello Chris,
This commit doesn't really "fix building with static libc", because it
was forbidden until now. It rather "allows" it.
On Mon, 28 Jan 2019 20:29:34 +1300
Chris Packham <judge.packham@gmail.com> wrote:
> Bring in an upstream patch to fix builds for targets which lack dlfcn.h
> and revert "package/syslog-ng: depend on !BR2_STATIC_LIBS".
>
> This reverts commit 44dbd2907c5995b0b0c56cb2274dc60415205dd8. Now that
> upstream has different fix for the build issues with a static libc we
> can re-enable syslog-ng on these systems.
>
> Fixes:
> - http://autobuild.buildroot.net/results/c0bca852e053cd0e021205b3a949e750ae602333
Also, this commit doesn't fix this autobuilder issue: the autobuilder
issue was resolved by your commit
44dbd2907c5995b0b0c56cb2274dc60415205dd8, which prevented selecting
syslog-ng in BR2_STATIC_LIBS=y configurations.
What this new commit does is re-allow selecting syslog-ng in
BR2_STATIC_LIBS=y configurations.
I've adjusted the commit log accordingly, and applied to master.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-01-29 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 7:29 [Buildroot] [PATCH v3] syslog-ng: fix builds with static libc Chris Packham
2019-01-29 22:03 ` 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=20190129230326.32c51889@windsurf \
--to=thomas.petazzoni@bootlin.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