public inbox for annobin@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: annobin@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): annobin - failed test (failure) (master)
Date: Wed, 6 Mar 2024 10:45:53 +0000	[thread overview]
Message-ID: <d4ea3fa4-8131-46d9-8d04-939cc2195eb9@redhat.com> (raw)
In-Reply-To: <20240305210558.GB24213@gnu.wildebeest.org>

Hi Mark,

> But in general the debian based builds fail because of the configure
> check for the clang++ include file failing.

Ah - because it is looking in /usr/include and not `llvm-config --includedir`

I am not sure how to resolve this.  The AC_CHECK_HEADER macro does not allow
for searching in non-standard locations.

Maybe it would be simpler to just delete this check ?

> And the fedora based builds fail because of a MAYB lto FAIL for the
> debuginfod testcase.

Right.  I have tracked this down to the fact that the new code you
suggested for loading potentially reloc encumbered binary files:

    Dwfl *dwfl = dwfl_begin (&dwfl_callbacks);
    Dwfl_Module *module = dwfl_report_elf (dwfl, data->full_filename, data->full_filename, -1, 0, false);

    if (module != NULL)
	{
	  Dwarf_Addr bias;
	  dwarf = dwfl_module_getdwarf (module, &bias);
	}

Appears to automatically follow debug links, using debuginfod if necessary.
So this means that annocheck no longer reports "I am contacting the
debuginfod server to see if it has the debug info" and so the debuginfod
test fails. :-)

I will update the test so that it checks to see if the debug information
was silently located.

Cheers
   Nick




  reply	other threads:[~2024-03-06 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 19:22 builder
2024-03-05 21:05 ` Mark Wielaard
2024-03-06 10:45   ` Nick Clifton [this message]
2024-03-07  0:05     ` Mark Wielaard
2024-03-07 13:34       ` ubuntu-riscv " Mark Wielaard
2024-03-08 15:28         ` Nick Clifton
2024-03-08 17:19           ` Mark Wielaard
2024-03-25 17:20 builder
2024-03-25 17:35 builder

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=d4ea3fa4-8131-46d9-8d04-939cc2195eb9@redhat.com \
    --to=nickc@redhat.com \
    --cc=annobin@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).