public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: make check fails for version 0.189 on aarch64
Date: Mon, 18 Sep 2023 15:31:12 +0200	[thread overview]
Message-ID: <75af689342185f330883efca7626fcc5222e81e2.camel@ipfire.org> (raw)
In-Reply-To: <20230915212422.GB5558@gnu.wildebeest.org>

Hi Mark,

Thanks for the prompt response. This error is now resolved. The test
suite is happy. Turns out, it was a problem in then underlying image.
After we updated it, the error went away.

Greetings Jonatan

Am Freitag, dem 15.09.2023 um 23:24 +0200 schrieb Mark Wielaard:
> Hi Jonatan,
> 
> On Fri, Sep 15, 2023 at 08:42:28PM +0200, Jonatan Schlag via
> Elfutils-devel wrote:
> > I'm currently trying to build elfutils in version 0.189 on an
> > aarch64
> > system. Unfortunately, make check fails with the following errors:
> > 
> > https://nopaste.ipfire.org/view/Sx7pjy4g
> > 
> > The full log can be found here:
> > 
> > https://pakfire.ipfire.org/jobs/28a23239-80a6-4a24-b506-dbc367d96afa/log
> > 
> > The same configuration works on x86_64. I currently run out of
> > ideas
> > what to try next. I know that the test suite passes on Debian for
> > aarch64. So there must be an error with the system itself, but as
> > said,
> > I lack ideas how to debug this further.
> > 
> > Some input would be highly appreciated.
> 
> So you only got 4 FAILs.
> 
> FAIL: run-backtrace-native.sh
> FAIL: run-backtrace-dwarf.sh
> FAIL: run-backtrace-native-core.sh
> FAIL: run-deleted.sh
> 
> And they all seem to fail in the same way. You get a backtrace, but
> almost all symbol names come out empty/null.
> 
> But your configure line does contain -g so you should at least get it
> for the elfutils libraries and (test) programs. The only possible
> issue with your configure line is the use of -fdebug-prefix-map which
> I believe doesn't work correctly when also using LTO.
> 
> And maybe your /usr/lib64/libc.so.6 might not have any symbols?
> 
> Cheers,
> 
> Mark


      reply	other threads:[~2023-09-18 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 18:42 Jonatan Schlag
2023-09-15 21:24 ` Mark Wielaard
2023-09-18 13:31   ` Jonatan Schlag [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=75af689342185f330883efca7626fcc5222e81e2.camel@ipfire.org \
    --to=jonatan.schlag@ipfire.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.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).