From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11236] util-linux fails to build on Travis CI when python also selected
Date: Thu, 16 Aug 2018 15:12:06 +0000 [thread overview]
Message-ID: <bug-11236-163-lW69sb7aq9@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11236-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11236
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Frank,
As discussed on IRC, this is an environment problem on TravisCI.
I suggested you investigate what /opt/pyenv/shims is for, and similarly
for all the other stuff in PATH. You may have to sanitise the PATH
somehow before calling Buildroot.
Otherwise, there's not much we can do about it... :-/
> I tried adding python-dev
Which I explained on IRC was useless because your error is about building
util-linux for the target, so the host python devel files are useless.
Closing as not reproducible on a standard environment...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-08-16 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 14:40 [Buildroot] [Bug 11236] New: util-linux fails to build on Travis CI when python also selected bugzilla at busybox.net
2018-08-16 15:12 ` bugzilla at busybox.net [this message]
2018-08-16 18:17 ` [Buildroot] [Bug 11236] " bugzilla at busybox.net
2018-08-18 0:24 ` bugzilla at busybox.net
2018-08-18 7:23 ` bugzilla at busybox.net
2018-08-20 15:26 ` bugzilla at busybox.net
2018-08-28 10:52 ` bugzilla at busybox.net
2018-08-28 10:53 ` bugzilla at busybox.net
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=bug-11236-163-lW69sb7aq9@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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