From: Mark Wielaard <mark@klomp.org>
To: libabigail@sourceware.org
Cc: buildbot@sourceware.org
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: <Ypk3UXit6RyQ1ZRt@wildebeest.org> (raw)
In-Reply-To: <Ypk2bsR62+Ey+IB5@wildebeest.org>
Sorry, mistyped the new buildbot@sourceware.org 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:
> https://builder.sourceware.org/buildbot/#/builders/libabigail-opensuseleap-x86_64
>
> But it fails the build with:
>
> abg-dwarf-reader.cc: In function ‘bool abigail::dwarf_reader::is_type_tag(unsigned int)’:
> abg-dwarf-reader.cc:6843:10: error: ‘DW_TAG_coarray_type’ was not declared in this scope
> case DW_TAG_coarray_type:
> ^~~~~~~~~~~~~~~~~~~
> abg-dwarf-reader.cc:6843:10: note: suggested alternative: ‘DW_TAG_array_type’
> case DW_TAG_coarray_type:
> ^~~~~~~~~~~~~~~~~~~
> DW_TAG_array_type
> abg-dwarf-reader.cc:6845:10: error: ‘DW_TAG_immutable_type’ was not declared in this scope
> case DW_TAG_immutable_type:
> ^~~~~~~~~~~~~~~~~~~~~
> abg-dwarf-reader.cc:6845:10: 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:
> https://builder.sourceware.org/buildbot/#/builders/libabigail-debian-amd64
> https://builder.sourceware.org/buildbot/#/builders/libabigail-centos-x86_64
>
> Cheers,
>
> Mark
>
> P.S. There is now a dedicated buildbot@sourceware.org list (CCed) for
> any questions about the buildbot builders.
>
parent reply other threads:[~2022-06-02 22:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Ypk2bsR62+Ey+IB5@wildebeest.org>]
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=Ypk3UXit6RyQ1ZRt@wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=libabigail@sourceware.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).