All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Discussion of the angstrom distribution development
	<angstrom-distro-devel@linuxtogo.org>
Subject: Re: [Angstrom-devel] Can't build gstreamer-ti
Date: Wed, 11 Aug 2010 12:15:35 -0400	[thread overview]
Message-ID: <20100811161535.GI7189@denix.org> (raw)
In-Reply-To: <20100811072031.GA7282@mi.fu-berlin.de>

On Wed, Aug 11, 2010 at 09:20:31AM +0200, Henning Heinold wrote:
> On Tue, Aug 10, 2010 at 03:27:10PM -0400, Denys Dmytriyenko wrote:
> > On Tue, Aug 10, 2010 at 06:48:55AM -0600, Gary Thomas wrote:
> > > On 08/10/2010 04:58 AM, Gary Thomas wrote:
> > >> But I've downloaded those tools and was able to build this recipe just
> > >> a few weeks ago. I think something in the staged packaging has broken it.
> > >
> > > I worked past this problem by installing a symlink by hand to my DVSDK 
> > > installed tools.
> > >
> > > Next problem :-(
> > >
> > > | Engine.c:(.text+0x19d4): undefined reference to `__aeabi_uidiv'
> > >
> > > How were these packages built to be put on the Angstrom package feed?
> > > Am I doing something wrong?
> > 
> > As Henning already said, Codec Engine only builds and works with binutils 2.18 
> > (which IS Angstrom's default, btw) on TI OMAP3/DaVinci processors.
> 
> Hm,
> 
> that is not 100% correct, but at the moment I dont have the time to make the patches for oe.

Until you have patches to fix the situation, I say it's 100% correct :) :)

-- 
Denys



      reply	other threads:[~2010-08-11 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C607E6C.2030104@mlbassoc.com>
     [not found] ` <AANLkTi=zp9r7hoym3kFEx9hpCgoQ8iOBVNZ6FhN7F4q6@mail.gmail.com>
2010-08-10 10:58   ` [Angstrom-devel] Can't build gstreamer-ti Gary Thomas
2010-08-10 12:48     ` Gary Thomas
2010-08-10 14:49       ` Henning Heinold
2010-08-10 19:27       ` Denys Dmytriyenko
2010-08-11  7:20         ` Henning Heinold
2010-08-11 16:15           ` Denys Dmytriyenko [this message]

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=20100811161535.GI7189@denix.org \
    --to=denis@denix.org \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=openembedded-devel@lists.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.