From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/dbus-python: fix build failure due to wrong auto-detected extra libs
Date: Thu, 4 Apr 2019 22:51:22 +0200 [thread overview]
Message-ID: <20190404225122.04f97af3@windsurf> (raw)
In-Reply-To: <20190404185228.112789-1-giulio.benetti@micronovasrl.com>
Hello,
On Thu, 4 Apr 2019 20:52:28 +0200
Giulio Benetti <giulio.benetti@micronovasrl.com> wrote:
> Using Python 3, during configuration, if PYTHON_EXTRA_LIBS is not
> defined, ./configure will launch a python script to retrieve LIBS and
> SYSLIBS variables, but this is done using host-python resulting in
> obtaining libraries that are not present in target. So while trying to
> link configuration test it fails complaining it can't find a
> library(i.e. libintl).
>
> Set PYTHON_EXTRA_LIBS the same as PYTHON_LIBS to be sure host libs are
> not used at all.
>
> Fixes:
> http://autobuild.buildroot.net/results/4078ee9e8aa304f044dc92e9345c28341349d468/
>
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
So it started failing with the introduction of gettext-tiny ? Do we
understand why it makes a difference for dbus-python ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-04-04 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 18:52 [Buildroot] [PATCH] package/dbus-python: fix build failure due to wrong auto-detected extra libs Giulio Benetti
2019-04-04 18:55 ` Giulio Benetti
2019-04-04 20:51 ` Thomas Petazzoni [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=20190404225122.04f97af3@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.