Bingo avr-li...@luna.dyndns.dk wrote:
You have to remember that Codesourcery is/was payed by ARM to
develop and maintain arm-gcc. So afaik. a lot of the patches hasn't
found their way into the official tree.
Yes, but that's no reason to not separate the stock GCC source tree
from the
Jens Bauer j...@bruger.mine.nu wrote:
I'll take a look at the Codesourcery toolchain anyway, it might
contain some good hints and tips. :)
I took a look at the Codesourcery code. The issue there is that all
you get is a large blurb of hacked up sourcecode, while Michael
Fischer separates his
I'll admit that I'd like to stay as close to the official releases as possible.
Which means I'd also like patches to be applied as early as possible (providing
that they're working and are acceptable, ofcourse)
IMHO: If patches are needed, they should be based upon an official release, not
some
Subject: Re: [avr-gcc-list] Trouble compiling avr-gcc 4.4.4 on Mac
OS X
Leopard with gcc-4.2 (Solved)
Regarding patches: The AVR-size patch; it's not yet officially added
to
binutils, is it ?
Correct, it is NOT added to binutils, and it very likely never will be
officially added.
Eric
Hi Eric,
I'm kinda going off-topic here...
Do you know if there's a reason for this, or is it just because it doesn't fit
in logically ?
(I find it a little cumbersome to update/fix patches every time a new official
release of a product is made).
Love,
Jens
Regarding patches: The AVR-size
As Jens Bauer wrote:
Do you know if there's a reason for this, or is it just because it
doesn't fit in logically ?
It is far too AVR-specific to go into a generic toolchain as GNU
binutils are. In order for being acceptable there, it would have to
be designed in a much more generic way, so it
compiling avr-gcc 4.4.4 on Mac
OS X
Leopard with gcc-4.2 (Solved)
As Jens Bauer wrote:
Do you know if there's a reason for this, or is it just because it
doesn't fit in logically ?
It is far too AVR-specific to go into a generic toolchain as GNU
binutils are. In order for being
On 2011-10-27 09:32, Joerg Wunsch wrote:
Jens Bauer j...@bruger.mine.nu wrote:
I'll take a look at the Codesourcery toolchain anyway, it might
contain some good hints and tips. :)
I took a look at the Codesourcery code. The issue there is that all
you get is a large blurb of hacked up
compiling avr-gcc 4.4.4 on Mac
OS X
Leopard with gcc-4.2 (Solved)
But at least before they were acquired by Mentor , i considered
Codesourcery to be the the latest in arm-gcc
I don't know what their status is after the acquisition.
I still consider them to be the latest in arm-gcc, just because
Jens Bauer j...@bruger.mine.nu wrote:
I used the same build of Yagarto as you mentioned.
Are you building on a PPC Mac ?
Nope, I don't have it.
I get duplicate symbols (___gmpz_abs).
I cannot find any ___gmpz_abs in GMP 4.3.2 which I am using.
Same as this:
On 2011-10-15 14:53, Jens Bauer wrote:
Hi Jörg,
I used the same build of Yagarto as you mentioned.
Are you building on a PPC Mac ?
GMP will not compile on a PPC Mac with GCC 4.0.1; but it *will* compile on an
intel Mac with GCC 4.0.1.
I get duplicate symbols (___gmpz_abs).
Same as this:
Hi Jörg,
I used the same build of Yagarto as you mentioned.
Are you building on a PPC Mac ?
GMP will not compile on a PPC Mac with GCC 4.0.1; but it *will* compile on an
intel Mac with GCC 4.0.1.
I get duplicate symbols (___gmpz_abs).
Same as this:
Hi Johann and Mark,
Good news to those, who got here, because they searched for this error-message.
I finally got gcc-4.5.3 to build, and 4.6.1 as well, without problems, read
on...
Johann wrote...
It seems that I *must* build the GMP/MPFR/MPC-libraries.
Strings GCC should build it for you.
Jens Bauer j...@bruger.mine.nu wrote:
I thought that I would 'get help' from building a Yagarto toolchain
(as it builds gcc-4.6.0 for ARM), but Yagarto (currently) fails on
my system; this is because it for some reason reverts to using
gcc-4.0 instead of gcc-4.2! -I'll try see if I can find
14 matches
Mail list logo