From: "Joel Sherrill <joel@merlin.gcs.redstone.army.mil>" <joel@merlin.gcs.redstone.army.mil>
To: gas2@cygnus.com
Subject: binutils 2.7 mipsorion64-elf question
Date: Wed, 11 Sep 1996 11:16:00 -0000 [thread overview]
Message-ID: <Pine.SV4.3.91.960911130312.3230E-100000@merlin> (raw)
I am trying to verify that the newly submitted mips port of rtems
compiles and was merged correctly and may have tripped across a problem:
The submitter was using the very old "cygnus-2.6.4-950101" whatever that is.
I am using binutils 2.7 and gcc 2.7.2 snapshot 960719 configured for
mips64orion-rtems which is a clone of mips64orion-elf.
The warning from ld is:
liblnk.rel: uses different e_flags (0x0) fields than previous modules
(0x20000001)
clock.rel: uses different e_flags (0x1) fields than previous modules
(0x20000001)
I can't explain the reason why sometimes it is a 0x0 and sometimes it is
a 0x1 but I think that all of the files with this problem were generated
using "ld -r".
Does this sound like a known/familiar problem or do you need some more
information from me?
--joel
next reply other threads:[~1996-09-11 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-11 11:16 Joel Sherrill <joel@merlin.gcs.redstone.army.mil> [this message]
1996-09-11 11:25 ` Ian Lance Taylor
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=Pine.SV4.3.91.960911130312.3230E-100000@merlin \
--to=joel@merlin.gcs.redstone.army.mil \
--cc=gas2@cygnus.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).