From: David Fernandez <david.fernandez.work@googlemail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: eCos arm-eabi GNU tools - test release 4.6.3-20120623
Date: Wed, 27 Jun 2012 11:29:00 -0000 [thread overview]
Message-ID: <CAA6dH32Bqa1mYW9xnnc-TgAsdM6b_8H9EJWOqTDT68TcqKT7mQ@mail.gmail.com> (raw)
In-Reply-To: <4FEAAF76.60703@dallaway.org.uk>
>> Could you provide a link to the patch tarball? I usually build the
>> tool-chain, and like to try that.
>
> You should find the patch tarball on your local eCos mirror site at:
>
> gnutools/src/test/ecos-gnutools-20120623-patches.tar.bz2
>
Yes, it works. Great!
Do you know anything on the multilib question? My experience is that,
if you don't set the default cpu and mode appropriately, gcc will
compile newlib's crt0.S using the wrong default options, and you end
up with a crt0.o with ARM32 code where you would expect thumb or
thumb-2... I don't know if the gcc-4.6.3 sources have this problem,
but surely the gcc-4.7.1 has it, unless you know of some other
configuration option that makes this work fine.
--
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:[~2012-06-27 11:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 11:08 [ECOS] " John Dallaway
2012-06-26 11:44 ` [ECOS] Fwd: " Ilija Kocho
2012-07-27 11:37 ` Alex Schuilenburg
2012-07-30 9:38 ` Ilija Kocho
2012-07-30 10:09 ` Sergei Gavrikov
2012-07-31 11:48 ` Alex Schuilenburg
2012-06-26 21:50 ` [ECOS] " David Fernandez
2012-06-27 7:00 ` John Dallaway
2012-06-27 11:29 ` David Fernandez [this message]
2012-06-27 12:09 ` Ilija Kocho
2012-06-27 16:22 ` David Fernandez
2012-06-27 16:38 ` Stanislav Meduna
2012-06-27 16:49 ` Ilija Kocho
2012-06-28 20:05 ` David Fernandez
2012-06-28 20:01 ` David Fernandez
2014-06-13 10:25 ` [ECOS] eCos arm-eabi GNU tools - " John Dallaway
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=CAA6dH32Bqa1mYW9xnnc-TgAsdM6b_8H9EJWOqTDT68TcqKT7mQ@mail.gmail.com \
--to=david.fernandez.work@googlemail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).