mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Waldemar Brodkorb <mail@waldemar-brodkorb.de>
To: musl@lists.openwall.com
Subject: Re: automatic musl-test
Date: Thu, 10 Apr 2014 16:10:14 +0200	[thread overview]
Message-ID: <20140410141012.GV3914@waldemar-brodkorb.de> (raw)
In-Reply-To: <20140409211742.GQ3034@port70.net>

Hi, 
Szabolcs Nagy wrote,

> * Szabolcs Nagy <nsz@port70.net> [2014-04-09 22:36:53 +0200]:
> 
> > * Szabolcs Nagy <nsz@port70.net> [2014-04-09 22:16:24 +0200]:
> > > * Waldemar Brodkorb <wbx@openadk.org> [2014-04-09 17:07:59 +0200]:
> > > > A report generated from today, is here:
> > > > http://openadk.org/musl-test/
> > > > 
> > > 
> > > hm something is wrong with the i686-git float tests
> > > 
> > 
> > can you send me some test binaries built by your toolchain?
> > 
> 
> ok i downloaded the adk-test-framework and the i686
> root fs has glibc in it..

Sure, the base system is glibc.
 
> that explains all the errors :)
> 
> may be you should report the bugs to glibc..
> 
> (i knew about several fp errors in glibc but i never had
> a recent enough glibc to test them)

Hmm, but the libc-test is compiled with musl libc via a special
specs file. So no glibc code involved while executing the test
binaries.
$ readelf -a libc-test/src/math/fenv.exe|grep interpreter
      [Requesting program interpreter: /lib/ld-musl-i686.so.1]

Upps, and here we see, that the wrong interpreter is linked into the
binary. I fixed it. Get a new REPORT.

best regards
 Waldemar

 


      reply	other threads:[~2014-04-10 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 15:07 Waldemar Brodkorb
2014-04-09 20:16 ` Szabolcs Nagy
2014-04-09 20:36   ` Szabolcs Nagy
2014-04-09 21:17     ` Szabolcs Nagy
2014-04-10 14:10       ` Waldemar Brodkorb [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=20140410141012.GV3914@waldemar-brodkorb.de \
    --to=mail@waldemar-brodkorb.de \
    --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).