From: Ian Lance Taylor <ian@cygnus.com>
To: joel@merlin.gcs.redstone.army.mil
Cc: gas2@cygnus.com
Subject: Re: possible bug in bfd/sunos.c
Date: Tue, 28 May 1996 09:07:00 -0000 [thread overview]
Message-ID: <199605281607.MAA13904@sanguine.cygnus.com> (raw)
In-Reply-To: <Pine.SV4.3.91.960528101146.13030G-100000@merlin>
Date: Tue, 28 May 1996 10:50:25 -0500 (CDT)
From: Joel Sherrill <joel@merlin.gcs.redstone.army.mil>
I am configured for sparc-rtems which is essentially the same as
sparc-aout with different CPP_PREDEFINES. I use the following assembly
file (cut down to the point of uselessness :) ):
.text
sethi %hi(stack_space + 16 * 1024), %g1
call _main
.comm stack_space, 16 * 1024
I then run this script on it:
sparc-rtems-as -o test.o test.s
sparc-rtems-ld test.o
and get the following message:
bfd assertion fail ../../src/bfd/sunos.c:1839
If you configure for a SunOS target, the linker will automatically
generate a shared library if there are any undefined symbols in the
link. This odd behaviour is for compatibility with the SunOS linker.
In the current snapshots, the sparc-aout target does not have this
behaviour, since shared libraries are not useful for embedded systems,
but in 2.6 the sparc-aout target is the same as SunOS.
In your example, the linker is created a shared library.
The assertion failure you are getting is, as you guessed, a bug in the
assertion condition. You can just replace the BFD_ASSERT with one
from a current snapshot to avoid it. It is likely, though, that you
do not want to create a shared library at all.
Ian
next prev parent reply other threads:[~1996-05-28 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-28 8:56 Joel Sherrill
1996-05-28 9:07 ` Ian Lance Taylor [this message]
1996-05-28 12:14 ` Joel Sherrill
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=199605281607.MAA13904@sanguine.cygnus.com \
--to=ian@cygnus.com \
--cc=gas2@cygnus.com \
--cc=joel@merlin.gcs.redstone.army.mil \
/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).