Hi,

> > ... a real linux kernel (or whatever).
> 
> Yup; we still have a Phytec board laying around somewhere in 
> the lab, but we never managed to do anything useful with it, 
> because at the time we started, there was no CodeSourcery 
> activity visible wrt. gcc, and the freescale stuff was not usable.

Yes, indeed. But with the latest GCC version on SVN trunk there should
some usable support for v4e cores now :-) Just another good reason to
put the mcf548x into consideration for our next platform. As an
long-yeared m68k/coldfire fan, I would really like to do some work with
this core.

> Then I would go the patch way; what you can also do is make a 
> big patch from gcc-4.2-latest to CVS as of some date, and 
> start from there.

I agree. Probably it's best to use the latest official 4.2.1 GCC version
and apply some hand-generated monster patch to the latest trunk version.
At least this would fit best into the ptxdist framework.

> > GLibC Ports 2.6.1 seems to support these latest GCC improvements 
> > already.
>
> Good start.

I hope it's not just vapor code :-)

> > line 16: -E: command not found
> 
> Hmmm, I've seen that before. However, I cannot remember the 
> reason; would be good to have a look at the code.

Maybe this problem is gone with the latest GCC version. Otherwise I will
post a patch here, so everyone can try.

> Looks like you are doing some serious work on that. I can 
> give you rw access to the repository, so you could check the 
> config into the trunk.

Thanks. This will really simplify my work as I can store working
milestones directly to where they belong. 

I would also like to create some updated configs for ARM, MIPS etc using
GCC 4.2.1 and glibc 2.6.1. Just to keep the OSELAS toolchains as much
up-to-date as possible.

> If you want to, please send me an encrypted mail with your 
> favourite svn password.

I will do. I first need to setup my gpg stuff at company.

Regards
Carsten




____________
Virus checked by G DATA AntiVirusKit
Version: AVKA 17.387 from 17.08.2007

-- 
ptxdist mailing list
[email protected]

Reply via email to