From: "fantasquex at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/29073] program header entry 2: unknown program header entry type 0x70000003
Date: Wed, 01 Jun 2022 15:53:49 +0000 [thread overview]
Message-ID: <bug-29073-10460-s7uWTS0DjR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29073-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29073
--- Comment #3 from Letu Ren <fantasquex at gmail dot com> ---
Hi! I encountered this issue when building packages for ArchLinux RISC-V. I
wonder whether there is a patch which can be backported to 0.187 to make tests
pass.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-01 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 9:50 [Bug tools/29073] New: " schwab@linux-m68k.org
2022-04-23 21:47 ` [Bug tools/29073] " mark at klomp dot org
2022-04-25 12:48 ` mliska at suse dot cz
2022-06-01 15:53 ` fantasquex at gmail dot com [this message]
2022-08-11 7:30 ` schwab@linux-m68k.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=bug-29073-10460-s7uWTS0DjR@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).