From: Jorge Almeida <jjalmeida@gmail.com>
To: musl@lists.openwall.com
Subject: Re: clockspeed
Date: Wed, 13 Jul 2016 13:10:55 -0700 [thread overview]
Message-ID: <CAKpSnpK1xiEfYZUSraWb8VU=1ZHEjk-o7jH+4S51snX-TVZWaQ@mail.gmail.com> (raw)
In-Reply-To: <20160713194227.GL15995@brightrain.aerifal.cx>
On Wed, Jul 13, 2016 at 12:42 PM, Rich Felker <dalias@libc.org> wrote:
> On Wed, Jul 13, 2016 at 12:04:36PM -0700, Jorge Almeida wrote:
>> Has anyone compiled clockspeed against musl, in a x86_64?
>
> I'm guessing you mean DJB's package,
Indeed.
but the name is generic enough
> that I can't be sure. Next time try to be more clear.
I had no idea there was some other package with the same name.
>
>> If so, would you share conf-cc and conf-ld?
>
> I just did as a test and it has some obvious issues like missing and
> wrong prototypes for standard functions and "extern int errno;" rather
> than #include <errno.h> (the latter is DJB's willfully wrong code to
> make a point that he likes being wrong), but it compiled "ok" after
> changing error.h. No idea if it works.
>
> I didn't modify conf-cc or conf-ld at all because the native gcc
> targets musl, but if you wanted to cross-compile it would probably
> work putting the name of your cross compiler there, or the musl-gcc
> wrapper even.
>
I'm not cross-compiling, but the distro is not musl-based. Yes, I put
the wrapper in conf-cc and conf-ld.
I've been using clockspeed for years (with < 5ms discrepancy relative
to the NTP server, on crappy hardware). But I had it compiled against
dietlibc long ago (in x86), and now it doesn't compile against dietlib
nor against musl. Just wondering if x86_64 brings about some extra
problem.
Jorge
prev parent reply other threads:[~2016-07-13 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 19:04 clockspeed Jorge Almeida
2016-07-13 19:42 ` clockspeed Rich Felker
2016-07-13 20:10 ` Jorge Almeida [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='CAKpSnpK1xiEfYZUSraWb8VU=1ZHEjk-o7jH+4S51snX-TVZWaQ@mail.gmail.com' \
--to=jjalmeida@gmail.com \
--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).