[OpenWrt-Devel] Using the SDK vs toolchain for custom packages; SDK HW requirements;

[Stan Grishin]

Is there a difference between using pre-built SDK (from
downloads.openwrt.org) vs the toolchain from git for building custom
packages? I've been using SDK, but here and from PMs on the forum I see
toolchain recommended -- why?

Also, I have only been installing only some libs + luci-base
with ./scripts/feeds install, however I'm seeing recommendations to install
all packages (./scripts/feeds install -a) which on my system (Ubuntu 18.04
8 GB RAM, 2 vCPUs, 160 GB SSD VM) result in the segfault.

After I've downloaded and unpacked a fresh SDK for mvebu/19.07.2, then in
the SDK directory:
rm -f .config && make defconfig
./scripts/feeds update -f
./scripts/feeds install -a
make -j1 V=sc
...
make[3]: ***
[/home/stangri/development/Builder/SDK_mvebu_19.07.2/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/linux-mvebu_cortexa9/base-files/.configured_ef91f8dd9e1b18f9e888cabc5c198db0_8e081b74cf069e1e6800a5bbcbb282f0]
Segmentation fault (core dumped)
make[3]: Leaving directory
'/home/stangri/development/Builder/SDK_mvebu_19.07.2/feeds/base/package/base-files'
time: package/feeds/base/base-files/compile#0.23#0.06#0.41
package/Makefile:111: recipe for target
'package/feeds/base/base-files/compile' failed
make[2]: *** [package/feeds/base/base-files/compile] Error 2
make[2]: Leaving directory
'/home/stangri/development/Builder/SDK_mvebu_19.07.2'
package/Makefile:107: recipe for target
'/home/stangri/development/Builder/SDK_mvebu_19.07.2/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/stamp/.package_compile'
failed
make[1]: ***
[/home/stangri/development/Builder/SDK_mvebu_19.07.2/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/stamp/.package_compile]
Error 2
make[1]: Leaving directory
'/home/stangri/development/Builder/SDK_mvebu_19.07.2'
/home/stangri/development/Builder/SDK_mvebu_19.07.2/include/toplevel.mk:218:
recipe for target 'world' failed
make: *** [world] Error 2

Am I doing something wrong?

Also, I don't believe this is addressed in wiki for neither SDK nor
toolchain, but in order to build a custom luci package, here's what I do --
I init a git directory in package/luci and with sparse checkout only
checkout luci.mk (and build directory of in18n.pl) from the
appropriate branch, then place custom luci apps in
package/luci/applications. I believe it was also recommended by one of the
core developers but in case it wasn't and it's something I came up with
myself -- is that the proper procedure for building custom (as in not in
the feeds) luci apps?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20200413/35f834f6/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel