From: "eric.boehm at broadcom dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/28975] New: run-large-elf-file.sh fails in 32-bit cross-compile on 64-bit machine
Date: Thu, 17 Mar 2022 20:40:37 +0000 [thread overview]
Message-ID: <bug-28975-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28975
Bug ID: 28975
Summary: run-large-elf-file.sh fails in 32-bit cross-compile on
64-bit machine
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: general
Assignee: unassigned at sourceware dot org
Reporter: eric.boehm at broadcom dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
run-large-elf-file.sh should not run if it is a 32-bit cross-compile on a
64-bit machine.
The shell script checks
long_bit=$(getconf LONG_BIT)
which will return 64 even if it is a 32-bit compile
Here's a patch which is a bit of a hack. There are probably more appropriate
ways to fix this.
This affects versions 0.181-0.186
--- elfutils-0.181/tests/run-large-elf-file.sh.orig 2020-09-08
04:45:06.000000000 -0700
+++ elfutils-0.181/tests/run-large-elf-file.sh 2022-03-17 12:23:53.967607000
-0700
@@ -21,3 +21,8 @@
# ELF files.
-long_bit=$(getconf LONG_BIT)
+if [[ $CC =~ "-m32" ]]
+then
+ long_bit=32
+else
+ long_bit=$(getconf LONG_BIT)
+fi
echo "long_bit: $long_bit"
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-03-17 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 20:40 eric.boehm at broadcom dot com [this message]
2022-03-20 23:19 ` [Bug general/28975] " mark at klomp dot org
2022-03-24 11:34 ` mark at klomp dot 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-28975-10460@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).