From: Paul Kinzelman <PaulK@isdcorp.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] tool build
Date: Wed, 05 Apr 2000 13:12:00 -0000 [thread overview]
Message-ID: <A71E53794EDDD211945E009027468857239FA1@isdnts02.isdcorp.com> (raw)
Yes, that was the problem. Sorry for the desperate entreaty. :-)
I get kind of desperate when something hugely complicated quits.
I had make the tools area be someplace other than '/tools'
and evidently either messed up, or something doesn't work about
moving the tools area. I looked and that file *is* on my
tools area.
I think I can fix it now.
Thanks so much!
-PaulK
-----Original Message-----
From: Jonathan Larmour [ mailto:jlarmour@redhat.co.uk ]
Sent: Wednesday, April 05, 2000 12:15 PM
To: Paul Kinzelman
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] tool build
Paul Kinzelman wrote:
>
> I've been having major problems even trying to build the tool set to
> look at eCos, any help would be desperately appreciated.
>
> I've been trying to build the gcc cross-compiler. I very carefully
> tried to follow the instructions on
> http://sourceware.cygnus.com/ecos/tools/linux-arm-elf.html
>
> On one system (2.2.5-15 kernel, egcs-2.91.66), I get a bunch of:
> _udivsi3
> /bin/sh: arm-elf-ar: command not found
> _divsi3
> /bin/sh: arm-elf-ar: command not found
> _umodsi3
> /bin/sh: arm-elf-ar: command not found
> and then the make aborts.
And does arm-elf-ar definitely exist in your tools install directory? By
any chance, is the --prefix/--exec-prefix you used when configuring
binutils different from the --prefix/--exec-prefix you used for gcc?
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next reply other threads:[~2000-04-05 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 13:12 Paul Kinzelman [this message]
2000-04-06 8:58 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2000-04-05 12:07 Paul Kinzelman
2000-04-05 12:15 ` Jonathan Larmour
2000-04-05 13:33 ` Grant Edwards
2000-04-10 0:16 ` Andrew Lunn
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=A71E53794EDDD211945E009027468857239FA1@isdnts02.isdcorp.com \
--to=paulk@isdcorp.com \
--cc=ecos-discuss@sourceware.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).