public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: Versioned symbols in elfutils and uClibc
Date: Tue, 28 Apr 2015 13:01:44 +0300	[thread overview]
Message-ID: <CAMo8BfKXx1ui=90DQUrK-NRe6sAxzbDWYmg6QL1Y3GkEv78iYQ@mail.gmail.com> (raw)
In-Reply-To: CAMo8BfK=By_rwOzmC8YWP1=zJcjEdeMS5WVNpsKpeM6bmUy1kg@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

On Mon, Apr 27, 2015 at 5:12 AM, Max Filippov <jcmvbkbc@gmail.com> wrote:
> On Fri, Apr 24, 2015 at 4:36 PM, Mark Wielaard <mjw@redhat.com> wrote:
>> On Fri, Apr 24, 2015 at 07:49:55AM -0400, Anthony G. Basile wrote:
>>> On 04/23/15 18:24, Max Filippov wrote:
>>> >A lot of tests failed because elfutils were built with --disable-progs
>>> >(otherwise the build fails), and some test binaries failed to build
>>> >because they call functions not available in uClibc.
>>
>> Hmmm. elfutils doesn't support --disable-progs. Not having the tools
>
> I'm building my rootfs in the Buildroot. That must be a local buildroot
> patch from some kind soul that's been using uClibc.
>
> So, I've switched to the pristine sources from git and forward-ported
> series pointed to by Anthony and now the results are the following:
> The log is attached. I'll take a look at the segfaults.

Ok, segfaults were caused by uClibc (not supporting %m[...] in sscanf)
and argp-standalone (passing arbitrary ints to isprint). After fixing
these issues I get the following numbers:

# TOTAL: 134
# PASS:  121
# SKIP:  7
# XFAIL: 0
# FAIL:  6
# XPASS: 0
# ERROR: 0

-- 
Thanks.
-- Max

             reply	other threads:[~2015-04-28 10:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 10:01 Max Filippov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-03 18:18 Max Filippov
2015-05-01  8:52 Mark Wielaard
2015-04-29  0:35 Max Filippov
2015-04-29  0:29 Max Filippov
2015-04-28 17:35 Mark Wielaard
2015-04-28 17:35 Anthony G. Basile
2015-04-28 17:34 Mark Wielaard
2015-04-28 17:10 Mark Wielaard
2015-04-28 17:04 Mark Wielaard
2015-04-27  2:12 Max Filippov
2015-04-25 13:29 Anthony G. Basile
2015-04-25 13:14 Anthony G. Basile
2015-04-25  9:41 Mark Wielaard
2015-04-24 16:13 Max Filippov
2015-04-24 13:36 Mark Wielaard
2015-04-24 11:49 Anthony G. Basile
2015-04-23 22:24 Max Filippov
2015-04-23 20:56 Mark Wielaard
2015-04-23 20:20 Max Filippov
2015-04-23 19:39 Mark Wielaard
2015-04-22 21:18 Max Filippov

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='CAMo8BfKXx1ui=90DQUrK-NRe6sAxzbDWYmg6QL1Y3GkEv78iYQ@mail.gmail.com' \
    --to=jcmvbkbc@gmail.com \
    --cc=elfutils-devel@lists.fedorahosted.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).