m68k gcc was Re: BSP for 5307

[Peter Barada]

>> Yes, I'm working on the coldfire changes for v3/v4/v4e, but I haven't
>> convinced the lawyers to sign off yet. 
>
>That can take time.  :(

Oh, don't I know!  :-)

>> I'm also having trouble
>> getting g++ to build with gcc-20020211.  I think in my version I'll
>> have all of Fiddes' patches, but I'll have to double check.
>
>Is David still providing up to date patches against gcc 3.0?  I haven't
>heard from him in a while.  Is it possible some of the patches are out
>of date?

I've tried building a *straight* g++-20020211, and it dies in
different ways for lots of targets (arm-elf, m68k-elf, sh-elf, etc).
I'm now starting over by pulling out *every* stock tool (gcc-20020211,
newlib-1.9.0, binutils-2.11.2, gdb-5.1) in a hopeful attempt to prove
that *I* screwed up somewhere along the line...

>> I'm also having trouble
>> getting g++ to build with gcc-20020211.  I think in my version I'll
>> have all of Fiddes' patches, but I'll have to double check.
>
>Is David still providing up to date patches against gcc 3.0?  I haven't
>heard from him in a while.  Is it possible some of the patches are out
>of date?

I've only found patches against gcc-2.95.3 on www.fiddes.net, so I
don't think Dave has any 3.0.x patches...

-- 
Peter Barada                                   Peter.Barada at motorola.com
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)