From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@cygnus.co.uk>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] failure of "make tests" for Linux synthetic target
Date: Mon, 25 Oct 1999 07:26:00 -0000 [thread overview]
Message-ID: <19991025092632.A18900@visi.com> (raw)
In-Reply-To: <3811306E.4FB2F19B@cygnus.co.uk>
On Sat, Oct 23, 1999 at 03:50:06AM +0000, Jonathan Larmour wrote:
> Grant Edwards wrote:
> >
> > The build of the linux synthetic target for eCOS seemed to go OK, but
> > when I did a "make tests" it failed because of what appears to be a
> > linker configuration problem. I could add bss4 and bss5 sections to
> > target.ld by hand, but that doesn't sound too kosher.
[...]
> Try 'objdump --section-headers install/lib/libtarget.a | grep -10 bss4'
No bss[45] sections ins libtarget.a or vectors.o.
However, extras.o does contain bss[45] sections:
> What versions of the tools are you using? i.e. ' i686-pc-linux-gnu-gcc -v'.
$ i686-pc-linux-gnu-gcc -v
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.1/specs
gcc version 2.95.1 19990816 (release)
I just build the copiler last week -- I initially tried to use the
version that came with RH6.0: gcc version egcs-2.91.66 19990314/Linux
(egcs-1.1.2 release). But, there were some options used by the ecos
makefiles that it didn't support.
If this us just something that is due to my using a newer version of
gcc than was used when the eCOS distribution was set up, then I'll add
bss[45] sections to the .ld file and assume it's not a problem.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~1999-10-25 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-22 15:32 Grant Edwards
1999-10-22 20:50 ` Jonathan Larmour
1999-10-25 7:26 ` Grant Edwards [this message]
1999-10-25 10:15 ` Jonathan Larmour
1999-10-25 10:21 ` Grant Edwards
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=19991025092632.A18900@visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@cygnus.co.uk \
/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).