Hi all, thanks to this[0] bug report I found that the ar71xx/generic ImageBuilder doesn't create any firmware images for profile OM2P when used with BIN_DIR.
My first guess is that it's somewhat related to a hard coded destination which doesn't handle BIN_DIR. At the very end of an "successful" build log: > if [ -e > "/home/aparcar/worker/imagebuilder/openwrt/18.06.2/ar71xx/generic/bin/targets/ar71xx/generic/openwrt-18.06.2-c9d037b0992cca4-ar71xx-generic-om2p-squashfs-factory.bin" > ]; then cp > "/home/aparcar/worker/imagebuilder/openwrt/18.06.2/ar71xx/generic/bin/targets/ar71xx/generic/openwrt-18.06.2-c9d037b0992cca4-ar71xx-generic-om2p-squashfs-factory.bin" > > "/home/aparcar/worker/imagebuilder/openwrt/18.06.2/ar71xx/generic/bin/targets/ar71xx/generic/openwrt-18.06.2-c9d037b0992cca4-ar71xx-generic-om2p-squashfs-sysupgrade.bin"; > fi Running the following commands $ make image PROFILE="OM2P" $ ls openwrt-18.06.2-ar71xx-generic-device-om2p.manifest openwrt-18.06.2-ar71xx-generic-vmlinux.bin openwrt-18.06.2-ar71xx-generic-om2p-squashfs-factory.bin openwrt-18.06.2-ar71xx-generic-vmlinux.elf openwrt-18.06.2-ar71xx-generic-om2p-squashfs-sysupgrade.bin openwrt-18.06.2-ar71xx-generic-vmlinux.lzma openwrt-18.06.2-ar71xx-generic-root.squashfs openwrt-18.06.2-ar71xx-generic-vmlinux-lzma.elf openwrt-18.06.2-ar71xx-generic-uImage-lzma.bin sha256sums $ make image PROFILE="OM2P" BIN_DIR="/tmp/test/" $ ls /tmp/test/ openwrt-18.06.2-ar71xx-generic-device-om2p.manifest openwrt-18.06.2-ar71xx-generic-vmlinux.elf openwrt-18.06.2-ar71xx-generic-root.squashfs openwrt-18.06.2-ar71xx-generic-vmlinux.lzma openwrt-18.06.2-ar71xx-generic-uImage-lzma.bin openwrt-18.06.2-ar71xx-generic-vmlinux-lzma.elf openwrt-18.06.2-ar71xx-generic-vmlinux.bin sha256sums Hopefully someone could fix this! Best regards, Paul [0]: https://github.com/libremesh/chef/issues/79 _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
