All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Blackfin support
Date: Fri, 09 Jan 2009 17:22:43 +0100	[thread overview]
Message-ID: <gk7tkl$p1o$1@ger.gmane.org> (raw)
In-Reply-To: <20090109155223.GF400@smtp.west.cox.net>

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

When you get to the point of building uclibc, the fun starts, since 
uclinux (not uclibc) has no proper shared library support, so you have 
to choose an emulation method (fdpic being one of the options).
 From that point on it's downhill, since various parts of uclibc have 
fork() in their code, gcc will ICE on other parts, etc.

My latest attempt was:

http://dominion.thruhere.net/koen/cms/blackfin-toolchain-progress

I still have the board, so if you make some progress I can test it :)

regards,

Koen





  reply	other threads:[~2009-01-09 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 15:52 Blackfin support Tom Rini
2009-01-09 16:22 ` Koen Kooi [this message]
2009-01-09 18:35   ` Tom Rini
2009-01-09 20:51     ` Koen Kooi
2009-07-09  0:08   ` Mike Frysinger
2009-07-24 11:29     ` Dmitry Eremin-Solenikov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gk7tkl$p1o$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.