All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OT: determining in `Makefile.in` the Python version/path
Date: Sun, 09 Jan 2011 23:17:52 +0100	[thread overview]
Message-ID: <4D2A3410.6090906@opendreambox.org> (raw)
In-Reply-To: <1294607270.4036.73.camel@mattotaupa>

On 01/09/2011 10:07 PM, Paul Menzel wrote:
> I tried to use `python-config` to determine the Python version [3].
> 
>         ifeq (arm, $(ARCH))
>         -# Force external python2.5 for now!
>         -LIBS +=-lpython2.5
>         +# Force external Python for now!
>         +LIBS += $(shell python-config --libs)
>          endif
> 
> This fails with the following error though documented in `log.do_compile`.
> 
>         Traceback (most recent call last):
>           File "/oe/build/angstrom-dev/sysroots/i686-linux/usr/bin/python-config", line 6, in <module>
>             from distutils import sysconfig
>           File "/oe/build/angstrom-dev/sysroots/i686-linux/usr/lib/python2.6/distutils/sysconfig.py", line 22, in <module>
>             PREFIX = os.path.normpath(sys.prefix).replace( os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
> 

For OE's Python, you need to set some variables in your recipe, e.g.:

EXTRA_OECONF = " \
        BUILD_SYS=${BUILD_SYS} \
        HOST_SYS=${HOST_SYS} \
        STAGING_INCDIR=${STAGING_INCDIR} \
        STAGING_LIBDIR=${STAGING_LIBDIR} \
"

Regards,
Andreas



  reply	other threads:[~2011-01-09 22:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09 21:07 OT: determining in `Makefile.in` the Python version/path Paul Menzel
2011-01-09 22:17 ` Andreas Oberritter [this message]
2011-01-10 10:46   ` Paul Menzel

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=4D2A3410.6090906@opendreambox.org \
    --to=obi@opendreambox.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.