Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8971] New: build for beaglebone fails
Date: Sat, 04 Jun 2016 14:56:20 +0000	[thread overview]
Message-ID: <bug-8971-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 8971
           Summary: build for beaglebone fails
           Product: buildroot
           Version: 2016.05
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: craigswank at fastmail.fm
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 6446
  --> https://bugs.busybox.net/attachment.cgi?id=6446&action=edit
build output

The build fails when I do:

  $ make beaglebone_defconfig
  $ make

I've attached the entire output of the make command.

I'm building on ubuntu 

?  buildroot git:(aa6fd11) ? uname -a
Linux sigatoka 3.19.0-49-generic #55-Ubuntu SMP Fri Jan 22 02:10:24 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
?  buildroot git:(aa6fd11) ? lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 15.04
Release:        15.04
Codename:       vivid

If anyone needs more info please ask, I can't think of anything else right now.

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

             reply	other threads:[~2016-06-04 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-04 14:56 bugzilla at busybox.net [this message]
2016-06-06 21:03 ` [Buildroot] [Bug 8971] build for beaglebone fails bugzilla at busybox.net
2016-06-12 19:30 ` 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-8971-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox