public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: binutils@sources.redhat.com
Subject: gas misbehavior in binutils-2.16.1 for sh4 target and --enable-shared
Date: Wed, 24 Aug 2005 23:52:00 -0000	[thread overview]
Message-ID: <200508241953.14014.vapier@gentoo.org> (raw)

while debugging a gcc issue, i noticed that `file` was giving me varying 
results; turns out that it was due to configuring binutils-2.16.1 with 
--enable-shared.  binutils-2.15 works as expected, so i'm inclined to think it 
a bug :).  the other quirky thing is readelf shows different Flags in the ELF 
header ...

using vanilla binutils-2.16.1 and binutils-2.15 on an amd64 host, i ran:
./configure --target=sh4-linux --enable-shared
make
touch test.s
./gas/as-new test.s -o test.o
file test.o
./binutils/readelf -h test.o | grep Flags

binutils-2.16.1 with --enabled-shared:
test.o: ELF 32-bit LSB relocatable, Hitachi SH, version 1 (SYSV), not stripped
Flags: 0x19, unknown ISA

binutils-2.16.1 without --enabled-shared:
binutils-2.15 with --enabled-shared:
test.o: ELF 32-bit LSB relocatable, Hitachi SH, version 1 MathCoPro/FPU/MAU 
Required (SYSV), not stripped
Flags: 0x1, sh1

running through strace shows that the correct libbfd.so is being loaded, 
libbfd-2.16.1.so from ./bfd/.libs/x86_64/libbfd-2.16.1.so ... so what 
gives ? :)

for reference, i tested a few different versions ... 2.15.92.0.2 and 
2.16.91.0.3 also have this odd behavior ...
-mike

             reply	other threads:[~2005-08-24 23:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 23:52 Mike Frysinger [this message]
2005-08-25  5:13 ` Kaz Kojima
2005-08-25  5:46   ` Alan Modra
2005-08-25  5:59     ` Kaz Kojima
2005-08-25 22:08   ` Mike Frysinger

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=200508241953.14014.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=binutils@sources.redhat.com \
    /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).