From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8616] New: Fail to build for raspberrypi_defconfig with big endian
Date: Wed, 20 Jan 2016 14:28:51 +0000 [thread overview]
Message-ID: <bug-8616-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8616
Bug ID: 8616
Summary: Fail to build for raspberrypi_defconfig with big
endian
Product: buildroot
Version: unspecified
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: paulonunes at mail.com
CC: buildroot at uclibc.org
Created attachment 6286
--> https://bugs.busybox.net/attachment.cgi?id=6286&action=edit
last lines of stdout on the failed execution
On building using raspberrypi_defconfig configuration and changing the
endianness to big endian, the buildroot fails to finish the build as attached
files describe in detail.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-01-20 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 14:28 bugzilla at busybox.net [this message]
2016-01-21 16:55 ` [Buildroot] [Bug 8616] Fail to build for raspberrypi_defconfig with big endian 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-8616-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.