public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Subject: Re: New leap tester fails libabigail build because of too old elfutils version (0.168)
Date: Fri, 3 Jun 2022 00:18:57 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Sorry, mistyped the new mailinglist address.
Now correct on CC.

On Fri, Jun 03, 2022 at 12:15:10AM +0200, Mark Wielaard wrote:
> Hi,
> We added a new opensuse-leap container tester to libabigail:
> But it fails the build with:
> In function ‘bool abigail::dwarf_reader::is_type_tag(unsigned int)’:
> error: ‘DW_TAG_coarray_type’ was not declared in this scope
>      case DW_TAG_coarray_type:
>           ^~~~~~~~~~~~~~~~~~~
> note: suggested alternative: ‘DW_TAG_array_type’
>      case DW_TAG_coarray_type:
>           ^~~~~~~~~~~~~~~~~~~
>           DW_TAG_array_type
> error: ‘DW_TAG_immutable_type’ was not declared in this scope
>      case DW_TAG_immutable_type:
>           ^~~~~~~~~~~~~~~~~~~~~
> note: suggested alternative: ‘DW_TAG_volatile_type’
>      case DW_TAG_immutable_type:
>           ^~~~~~~~~~~~~~~~~~~~~
>           DW_TAG_volatile_type
> DW_TAG_coarray_type and DW_TAG_immutable_type are two new DWARF5 tags,
> not yet defined in libdw-0.168.
> We could workaround that by checking and ignoring or redefining them.
> But even then the testsuite fails various tests. I suspect because
> there are various DWARF5 test files now.
> Does it make sense try to make this work against such an old elfutils version?
> Or should we simply not run a builder with this old an elfutils version?
> elfutils 0.171 was the first version to officially support
> DWARF5. Maybe that should be the minimum version for libabigail now?
> The centos7 builder and debian-old-stable builders have elfutils 0.176
> and are both green:
> Cheers,
> Mark
> P.S. There is now a dedicated list (CCed) for
>      any questions about the buildbot builders.

           reply	other threads:[~2022-06-02 22:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).