public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: jlarmour@cygnus.co.uk (Jonathan Larmour)
To: geir@dod.no
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Problems with ecosSWtools and thumb-elf
Date: Tue, 13 Jul 1999 10:47:00 -0000	[thread overview]
Message-ID: <199907131746.SAA21059@peshwari.cygnus.co.uk> (raw)
In-Reply-To: <xq3k8s496s9.fsf@hridil.ifi.uio.no>

In article < xq3k8s496s9.fsf@hridil.ifi.uio.no > you write:
>jlarmour@cygnus.co.uk (Jonathan Larmour) writes:
>> If you do go down that route, let the list know how you get on, and just
>> ask if you have any problems. I'm sure someone should be able to help.
>
>I did. I picked up binutils-2.9.1 and egcs-1.1.2. I compiled and
>installed binutils first, then egcs. The options to configure were
>--target=thumb-coff --prefix=/local/hacks/arm. For some reason there
>is no elf support for thumb in binutils-2.9.1. Or was it egcs? I
>forget.

Not in egcs-1.1.2, no. That's my fault for not specifying which version.
Sorry :-(. The place to get the latest snapshot is
ftp://egcs.cygnus.com/pub/egcs/snapshots/index.html

When gcc-2.95 comes out, you could use that instead.

I believe binutils-2.9.1 should be adequate though.

>Since I will use this in an embedded system which will not run *nix or
>even have a filesystem or a terminal, I did not have or need the
>standard *.h files (stdio.h and so on). Had to define "inhibit_libc"
>when compiling libgcc2.c so xgcc would not barf on some
>includes. According to the code, that can lead to problems.

If you download newlib from ftp://ftp.cygnus.com/pub/newlib/ , and put
symlinks in your egcs tree to the "newlib" and "libgloss" directories
in that distribution, that should work around some of the problems
you had further down. You also won't need to define inhibit_libc I
believe.

>The makefile did not find the assembler by itself, even if I was
>compiling egcs with the same prefix as binutils. I had to have
>thumb-coff-as in my path.

That doesn't surprise me. I think using the PATH is probably the right
thing.

>The tests failed. It said:
[snip] see above

>Seems I have solved my most immediate problem(s), but egcs seems to
>have poorer cross-target support than the ecos tools. Is this correct?

No, not if you have all the parts in place. We should ensure there is
documentation of how to do this for people in future.

Jifl
-- 
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
 my brains kept falling out."    || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/  These opinions are all my own fault

  reply	other threads:[~1999-07-13 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-12  5:23 Geir Harris Hedemark
1999-07-12  6:23 ` Ian Lance Taylor
1999-07-12  6:39 ` Jonathan Larmour
1999-07-12  7:39   ` Geir Harris Hedemark
1999-07-13  3:35   ` Geir Harris Hedemark
1999-07-13 10:47     ` Jonathan Larmour [this message]
1999-07-15  7:13       ` Geir Harris Hedemark
1999-07-15  7:35         ` Jonathan Larmour

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=199907131746.SAA21059@peshwari.cygnus.co.uk \
    --to=jlarmour@cygnus.co.uk \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=geir@dod.no \
    /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).