public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ARM Thumb - not working under Linux either
Date: Sat, 10 Feb 2001 18:43:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20010210214233.00ad9b30@larwe.com> (raw)
In-Reply-To: <3A846595.AA61BFFA@redhat.com>

Hello Jonathan,

> > Do you have any insight on why I can't get eCos compiled with Thumb
> > interworking? It would be an acceptable workaround for me if I could have
>
>I had a quick look. What you are seeing is messages like the following?
>
>home/jlarmour/sourceware/test/arm-elf/H-i686-pc-linux-gnu/lib/gcc-lib/arm-elf/2.97/../../../../arm-elf/bin/ld:
>_div_df.o(__divdf3): warning: interworking not enabled.
>
>This object is actually from libgcc - part of the compiler. It has not been
>built with -mthumb-interwork.

Yeah, and thank you for pointing out this very dumb mistake. I didn't think 
of libgcc at all; I had this feeling in my head that all I was linking was 
eCos and my app, despite having written the makefile by hand :/

>You probably need to edit (in your gcc sources) gcc/config/arm/t-arm-elf
>and uncomment:
>
># MULTILIB_OPTIONS    += mno-thumb-interwork/mthumb-interwork
># MULTILIB_DIRNAMES   += normal interwork
># MULTILIB_EXCEPTIONS += *mapcs-26/*mthumb-interwork*

Excellent suggestion, thanks. I will try that tonight or tomorrow. Right 
now I am wrestling with a couple of sourcefiles that no longer compile 
under the new gcc (they are part of mpeg2dec and it seems to be a new 
preprocessor bug).

=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."

  reply	other threads:[~2001-02-10 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 11:01 Lewin A.R.W. Edwards
2001-02-09  9:46 ` Jonathan Larmour
2001-02-09 12:47   ` Lewin A.R.W. Edwards
2001-02-09 13:48     ` Jonathan Larmour
2001-02-10 18:43       ` Lewin A.R.W. Edwards [this message]
2001-02-09 10:15 ` Bart Veer
2001-02-09 12:55   ` Lewin A.R.W. 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=4.3.2.7.2.20010210214233.00ad9b30@larwe.com \
    --to=larwe@larwe.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.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).