I have compiled optimised (target arch, LTO, etc) x86 build for my APU2 and everything is great, apart from the non-functional "Update lists" button in LuCI:
Which box have I forgotten to tick in the make menuconfig
?
I have compiled optimised (target arch, LTO, etc) x86 build for my APU2 and everything is great, apart from the non-functional "Update lists" button in LuCI:
Which box have I forgotten to tick in the make menuconfig
?
Are you just making a statement, or asking a question?
Sorry. Wasn’t trying to be brazen, just didn’t grasp the context properly
For LuCI, menuconfig
should select the package by selecting LuCI/Collections/luci - Selects: PACKAGE_libc [=y] && PACKAGE_luci-app-opkg [=y] && PACKAGE_luci-light
You can select it individually from
LuCI/Applications/luci-app-opkg
from the .config
CONFIG_PACKAGE_libc=y
CONFIG_PACKAGE_luci-app-opkg=y
CONFIG_PACKAGE_luci=y
CONFIG_PACKAGE_luci-light=y
Are you able to opkg update
on the commmand line?
root@router:~# opkg update
root@router:~# echo $?
0
root@router:~#
Well, returns true, so /tmp/opkg-lists
should be populated and by default the GUI should also display the packages in System/Software
.
Do your customfeeds.conf
and distfeeds.conf
exist?
/tmp/opkg-lists
is an empty folder.
# add your custom package feeds here
#
# src/gz example_feed_name http://www.example.com/path/to/files
distfeeds.conf
does not exist.
There’s your problem.
EDIT: If you installed a squash fs, you should find a copy in /rom/etc/opkg/distfeeds.conf
.
If you installed an ext4 fs and you haven’t cleaned your buildroot, enter your buildroot and use find . -name distfeeds.conf
That should return a distfeeds.conf
you can use to recreate it to/etc/opkg/distfeeds.conf
It may not be quite that easy. There is no clean distfeeds.conf file in the source code, instead it is parsed from available feeds during compilation time.
But yes, after compilation, there should be a clean file in the created root directory copy.
(post deleted by author)
Negative, there is no distfeeds.conf
under the buildroot.
I see only feeds.buildinfo
under the /bin/targets/x86/64
.
Odd ¯\_(ツ)_/¯
. Per @hnyman this uses your build feeds.
This is what I get from my most current X86-64 buildroot:
user@Vostro:~/8-mini/openwrt$ find . -name distfeeds.conf
./build_dir/target-x86_64_musl/root.orig-x86/etc/opkg/distfeeds.conf
./build_dir/target-x86_64_musl/root-x86/etc/opkg/distfeeds.conf
./build_dir/target-x86_64_musl/linux-x86_64/base-files/.pkgdir/base-files/etc/opkg/distfeeds.conf
./build_dir/target-x86_64_musl/linux-x86_64/base-files/ipkg-x86_64/base-files/etc/opkg/distfeeds.conf
./staging_dir/target-x86_64_musl/root-x86/etc/opkg/distfeeds.conf
If you are building from x86-64 Snapshot you can use this for /etc/opkg/distfeeds
src/gz openwrt_core https://downloads.openwrt.org/snapshots/targets/x86/64/packages
src/gz openwrt_base https://downloads.openwrt.org/snapshots/packages/x86_64/base
src/gz openwrt_luci https://downloads.openwrt.org/snapshots/packages/x86_64/luci
src/gz openwrt_packages https://downloads.openwrt.org/snapshots/packages/x86_64/packages
src/gz openwrt_routing https://downloads.openwrt.org/snapshots/packages/x86_64/routing
If building from a release, just replace snapshots
with release/release version
. This should get you going atm to generate your opkg lists.