Re: Blackfin support

[Koen Kooi <k.kooi@student.utwente.nl>]

On 09-01-09 19:35, Tom Rini wrote:
> On Fri, Jan 09, 2009 at 05:22:43PM +0100, Koen Kooi wrote:
>> On 09-01-09 16:52, Tom Rini wrote:
>>> Hey all.  Has anyone built any of the blackfin boards recently?  I'm
>>> finding things like uClibc 0.9.29+ require -mfdpic which isn't in our
>>> gcc 4.1.x, is in gcc 4.2.x (but requires a patch to define __FDPIC__
>>> rather than __BFIN_FDPIC__) and other issues still.  Just seeing if
>>> anyone else has these things working before I start getting down and
>>> dirty.  Thanks!
>> I keep starting anew with blackfin support due to the current problems:
>>
>> * ADI uses their own 'distro', the rest of the world a custom buildroot
>> * You need to get gcc from blackfin SVN to get something to compile
>> * you need to choose either uclibc from blackfin svn or upstream uclibc
>
> Oh joy of joys.  Would it be a problem to import the ADI magic versions
> of thing (and SRC_URI_append_bfin) ?

Not at all, my local diff for that got blown away during the git 
transition, but it's a one liner for gcc_4.<something>.inc where you 
override SRC_URI to point to svn://bf.ucl.org
I hope you get the semi-shared lib thing to work, since that's what 
would be usefull for OE, but I can see the use for static binaries.
Did Richard merge his darwin stuff yet that allows shared libs to have 
custom extensions (.e.g .dylib for OSX)? That would make this a bit 
easier to handle.

regards,

Koen