From: Geir Harris Hedemark <geir@dod.no>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Problems with ecosSWtools and thumb-elf
Date: Mon, 12 Jul 1999 05:23:00 -0000 [thread overview]
Message-ID: <xq3pv1yoy4g.fsf@hridil.ifi.uio.no> (raw)
I have been looking into using ecos and its tools for an embedded
ARM7TDMI ASIC we are doing.
I seem to be able to compile to the arm-elf target without problems,
but when I compile for the thumb-elf target, things move into an
endless loop when libgcc1 and libgcc2 is compiled.
I am compiling on a Solaris 2.6 box. config.status looks like this for
the thumb-arb target:
../ecosSWtools-arm-990321/src/configure
--with-gcc-version-trigger=/data/nova/imp/software/ecosSWtools-arm-990321/src/gcc/version.c
--host=sparc-sun-solaris2.6 --target=thumb-elf
--prefix=/local/hacks/arm --nf --norecursion
My $PATH is pruned maximally. That should not cause any problems,
especially since arm-elf seems to compile ok and provide usable code.
Two questions: Has anyone run into similar problems and been able to
solve them? I have looked at the gcc Makefiles, and they have
significant differences, but none I am competent enough to point an
accusatory finger at.
If not, could someone please throw the appropriate .a files in my
direction (libgcc1.a and libgcc2.a, I guess)? I don't have access to
any commercial tools I can compile the assembly files with since we
wanted to check the cygnus tools out before spending an enourmous
amount of money.
Geir
next reply other threads:[~1999-07-12 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-12 5:23 Geir Harris Hedemark [this message]
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
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=xq3pv1yoy4g.fsf@hridil.ifi.uio.no \
--to=geir@dod.no \
--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).