All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: XBMC build for Raspberry Pi
Date: Wed, 05 Sep 2012 16:12:12 +0100	[thread overview]
Message-ID: <50476BCC.1090801@communistcode.co.uk> (raw)

Ok, so I'm delving in a little over my head here but you've got to start 
somewhere, right ;)

I'm trying to build XBMC for the Raspberry Pi and have run into the 
following error which I don't know how to fix:

configure: error: in 
`/home/jack/Projects/poky-rasp/raspberry/tmp/work/armv6-vfp-poky-linux-gnueabi/xbmc-11.0-r14+gitr1+5ea1d22052f4b6a13a10b1f2e80c90abfcd6023b/git':
configure: error:
   Could not link test program to Python. Maybe the main Python library 
has been
   installed in some non-standard library path. If so, pass it to configure,
   via the LDFLAGS environment variable.
   Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib"
============================================================================
    ERROR!
    You probably have to install the development version of the Python 
package
    for your distribution.  The exact name of this package varies among 
them.
============================================================================

Adding python-dev to DEPENDS seems to be a bit extreme, or is there 
another way around this?

Cheers,

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




             reply	other threads:[~2012-09-05 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 15:12 Jack Mitchell [this message]
2012-09-07  8:48 ` XBMC build for Raspberry Pi Jack Mitchell
2012-09-07  9:02   ` Henning Heinold
2012-09-07  9:12     ` Jack Mitchell

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=50476BCC.1090801@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --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.