[Buildroot] [PATCH 3/3] rpi-fw: New package

Maxime Hadjinlian maxime.hadjinlian at gmail.com
Sun Jan 6 14:47:17 UTC 2013


On Sun, Jan 6, 2013 at 3:26 PM, Peter Korsgaard <jacmet at uclibc.org> wrote:
>>>>>> "Floris" == Floris Bos <bos at je-eigen-domein.nl> writes:
>
> Hi,
>
>  Floris> Fails to install.
>  Floris> You need to create the target/boot directory first.
>
>  Floris> ==
>
>  Floris> /usr/bin/install -D -m 0644
>  Floris> /hdd/max/dev/tmp/buildroot/output/build/rpi-fw-76d0ac38f16b6343c6155c80db1e4758b3a5838a/boot/bootcode.bin
>  Floris> /hdd/max/dev/tmp/buildroot/output/target/boot/
>  Floris> /usr/bin/install: target
>  Floris> /hdd/max/dev/tmp/buildroot/output/target/boot/' is not a directory: No
>  Floris> such file or directory
>  Floris> make: ***
>  Floris> [/hdd/max/dev/tmp/buildroot/output/build/rpi-fw-76d0ac38f16b6343c6155c80db1e4758b3a5838a/.stamp_target_installed]
>  Floris> Error 1
>  Floris> ==
>
> That's the point of using install -D (create dest dirs as needed), but
> you need to provide it with the destination file name as well - E.G
> $(TARGET_DIR)/boot/bootcode.bin
>
>  Floris> But another question would be if bootloader files really should be
>  Floris> installed under target.
>  Floris> Keep in mind that the Raspberry Pi boot files are normally kept on a
>  Floris> FAT partition seperate from the root file system.
>
> Indeed, it probably makes more sense to just put it in IMAGES_DIR
> instead.
How about putting them all in a rpi-firmware folder inside IMAGES_DIR
? I don't want to just throw them in this folder, it would be a pain
afterwards since they all go in the same place.
>
> --
> Bye, Peter Korsgaard
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot



More information about the buildroot mailing list