From: David Fernandez <david.fernandez.work@googlemail.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: Stanislav Meduna <stano@meduna.org>,
eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: Re: [ECOS] Re: eCos arm-eabi GNU tools - test release 4.6.3-20120623
Date: Thu, 28 Jun 2012 20:05:00 -0000 [thread overview]
Message-ID: <4FECB8DC.1000100@googlemail.com> (raw)
In-Reply-To: <4FEB399D.60503@siva.com.mk>
On 27/06/12 17:49, Ilija Kocho wrote:
> On 27.06.2012 18:38, Stanislav Meduna wrote:
>> On 27.06.2012 18:22, David Fernandez wrote:
>>
>>>> You will find multilibs for all architectures of interest for eCos under
>>>> gnutools/arm-eabi/lib/gcc/arm-eabi/4.6.3/ directory. This multilib
>>>> configuration is produced by gcc-4.6.3-ecos-120524_t-arm-elf.diff.
>>> Ilija, are you then saying that gcc does not do it right as-is, and we
>>> need to patch it?
>> FWIW I do not remember such problems - I am compiling for an ARM9
>> and a thumb2 with the same toolchain and it works. I did not test
>> 4.6.3 specifically, but it worked for 4.5.something compiled
>> under MinGW (although with other problems) and works for 4.7
>> canadian cross (built on linux targeting MinGW and compiling
>> for eCos).
>>
>> As far as I remember the abovementioned patch only tweaks what
>> multilibs from the zillion possible actually get build.
> Correct, eCos' patch instructs GCC builder what libs (i.e. for which
> targets) are of interest for eCos.
>
> Ilija.
>
Then, is it usually necessary to patch gcc or prepare its source files
in a special way (other than just using the configure command) to get
the C libraries compiled for several architectures, cpus, and modes?
--
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-28 20:05 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
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 [this message]
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=4FECB8DC.1000100@googlemail.com \
--to=david.fernandez.work@googlemail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=ilijak@siva.com.mk \
--cc=stano@meduna.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).