From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Building RPi toolchain with 2014.05
Date: Tue, 26 Aug 2014 10:23:38 +0200 [thread overview]
Message-ID: <20140826082338.GA3925@free.fr> (raw)
In-Reply-To: <lthbud$oba$1@ger.gmane.org>
Malte, Al,
On 2014-08-26 09:11 +0200, Malte Forkel spake thusly:
> with buildroot 2013.05, I could create a toolchain for Raspberry Pi with
> $ make rpi_defconfig
> $ make toolchain
> If I try the same with buildroot 2014.05, i.e.
> $ make raspberrypi_defconfig
> $ make toolchain
> the log ends with
> >>> toolchain-buildroot undefined Extracting
> >>> toolchain-buildroot undefined Patching
> >>> toolchain-buildroot undefined Configuring
> >>> toolchain-buildroot undefined Building
> >>> toolchain-buildroot undefined Installing to target
> >>> toolchain undefined Extracting
> >>> toolchain undefined Patching
> >>> toolchain undefined Configuring
> >>> toolchain undefined Building
> >>> toolchain undefined Installing to target
> and the directory output/toolchain is not created.
>
> What am I missing?
I just tested the master branch, and it does build the toolchain
sucessfully.
But the toolchain does not end up in output/toolchain/. It is located in
output/host/ and can be called with, for example:
/path/to/buildroot/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-08-26 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 7:11 [Buildroot] Building RPi toolchain with 2014.05 Malte Forkel
2014-08-26 8:23 ` Yann E. MORIN [this message]
2014-08-26 17:52 ` Malte Forkel
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=20140826082338.GA3925@free.fr \
--to=yann.morin.1998@free.fr \
--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.