* [Buildroot] Building RPi toolchain with 2014.05
@ 2014-08-26 7:11 Malte Forkel
2014-08-26 8:23 ` Yann E. MORIN
0 siblings, 1 reply; 3+ messages in thread
From: Malte Forkel @ 2014-08-26 7:11 UTC (permalink / raw)
To: buildroot
Hi,
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?
Thanks,
Malte
^ permalink raw reply [flat|nested] 3+ messages in thread* [Buildroot] Building RPi toolchain with 2014.05
2014-08-26 7:11 [Buildroot] Building RPi toolchain with 2014.05 Malte Forkel
@ 2014-08-26 8:23 ` Yann E. MORIN
2014-08-26 17:52 ` Malte Forkel
0 siblings, 1 reply; 3+ messages in thread
From: Yann E. MORIN @ 2014-08-26 8:23 UTC (permalink / raw)
To: buildroot
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. |
'------------------------------^-------^------------------^--------------------'
^ permalink raw reply [flat|nested] 3+ messages in thread* [Buildroot] Building RPi toolchain with 2014.05
2014-08-26 8:23 ` Yann E. MORIN
@ 2014-08-26 17:52 ` Malte Forkel
0 siblings, 0 replies; 3+ messages in thread
From: Malte Forkel @ 2014-08-26 17:52 UTC (permalink / raw)
To: buildroot
Am 26.08.2014 um 10:23 schrieb Yann E. MORIN:
>
> 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
>
Yann,
thanks for your help! That's were the toolchain is in 2014.05, too.
Should have found it myself...
Regards,
Malte
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-08-26 17:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-08-26 7:11 [Buildroot] Building RPi toolchain with 2014.05 Malte Forkel
2014-08-26 8:23 ` Yann E. MORIN
2014-08-26 17:52 ` Malte Forkel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox