From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <musl-return-15230-ml=inbox.vuxu.org@lists.openwall.com>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,
	RCVD_IN_MSPIKE_WL,SUBJ_OBFU_PUNCT_FEW,SUBJ_OBFU_PUNCT_MANY
	autolearn=ham autolearn_force=no version=3.4.2
Received: from mother.openwall.net (mother.openwall.net [195.42.179.200])
	by inbox.vuxu.org (OpenSMTPD) with SMTP id f2f3d5ca
	for <ml@inbox.vuxu.org>;
	Sun, 19 Jan 2020 19:30:26 +0000 (UTC)
Received: (qmail 17506 invoked by uid 550); 19 Jan 2020 19:30:24 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 17487 invoked from network); 19 Jan 2020 19:30:24 -0000
Date: Sun, 19 Jan 2020 20:30:05 +0100
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Message-ID: <20200119193002.GN23985@port70.net>
Mail-Followup-To: musl@lists.openwall.com
References: <20200119163616.GE30412@brightrain.aerifal.cx>
 <20200119175117.GL23985@port70.net>
 <20200119181643.GI30412@brightrain.aerifal.cx>
 <20200119184225.GM23985@port70.net>
 <20200119185334.GJ30412@brightrain.aerifal.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200119185334.GJ30412@brightrain.aerifal.cx>
User-Agent: Mutt/1.10.1 (2018-07-13)
Subject: Re: [musl] [RFC] removing __NR_clock_gettime / SYS_clock_gettime

* 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.