From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] chrony: fix build with musl
Date: Thu, 16 Nov 2017 08:46:19 +0100 [thread overview]
Message-ID: <20171116084619.30f091df@windsurf.lan> (raw)
In-Reply-To: <20171116040130.qqgusklzyv4y2z2r@tarshish>
Hello,
On Thu, 16 Nov 2017 06:01:30 +0200, Baruch Siach wrote:
> > > .../chrony/0001-ntp-fix-build-with-musl-libc.patch | 39 ++++++++++++++++++++++
> > > 1 file changed, 39 insertions(+)
> > > create mode 100644 package/chrony/0001-ntp-fix-build-with-musl-libc.patch
> >
> > Applied to master, thanks. Is the problem fixed in upstream musl? If
> > not, did you report the problem?
>
> musl version 1.1.18 defines the SCM_TIMESTAMPING_PKTINFO macro. So once we
> bump musl and rebuild the toolchain, we can remove this patch.
OK, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-11-16 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 11:37 [Buildroot] [PATCH] chrony: fix build with musl Baruch Siach
2017-11-15 22:11 ` Thomas Petazzoni
2017-11-16 4:01 ` Baruch Siach
2017-11-16 7:46 ` 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=20171116084619.30f091df@windsurf.lan \
--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