From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3] gpsd: version bump 2.39 -> 3.19
Date: Sun, 27 Oct 2019 23:29:10 +0100 [thread overview]
Message-ID: <20191027222910.GB9169@lenoch> (raw)
In-Reply-To: <20191027162539.GH30823@pengutronix.de>
Hi Michael,
thanks for suggestions (and before you notice, there's more to fix than
those undefined symbols - dependencies are missing as well, so it is easy
to produce configuration which does not make much sense :))
Meanwhile I looked into gpsd's SConstruct file:
https://gitlab.com/gpsd/gpsd/blob/master/SConstruct#L1191
As I'm passing CROSS_PYTHON3 as target_python and CROSS_PYTHON3
is a script, sys.executable returns path to host-python and
all that configuration queried later using host-python
is wrong. Simply dropping this line fixes it.
https://gitlab.com/gpsd/gpsd/blob/master/SConstruct#L1705
Here our cross-python wrapper returns
INCLUDEPY = "/usr/include/python3.7m"
which is of course wrong for cross-compilation.
Above two changes are enough to cross-compile package...
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-10-27 22:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 7:33 [ptxdist] [PATCH 0/2] add scons conf tool and let gpsd to use it Ladislav Michl
2019-10-25 7:34 ` [ptxdist] [PATCH 1/2] add scons conf tool Ladislav Michl
2019-10-25 7:55 ` Michael Olbrich
2019-10-25 23:09 ` Ladislav Michl
2019-10-27 6:30 ` Michael Olbrich
2019-11-15 19:19 ` Ladislav Michl
2019-11-16 10:08 ` Michael Olbrich
2019-11-18 21:15 ` Ladislav Michl
2019-10-25 7:35 ` [ptxdist] [PATCH 2/2] gpsd: version bump 2.39 -> 3.19 Ladislav Michl
2019-10-25 8:16 ` Michael Olbrich
2019-10-25 13:17 ` [ptxdist] [PATCH v2] " Ladislav Michl
2019-10-25 13:38 ` Michael Olbrich
2019-10-25 13:58 ` Ladislav Michl
2019-10-25 23:13 ` [ptxdist] [PATCH v3] " Ladislav Michl
2019-10-27 6:22 ` Michael Olbrich
2019-10-27 16:25 ` Michael Olbrich
2019-10-27 22:29 ` Ladislav Michl [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=20191027222910.GB9169@lenoch \
--to=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.de \
/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