public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc
@ 2008-09-25  0:26 Øyvind Harboe
  2008-09-26  7:43 ` Sergei Gavrikov
  2008-09-26 14:14 ` simon.kallweit
  0 siblings, 2 replies; 7+ messages in thread
From: Øyvind Harboe @ 2008-09-25  0:26 UTC (permalink / raw)
  To: eCos Disuss

I've been toying around with building GCC toolchains(as one does...).

They are ready for testing if anyone is interested:

http://mail.zylin.com/pipermail/zylin-discuss_zylin.com/2008-September/000557.html

Feedback welcome!



W.r.t. eCos libstdc++ posix threads support they are not available here
as they require being built for the specific HAL in question. libstdc++ w/posix
threads works great under eCos though :-)


-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc
  2008-09-25  0:26 [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc Øyvind Harboe
@ 2008-09-26  7:43 ` Sergei Gavrikov
  2008-09-26  8:57   ` Øyvind Harboe
  2008-09-26 14:14 ` simon.kallweit
  1 sibling, 1 reply; 7+ messages in thread
From: Sergei Gavrikov @ 2008-09-26  7:43 UTC (permalink / raw)
  To: Øyvind Harboe; +Cc: eCos Disuss

Øyvind Harboe wrote:
> I've been toying around with building GCC toolchains(as one does...).
> 
> They are ready for testing if anyone is interested:
> 
> http://mail.zylin.com/pipermail/zylin-discuss_zylin.com/2008-September/000557.html
> 
> Feedback welcome!

Øyvind, thank you for your contribution. Before to start download I read
a point on the http://www.zylin.com/gccbinary.html page:

  The binaries contain the authoritative source of what build options
  that were used.

Does it mean what everyone can find all build options (and patches if
any one were applied) inside the bloat archives to replicate your builds
from GNU sources? Is there a guide how to build the stuff in the
archives? Like as an official eCos guide:
http://ecos.sourceware.org/ecos/build-toolchain.html

If it does mean, can you please to public 'the authoritative source'? in
text/html form on your web? Thank you.

Sergei


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc
  2008-09-26  7:43 ` Sergei Gavrikov
@ 2008-09-26  8:57   ` Øyvind Harboe
  2008-09-26  9:03     ` Sergei Gavrikov
  0 siblings, 1 reply; 7+ messages in thread
From: Øyvind Harboe @ 2008-09-26  8:57 UTC (permalink / raw)
  To: Sergei Gavrikov; +Cc: eCos Disuss

On Fri, Sep 26, 2008 at 9:38 AM, Sergei Gavrikov <sg@belvok.com> wrote:
> Øyvind Harboe wrote:
>> I've been toying around with building GCC toolchains(as one does...).
>>
>> They are ready for testing if anyone is interested:
>>
>> http://mail.zylin.com/pipermail/zylin-discuss_zylin.com/2008-September/000557.html
>>
>> Feedback welcome!
>
> Øyvind, thank you for your contribution. Before to start download I read
> a point on the http://www.zylin.com/gccbinary.html page:
>
>  The binaries contain the authoritative source of what build options
>  that were used.

Yes. Run gcc -v.

As in "authortative" meaning that if I wrote something on the web
page, the actual options used *could* be different. Cycle times
to do these sort of builds are *long* so it is something I tinker
with occasionally.

> Does it mean what everyone can find all build options (and patches if
> any one were applied) inside the bloat archives to replicate your builds
> from GNU sources? Is there a guide how to build the stuff in the
> archives? Like as an official eCos guide:
> http://ecos.sourceware.org/ecos/build-toolchain.html

Nope. I'm still learning here... I may write up some more once I get
better hang of this whole building GCC thing... The link above is
one of the more useful links that I found though.

> If it does mean, can you please to public 'the authoritative source'? in
> text/html form on your web? Thank you.

You can download them from the GCC mirrors, why would you want
them from Zylin?

Don't you know where the GCC mirrors are?



-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc
  2008-09-26  8:57   ` Øyvind Harboe
@ 2008-09-26  9:03     ` Sergei Gavrikov
  2008-09-26 12:55       ` Øyvind Harboe
  0 siblings, 1 reply; 7+ messages in thread
From: Sergei Gavrikov @ 2008-09-26  9:03 UTC (permalink / raw)
  To: Øyvind Harboe; +Cc: Sergei Gavrikov, eCos Disuss

Øyvind Harboe writes:
> Sergei Gavrikov wrote:
> > Øyvind Harboe wrote:
> >> I've been toying around with building GCC toolchains(as one does...).
> >>
> >> They are ready for testing if anyone is interested:
> >>
> >> http://mail.zylin.com/pipermail/zylin-discuss_zylin.com/2008-September/000557.html
> >>
> >> Feedback welcome!
> >
> > Øyvind, thank you for your contribution. Before to start download I read
> > a point on the http://www.zylin.com/gccbinary.html page:
> >
> >  The binaries contain the authoritative source of what build options
> >  that were used.
> 
> Yes. Run gcc -v.

It's wondeful to know about dumping GCC build options and it's specs
after downloading XXL archive :-) I have 128/32K connection. And what's
about binutils, newlib, gdb? Did you configure that using the prefix and
the target/host/build triplet only? I guessed you didn't.

> You can download them from the GCC mirrors, why would you want
> them from Zylin?
> 
> Don't you know where the GCC mirrors are?

Yes, I do. More that I have the copies of the referenced packages on my
disk and therefore I asked you about your steps (guide ?) just in a text
form, but no 7-zip :-) to replicate any build.  I dislike RTBF and
most like UTSL
http://web.bilkent.edu.tr/Online/Jargon30/JARGON_R/RTFB.HTML
http://web.bilkent.edu.tr/Online/Jargon30/JARGON_U/UTSL.HTML

You asked about a feedback. And I guess that the testers would compare
their build steps with your ones.

In any case, thank you for your spent time, bogomips and disk storage to
contribute the toolchains.
 
http://www.zylin.com/gcc/binaries/linux/nocortex-arm-elf.tar.bz2
  (try: 6) => `nocortex-arm-elf.tar.bz2'
Connecting to 192.168.0.1:3128... connected.
Proxy request sent, awaiting response... 206 Partial Content
Length: 54,147,927 (52M), 44,574,970 (43M) remaining [application/x-tar]

19% [++++++>                              ] 10,440,434    --.--K/s  ETA

I wonder what I'll got then... GCC/newlib/binutils/gdb sources?

Sergei


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc
  2008-09-26  9:03     ` Sergei Gavrikov
@ 2008-09-26 12:55       ` Øyvind Harboe
  0 siblings, 0 replies; 7+ messages in thread
From: Øyvind Harboe @ 2008-09-26 12:55 UTC (permalink / raw)
  To: Sergei Gavrikov; +Cc: eCos Disuss

On Fri, Sep 26, 2008 at 10:58 AM, Sergei Gavrikov <sg@belvok.com> wrote:
> Øyvind Harboe writes:
>> Sergei Gavrikov wrote:
>> > Øyvind Harboe wrote:
>> >> I've been toying around with building GCC toolchains(as one does...).
>> >>
>> >> They are ready for testing if anyone is interested:
>> >>
>> >> http://mail.zylin.com/pipermail/zylin-discuss_zylin.com/2008-September/000557.html
>> >>
>> >> Feedback welcome!
>> >
>> > Øyvind, thank you for your contribution. Before to start download I read
>> > a point on the http://www.zylin.com/gccbinary.html page:
>> >
>> >  The binaries contain the authoritative source of what build options
>> >  that were used.
>>
>> Yes. Run gcc -v.
>
> It's wondeful to know about dumping GCC build options and it's specs
> after downloading XXL archive :-) I have 128/32K connection. And what's
> about binutils, newlib, gdb? Did you configure that using the prefix and
> the target/host/build triplet only? I guessed you didn't.

It takes time to test & document all this, but my intention is to get more info
on the web page itself once the dust settles.

>> You can download them from the GCC mirrors, why would you want
>> them from Zylin?
>>
>> Don't you know where the GCC mirrors are?
>
> Yes, I do. More that I have the copies of the referenced packages on my
> disk and therefore I asked you about your steps (guide ?) just in a text
> form, but no 7-zip :-) to replicate any build.  I dislike RTBF and
> most like UTSL
> http://web.bilkent.edu.tr/Online/Jargon30/JARGON_R/RTFB.HTML
> http://web.bilkent.edu.tr/Online/Jargon30/JARGON_U/UTSL.HTML
>
> You asked about a feedback. And I guess that the testers would compare
> their build steps with your ones.

I'm travelling down a lot of blind alleys while putting together this.

Once the dust settles and I'm reasonably satisified that my scripts
are helpful to anyone else, I'll upload them.

> In any case, thank you for your spent time, bogomips and disk storage to
> contribute the toolchains.
>
> http://www.zylin.com/gcc/binaries/linux/nocortex-arm-elf.tar.bz2
>  (try: 6) => `nocortex-arm-elf.tar.bz2'
> Connecting to 192.168.0.1:3128... connected.
> Proxy request sent, awaiting response... 206 Partial Content
> Length: 54,147,927 (52M), 44,574,970 (43M) remaining [application/x-tar]
>
> 19% [++++++>                              ] 10,440,434    --.--K/s  ETA
>
> I wonder what I'll got then... GCC/newlib/binutils/gdb sources?

Sources not included in that download.

If you tought 34mByte was big for a binary, how about a 150mByte arm-elf
multilb download w/zip, which is why I'm using .7r for Windows binaries :-)



-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc
  2008-09-25  0:26 [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc Øyvind Harboe
  2008-09-26  7:43 ` Sergei Gavrikov
