From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] gpsd: proper usage of prefix and DESTDIR
Date: Wed, 25 Jul 2012 10:55:08 +0200 [thread overview]
Message-ID: <20120725105508.1c7179df@skate> (raw)
In-Reply-To: <CAHt8ZCPHv7MR=WAvPRL5PxiTp=NsgDkhWKFusCEYgxiBtZPWXg@mail.gmail.com>
Le Wed, 25 Jul 2012 09:49:35 +0100,
Simon Dawson <spdawson@gmail.com> a ?crit :
> Yes, you're right. It was using the native compiler before your
> patches, but somehow managed to get through the build without falling
> over. Another problem then.
Can you share a defconfig that shows the problem? I've tested the build
with BR2_PACKAGE_PYTHON + BR2_PACKAGE_GPSD, and it just builds (even
though the output is completely incorrect: the gpsd Python modules are
installed in the wrong location and are built for the host rather than
the target).
Do you actually need the Python support in gpsd? :-)
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-25 8:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 22:10 [Buildroot] [PATCH 1/3] gpsd: proper usage of prefix and DESTDIR Thomas Petazzoni
2012-07-24 22:10 ` [Buildroot] [PATCH 2/3] gpsd: add patch to disable rpath Thomas Petazzoni
2012-07-25 8:50 ` Simon Dawson
2012-07-24 22:10 ` [Buildroot] [PATCH 3/3] qt: tune .pc files after installation in staging directory Thomas Petazzoni
2012-07-25 7:26 ` Simon Dawson
2012-07-25 7:43 ` Thomas Petazzoni
2012-07-25 7:57 ` Simon Dawson
2012-07-25 7:53 ` [Buildroot] [PATCH 1/3] gpsd: proper usage of prefix and DESTDIR Simon Dawson
2012-07-25 8:22 ` Thomas Petazzoni
2012-07-25 8:49 ` Simon Dawson
2012-07-25 8:50 ` Simon Dawson
2012-07-25 8:55 ` Thomas Petazzoni [this message]
2012-07-25 10:35 ` Simon Dawson
2012-07-25 14:11 ` Thomas Petazzoni
2012-07-25 14:27 ` Simon Dawson
2012-07-25 16:28 ` Thomas Petazzoni
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=20120725105508.1c7179df@skate \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox