From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Missing Python Mako dependency
Date: Wed, 16 May 2018 13:28:36 +0200 [thread overview]
Message-ID: <20180516112835.GA29963@lenoch> (raw)
On systems without Python Mako build is failing with:
----------------------------------
target: host-system-python.prepare
----------------------------------
Checking for Python ...
Checking for Python libxml2 bindings ...
Checking for Python Mako ...
ptxdist: error: Python mako module not found! Please install python-mako (debian)
make: *** [/home/ladis/src/ptxdist/rules/host-system-python.make:28: /home/ladis/src/peoplemetr/SimEarTools/dist/build/platform-igep2/state/host-system-python.prepare] Error 1
Do we want to check for it in configure.ac or provide host package?
Side note: I barely agree with Rob Ladley, but he made pretty valid point
in distant past which I still do remember. In short, he never get the
point of install stage of "rootfs makefile".
So what if we make configure.ac just an another PTXdist stage and select
host packages needed to be compiled based on configure output?
ladis
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2018-05-16 11:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180516112835.GA29963@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