@ 2008-09-26 14:14 ` simon.kallweit
  2008-09-26 15:14   ` Øyvind Harboe
  1 sibling, 1 reply; 7+ messages in thread
From: simon.kallweit @ 2008-09-26 14:14 UTC (permalink / raw)
  To: Øyvind Harboe; +Cc: eCos Disuss

Hi

I just tried to compile my work-in-progress Cortex-M3 port with your 
arm-elf compiler. Without much luck though, as it seems that your 
compiler is compiled for hardware floating point architectures, or did I 
get something wrong? Also it occured to me, that you got a dependency to 
the mpfr library, which should not really be there I guess. At least it 
wasn't with all the other toolchains I used/built so far.

Did you do any tests based on Cortex-M3? Or only Cortex-A8?

Best regards,
Simon

Øyvind Harboe wrote:
> I've been toying around with building GCC toolchains(as one does...).
>
> They are ready for testing if anyone is interested:
>
> http://mail.zylin.com/pipermail/zylin-discuss_zylin.com/2008-September/000557.html
>
> Feedback welcome!
>
>
>
> W.r.t. eCos libstdc++ posix threads support they are not available here
> as they require being built for the specific HAL in question. libstdc++ w/posix
> threads works great under eCos though :-)
>
>
>   


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc
  2008-09-26 14:14 ` simon.kallweit
@ 2008-09-26 15:14   ` Øyvind Harboe
  0 siblings, 0 replies; 7+ messages in thread
From: Øyvind Harboe @ 2008-09-26 15:14 UTC (permalink / raw)
  To: simon.kallweit; +Cc: eCos Disuss

On Fri, Sep 26, 2008 at 4:02 PM, simon.kallweit@intefo.ch
<simon.kallweit@intefo.ch> wrote:
> Hi
>
> I just tried to compile my work-in-progress Cortex-M3 port with your arm-elf
> compiler. Without much luck though, as it seems that your compiler is
> compiled for hardware floating point architectures, or did I get something
> wrong?  Also it occured to me, that you got a dependency to the mpfr library,
> which should not really be there I guess. At least it wasn't with all the
> other toolchains I used/built so far.

Would you be willing to help out testing and post a bit more detail on what
 you did, what you expected and your results?

Post to http://zylin.com/mailman/listinfo/zylin-discuss_zylin.com, I believe
the ecos-discuss mailing list has interest in a *working* Cortex toolchain
rather than the work in progress as it is now :-)

> Did you do any tests based on Cortex-M3? Or only Cortex-A8?

Nope. It is ready for such testing and I appreciate your feedback.



-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2008-09-26 14:14 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-09-25  0:26 [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc Øyvind Harboe
2008-09-26  7:43 ` Sergei Gavrikov
2008-09-26  8:57   ` Øyvind Harboe
2008-09-26  9:03     ` Sergei Gavrikov
2008-09-26 12:55       ` Øyvind Harboe
2008-09-26 14:14 ` simon.kallweit
2008-09-26 15:14   ` Øyvind Harboe

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).