From: Ian Lance Taylor <ian@cygnus.com>
To: davem@caip.rutgers.edu
Cc: gas2@cygnus.com
Subject: Re: bfd assertion bug found
Date: Mon, 27 Nov 1995 23:04:00 -0000 [thread overview]
Message-ID: <9511280704.AA07439@tweedledumb.cygnus.com> (raw)
In-Reply-To: <199511280437.XAA07279@huahaga.rutgers.edu>
Date: Mon, 27 Nov 1995 23:37:29 -0500
From: "David S. Miller" <davem@caip.rutgers.edu>
It seems that the linker interprets arguments differently in 2.6,
if I specify '-N' to the linker in 2.5.2 it produces a static final
object, in 2.6 it sets config.dynamic_link to true. This is what
causes trouble when relocations are being scanned.
It sounds like a bug that -N does not cause a static link. However, I
do not understand how it could produce the symptoms you are reporting.
I have no trouble doing a dynamic link with -N--the final output does
not run, since the dynamic information is misplaced, but the link does
succeed without any assertion errors. I think you must be seeing two
different problems.
Ian
next prev parent reply other threads:[~1995-11-27 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-27 20:37 David S. Miller
1995-11-27 23:04 ` Ian Lance Taylor [this message]
1995-11-28 0:08 ` David S. Miller
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=9511280704.AA07439@tweedledumb.cygnus.com \
--to=ian@cygnus.com \
--cc=davem@caip.rutgers.edu \
--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).