Dixi quod…
>I’ll do that now: I’ve applied all our latest m68k patches
>to the gcj-4.6 source tree and will rebuild that (takes about
>3-4 days on my fastest VMs) and upload that to unreleased,
>then binNMU ecj against that (it was previously built by
>gcj-4.4).
This appears to have fixed my issu
Hello group,
This post is a bit off-topic since I am not actually trying to bootstrap
gcc-4.6.3 on Debian but on another m68k system.
I have been tinkering with my NeXTstation Turbo Color for quite a while and
among other things I was able to (almost) port gcc-3.2.3. At least I have the
C por
Vaugha Brewchuk dixit:
>This post is a bit off-topic since I am not actually trying to
>bootstrap gcc-4.6.3 on Debian but on another m68k system.
That doesn’t prevent you from taking clues from Debian, such as,
which patches to apply, right? ;-)
>And hence my question: has anyone successfully bo
Vaugha Brewchuk dixit:
>ICE while compiling unwind-dw2.c:
What executable format do you use on NeXTstep?
Is that Mach-O or something similarily cr…uel, or ELF?
I’m asking because, TTBOMK, unwind-dw2.c is used for
DWARF2 unwinding which is some ELF thing. Maybe you
can have a peek at the configu
On Thu, 17 May 2012, Vaugha Brewchuk wrote:
>
> ... And hence my question: has anyone successfully bootstrapped
> gcc-4.6.3 on m68k?
No, I've never bootstrapped gcc on m68k, but I've seen ICEs with cross
compilers over the years.
>
> ... I also wonder whether perhaps a different gcc-4 versi
On 2012-05-17, at 8:38 PM, Thorsten Glaser wrote:
Thank you very much for this response and also for your other post referencing
the Debian m68k patches. I will apply the patches on the next go through the
build.
> Vaugha Brewchuk dixit:
>
>> ICE while compiling unwind-dw2.c:
>
> What exec
On 2012-05-17, at 8:55 PM, Finn Thain wrote:
>
> On Thu, 17 May 2012, Vaugha Brewchuk wrote:
>
>>
>> ... And hence my question: has anyone successfully bootstrapped
>> gcc-4.6.3 on m68k?
>
> No, I've never bootstrapped gcc on m68k, but I've seen ICEs with cross
> compilers over the years.
>
Vaugha Brewchuk dixit:
>it and see what happens. Unfortunately I will not know for at least 12
>hours what the outcome is :-). Yes, just the genattrtab takes over 9.5
>hours to execute on a 33 MHz 68040. It is an exercise in patience and
>a humbling reminder of the years gone by.
Don’t worry, it’
Vaugha Brewchuk dixit:
>The biggest challenge on the NeXT is that the libraries are approx. 20
>years old. What is there of POSIX, is very broken, and many of the
>standard c library functions are completely obsolete. So even once a
>compile is built and works well, many tests tend to fail.
Well,
9 matches
Mail list logo
