From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] python: fix python-config for cross-compilation
Date: Tue, 01 Oct 2013 23:58:32 +0200 [thread overview]
Message-ID: <87y56cslfb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1380576047-21001-2-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Mon, 30 Sep 2013 23:20:45 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
Thomas> Some packages (trace-cmd) use python-config to find out which
Thomas> headers and libraries should be used to link against the Python
Thomas> libraries. By default, python-config returns paths that are
Thomas> inappropriate for cross-compilation: this patch fixes this by
Thomas> prepending those paths by the staging directory location.
My first thought was that this should just use PYTHON_CONFIG_SCRIPTS,
but looking closer at it, I see that it's actually a python script so it
won't work. It would be good to add a comment about this.
The shebang reads:
#!/usr/bin/python2.7
Now that we go to the effort to build a host-python I think it makes
sense to fixup the shebang as well - But:
./output/host/usr/bin/python output/staging/usr/bin/python2.7-config --cflags
-I/home/peko/source/buildroot/output/host/usr/include/python2.7 -I/home/peko/source/buildroot/output/host/usr/include/python2.7 -fno-strict-aliasing -O2 -I/home/peko/source/buildroot/output/host/usr/include -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes
E.G. your s/-I/-I$(STAGING_DIR)/ trick won't work (and it didn't work
before if the host python wasn't built with --prefix=/usr).
Thomas> We also fix one of the python*-config file to actually be a symbolic
Thomas> link to the script, rather than a copy of it.
This I don't see here:
ls -lah output/staging/usr/bin/python*-config
-rwxr-xr-x 1 peko peko 1.6K Oct 1 23:50 output/staging/usr/bin/python2.7-config
lrwxrwxrwx 1 peko peko 16 Oct 1 23:50 output/staging/usr/bin/python2-config -> python2.7-config
lrwxrwxrwx 1 peko peko 14 Oct 1 23:50 output/staging/usr/bin/python-config -> python2-config
Care to fix these issues and resubmit?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-10-01 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 21:20 [Buildroot] [PATCH 1/4] trace-cmd: fix largefile build problem Thomas Petazzoni
2013-09-30 21:20 ` [Buildroot] [PATCH 2/4] python: fix python-config for cross-compilation Thomas Petazzoni
2013-10-01 21:58 ` Peter Korsgaard [this message]
2013-10-02 7:13 ` Thomas Petazzoni
2013-10-02 7:43 ` Peter Korsgaard
2013-09-30 21:20 ` [Buildroot] [PATCH 3/4] python3: " Thomas Petazzoni
2013-09-30 21:20 ` [Buildroot] [PATCH 4/4] trace-cmd: improve Python support Thomas Petazzoni
2013-10-01 21:29 ` [Buildroot] [PATCH 1/4] trace-cmd: fix largefile build problem Peter Korsgaard
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=87y56cslfb.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox