From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8781] New: Unable to build uboot for imx28evk
Date: Thu, 10 Mar 2016 10:20:25 +0000 [thread overview]
Message-ID: <bug-8781-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8781
Bug ID: 8781
Summary: Unable to build uboot for imx28evk
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: cycaxo at gmx.net
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 6386
--> https://bugs.busybox.net/attachment.cgi?id=6386&action=edit
build log
I am trying to use buildroot-2016.02 for the freescale imx28evk. Unfortunately,
I am not able to build uboot for this board. I was able to successfully build
images for another board (i.e. beaglebone), so I can exclude that there is a
problem with my environment.
My procedure was the following:
1. make freescale_imx28evk_defconfig
--> # configuration written to /buildroot-2016.02/.config
2. make
--> make[2]:
/buildroot-2016.02/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc:
Command not found
I am using Ubuntu 14.04LTS 64bit with all the required packages for building on
a x64 system (at least it works for beaglebone).
Please find attached the log file.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-03-10 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 10:20 bugzilla at busybox.net [this message]
2016-03-10 13:40 ` [Buildroot] [Bug 8781] Unable to build uboot for imx28evk bugzilla at busybox.net
2016-03-24 19:41 ` bugzilla at busybox.net
2016-04-19 21:27 ` 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-8781-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