All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11236] New: util-linux fails to build on Travis CI when python also selected
Date: Thu, 16 Aug 2018 14:40:19 +0000	[thread overview]
Message-ID: <bug-11236-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=11236

            Bug ID: 11236
           Summary: util-linux fails to build on Travis CI when python
                    also selected
           Product: buildroot
           Version: 2018.02.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: frankv at helium.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Here is a link to the build output.  Notice that Python.h cannot be located.

https://gist.github.com/fvasquez/1d4e94b37bd3388a3e6051d03d25fbd2

The failure only occurs when building on Travis CI.  The same defconfig builds
just fine on my Ubuntu 16.04 laptop.  I tried adding python-dev to apt packages
in .travis.yml to no avail.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2018-08-16 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 14:40 bugzilla at busybox.net [this message]
2018-08-16 15:12 ` [Buildroot] [Bug 11236] util-linux fails to build on Travis CI when python also selected bugzilla at busybox.net
2018-08-16 18:17 ` 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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.