From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: [musl] [RFC] removing __NR_clock_gettime / SYS_clock_gettime
Date: Sun, 19 Jan 2020 20:30:05 +0100 [thread overview]
Message-ID: <20200119193002.GN23985@port70.net> (raw)
In-Reply-To: <20200119185334.GJ30412@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2020-01-19 13:53:34 -0500]:
> On Sun, Jan 19, 2020 at 07:42:26PM +0100, Szabolcs Nagy wrote:
> > * Rich Felker <dalias@libc.org> [2020-01-19 13:16:43 -0500]:
> > > On Sun, Jan 19, 2020 at 06:51:17PM +0100, Szabolcs Nagy wrote:
> > > > i think you should build gcc with --enable-libstdcxx-time so
> > > > it does not try to do raw syscalls (which is bad on 64bit
> > > > targets too, not just for time64, i thought distros already
> > > > do this or patch out that entire thing)
> > >
> > > It does raw syscalls with that as I understand it. You need =rt to
> > > make it do the right thing.
> >
> > --enable-libstdcxx-time is default in mcm since
> >
> > commit 0291cc44eee410270a97efb6258394c1f1f8352a
> > Commit: Rich Felker <dalias@aerifal.cx>
> > CommitDate: 2016-05-06 18:37:09 +0000
> >
> > and the libstdc++ i built with that only has SYS_futex
> > syscalls in it on all targets.
> >
> > now i see that alpine libstdc++ has a raw clock_gettime
> > syscall in it too, alpine should fix that.
>
> Oh, the --enable-libstdcxx-time we already had was sufficient? I
> thought --enable-libstdcxx-time and --enable-libstdcxx-time=rt were
> different. Latest commit message may be nonsense then... :/
--enable-libstdcxx-time
is the same as
--enable-libstdcxx-time=yes
which does proper configure checks,
--enable-libstdcxx-time=rt
also checks -lrt which is not needed on musl,
but harmless (i guess it's an option so by
default libstdc++ avoids the -lrt dependency).
the default is =auto which hard-codes some
nonsense based on glibc version, we can fix
that for gcc-11 and them musl works without
magic options.
next prev parent reply other threads:[~2020-01-19 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 16:36 Rich Felker
2020-01-19 17:51 ` Szabolcs Nagy
2020-01-19 18:16 ` Rich Felker
2020-01-19 18:42 ` Szabolcs Nagy
2020-01-19 18:53 ` Rich Felker
2020-01-19 19:30 ` Szabolcs Nagy [this message]
2020-01-21 18:49 ` [musl] [RFC] [PATCH] " Rich Felker
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=20200119193002.GN23985@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).