From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>,
"eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] extern __inline__ and optimisation problems
Date: Wed, 21 Oct 2009 16:05:00 -0000 [thread overview]
Message-ID: <c09652430910210904p3b25e9acp425de772c9b4a59c@mail.gmail.com> (raw)
In-Reply-To: <20091021154001.GA4391@sg-laptop>
> Hm, I do not expect that it's possible to mix native host archive
> (libopenocd.a) is built using host headers/glibc and eCos archives
> (libtarget.a, libextras.a) are built with eCos headers/libc even for
> Linux synthetic target together.
I'm not (willingly) mixing host and eCos stuff. I'm crossbuilding
using autotools to eCos binaries.
This works fine for my arm-elf target, but something goes
haywire with arm-eabi and gcc. I suspect that it might be
a gcc 3 vs. gcc 4 problem. My suspicion is that I've got one
option too many or too little...
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-10-21 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 9:57 Øyvind Harboe
2009-10-21 13:59 ` Sergei Gavrikov
2009-10-21 15:16 ` Øyvind Harboe
2009-10-21 15:40 ` Sergei Gavrikov
2009-10-21 16:05 ` Øyvind Harboe [this message]
2009-10-21 16:15 ` Sergei Gavrikov
2009-10-21 16:50 ` Øyvind Harboe
2009-10-21 18:41 ` Sergei Gavrikov
2009-10-22 7:43 ` Øyvind Harboe
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=c09652430910210904p3b25e9acp425de772c9b4a59c@mail.gmail.com \
--to=oyvind.harboe@zylin.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).