From: "Sochat, Vanessa" <sochat1@llnl.gov>
To: "libabigail@sourceware.org" <libabigail@sourceware.org>
Subject: Patch for Incorrect Symbol DW_LANG_PL1 -> DW_LANG_PLI
Date: Sun, 17 Oct 2021 20:53:52 +0000 [thread overview]
Message-ID: <CC8ACF19-2FC1-406F-AC5B-9339B5538401@llnl.gov> (raw)
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
Hi Libabigail (and master Dodji!),
A symbol in elfutils was renamed (see line 7 here) in elfutils:
https://chromium.googlesource.com/external/elfutils/+/515dd0acc77673c953380bcf5ccfb05b83c5a3ab/NEWS
This results in this error when trying to install the 2.0 libabigail release (and I suspect others depending on the version of elfutils used):
error: 'DW_LANG_PL1' was not declared in this scope; did you mean 'DW_LANG_PLI'
And after some poking I figured out that this line https://sourceware.org/git/?p=libabigail.git;a=blob;f=src/abg-dwarf-reader.cc;h=1d6ad24cbfcc2d94c07311bb04112f14f4f0e71c;hb=HEAD#l11056 needs to be DW_LANG_PLI instead of DW_LANG_PL1.
I am attaching the patch I used to make the fix in spack: https://github.com/spack/spack/blob/03f84fb440770101816dad61ca59cf1bebf1997b/var/spack/repos/builtin/packages/libabigail/package.py#L37
If you want to reproduce that bug, you should be able to clone spack, comment out the line for the patch, add spack’s bin to the path, and then spack install libabigail.
I’ve also been having some trouble building libabigail from the git repository – the instructions in the sourceware docs don’t work completely, as I get a “syntax error near unexpected token ‘XML,’ and commenting out that line gets a bit further, but then errors missing library paths for libxml (which I’ve added). Do you have your release scripts you might share to reproduce what is in the release tarball?
Thank you, and thank you for all the recent work on libabigail!
Best,
Vanessa
[-- Attachment #2: 0001-plt.patch --]
[-- Type: application/octet-stream, Size: 838 bytes --]
From ba5e2b5dc9de106635c12ebe9260e2fc0212ff91 Mon Sep 17 00:00:00 2001
From: Vanessa Sochat <sochat1@llnl.gov>
Date: Fri, 15 Oct 2021 05:17:47 +0000
Subject: [PATCH] fixing incorrect symbol
Signed-off-by: @vsoch <vsoch@noreply.users.github.com>
---
src/abg-dwarf-reader.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/abg-dwarf-reader.cc b/src/abg-dwarf-reader.cc
index 1d6ad24c..8dd86c5a 100644
--- a/src/abg-dwarf-reader.cc
+++ b/src/abg-dwarf-reader.cc
@@ -11053,7 +11053,7 @@ dwarf_language_to_tu_language(size_t l)
return translation_unit::LANG_Ada95;
case DW_LANG_Fortran95:
return translation_unit::LANG_Fortran95;
- case DW_LANG_PL1:
+ case DW_LANG_PLI:
return translation_unit::LANG_PL1;
case DW_LANG_ObjC:
return translation_unit::LANG_ObjC;
--
2.17.1
next reply other threads:[~2021-10-17 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 20:53 Sochat, Vanessa [this message]
2021-10-17 22:04 ` Mark Wielaard
2021-10-18 15:27 ` Sochat, Vanessa
2021-10-18 16:25 ` Mark Wielaard
2021-10-18 17:08 ` Sochat, Vanessa
2021-10-18 18:03 ` Ben Woodard
2021-10-18 20:38 ` Sochat, Vanessa
2021-10-19 10:58 ` Dodji Seketeli
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=CC8ACF19-2FC1-406F-AC5B-9339B5538401@llnl.gov \
--to=sochat1@llnl.gov \
--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).