From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] linuxptp: needs NPTL
Date: Sun, 16 Sep 2018 15:39:42 +0200 [thread overview]
Message-ID: <20180916153942.56d7c7d1@windsurf> (raw)
In-Reply-To: <20180916050522.bldd73xzol5nryte@sapphire.tkos.co.il>
Hello,
On Sun, 16 Sep 2018 08:05:22 +0300, Baruch Siach wrote:
> On Sat, Sep 15, 2018 at 09:20:05PM +0200, Fabrice Fontaine wrote:
> > /home/buildroot/autobuild/run/instance-1/output/host/bin/or1k-linux-gcc phc_ctl.o phc.o sk.o util.o clockadj.o sysoff.o print.o version.o -lm -lrt -o phc_ctl
> > phc2sys.o: In function `do_loop':
> > phc2sys.c:(.text+0x18bc): undefined reference to `clock_nanosleep'
> >
> > Fixes:
> > - http://autobuild.buildroot.org/results/a31e0a5ae15e1164115e4e5981ef5fb3c3284bcc
>
> This should only affect 2018.02.x. The latest uClibc-ng version provides
> clock_nanosleep() even for non NPTL configurations.
Indeed. Due to this, perhaps there's a bunch of NPTL dependencies we
could remove:
package/blktrace/Config.in: depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # clock_nanosleep()
package/can-utils/Config.in: depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # clock_nanosleep()
package/dvblast/Config.in: depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # clock_nanosleep()
package/nilfs-utils/Config.in: depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # clock_nanosleep()
Anyway, for this linuxptp change, I have marked the patch as "Delegated
to Peter" on patchwork, so that Peter takes care of it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-16 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 19:20 [Buildroot] [PATCH 1/1] linuxptp: needs NPTL Fabrice Fontaine
2018-09-16 5:05 ` Baruch Siach
2018-09-16 13:39 ` Thomas Petazzoni [this message]
2018-09-20 21:46 ` 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=20180916153942.56d7c7d1@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