From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] nilfs-utils: need NPTL threads
Date: Fri, 5 Jan 2018 11:31:42 +0100 [thread overview]
Message-ID: <20180105113142.47e4e087@windsurf.lan> (raw)
In-Reply-To: <20180105101708.GF8058@airbook.vandijck-laurijssen.be>
Hello,
On Fri, 5 Jan 2018 11:17:08 +0100, Kurt Van Dijck wrote:
> > The UCLIBC_HAS_ADVANCED_REALTIME help text says that this options enables
> > clock_nanosleep(). But with current code you must have NPTL enabled for
> > clock_nanosleep(). So the help text is not correct.
> >
> > This also means that architectures lack NPTL support can't have
> > clock_nanosleep() at all. Is there a reason for that?
>
> I share the concern, I appears that a shortcut has been taken in the
> uClibc configuration.
>
> OTOH, the topic of this thread has drifted away.
> From the nilfs-utils point of view, depending on NPTL is necessary
> today, so the patch stands.
> I propose to start a different thread, and merge this patch for
> nilfs-utils. Doing so would fix the current build problems,
> and when the uclibc problem eventually resolves, nilfs-utils too will be
> patched to not depend on NPTL.
>
> What do you think about that?
I agree. Especially since the same problem affects other packages, and
we have already added a NPTL dependency for those. When/if the uClibc
problem is fixed, we can get back to those packages and remove the NPTL
dependency if clock_nanosleep() becomes usable without NPTL.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-05 10:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 10:10 [Buildroot] [PATCH 1/2] nilfs-utils: need NPTL threads Kurt Van Dijck
2018-01-04 10:10 ` [Buildroot] [PATCH 2/2] nilfs-utils: fix build with static toolchains Kurt Van Dijck
2018-01-06 14:47 ` Thomas Petazzoni
2018-01-06 20:30 ` Kurt Van Dijck
2018-01-04 10:19 ` [Buildroot] [PATCH 1/2] nilfs-utils: need NPTL threads Baruch Siach
2018-01-04 10:33 ` Thomas Petazzoni
2018-01-04 10:51 ` Baruch Siach
2018-01-04 11:28 ` Kurt Van Dijck
2018-01-04 15:52 ` Yann E. MORIN
2018-01-04 17:23 ` Baruch Siach
[not found] ` <20180104201958.GB5130@waldemar-brodkorb.de>
2018-01-05 5:23 ` Baruch Siach
2018-01-05 10:17 ` Kurt Van Dijck
2018-01-05 10:31 ` Thomas Petazzoni [this message]
2018-01-05 11:24 ` Baruch Siach
2018-01-05 13:20 ` Kurt Van Dijck
2018-01-05 14:03 ` Baruch Siach
2018-01-07 20:08 ` Waldemar Brodkorb
2018-01-05 19:56 ` Kurt Van Dijck
2018-01-06 14:35 ` Thomas Petazzoni
2018-01-06 20:32 ` Kurt Van Dijck
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=20180105113142.47e4e087@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