Re: [OpenWrt-Devel] Packages were found, but none compatible with the architectures configured
I recall having similar issues when using a recent trunk compiled image (after the kernel upgrade) and trying to use a kmod package from the 8.09.1 repository ... I guess it's the kernel version. ede On 20.10.2009 12:33, ZioPRoTo (Saverio Proto) wrote: # opkg install kmod-sched Collected errors: * Packages were found, but none compatible with the architectures configured I had the same problem with weekend upgrading some packages on same devices running 8.09.1 tag, and packages were compiled using the trunk toolchain. I don't know exactly if this is your case, but for example the Atheros target changed architecture name from "mips" to "atheros_uClibc-0.9.30.1". So if your firmware was compiled before the target name change, and you are now compiling the packages with a recent toolchain, the opkg will fail its check because it thinks you are installing a package for a wrong target. I have no idea if this only applies for the Atheros target or also for other targets. Saverio ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Packages were found, but none compatible with the architectures configured
> # opkg install kmod-sched > Collected errors: > * Packages were found, but none compatible with the architectures configured I had the same problem with weekend upgrading some packages on same devices running 8.09.1 tag, and packages were compiled using the trunk toolchain. I don't know exactly if this is your case, but for example the Atheros target changed architecture name from "mips" to "atheros_uClibc-0.9.30.1". So if your firmware was compiled before the target name change, and you are now compiling the packages with a recent toolchain, the opkg will fail its check because it thinks you are installing a package for a wrong target. I have no idea if this only applies for the Atheros target or also for other targets. Saverio ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Packages were found, but none compatible with the architectures configured
I'm trying to upgrade some packages I just built from an updated trunk (r18050) and getting: # opkg install kmod-sched Collected errors: * Packages were found, but none compatible with the architectures configured Hardware is an ASUS WL500GP: # uname -a Linux gw 2.6.25.20 #1 Sat Feb 7 13:49:36 EST 2009 mips unknown The package's control file says: Package: kmod-sched Version: 2.6.30.8-1 Depends: kernel (=2.6.30.8-1) Provides: Source: package/kernel Section: kernel Priority: optional Maintainer: OpenWrt Developers Team Architecture: brcm47xx Installed-Size: 251800 Description: Kernel schedulers for IP traffic (Yes, I know the kernel version of this package doesn't match the running kernel. That will be remedied once I have the necessary kmod packages installed.) In any case, how is opkg verifying this mismatch? Is it comparing the Architecture: tag in the control file to $(uname -m)? If so, why is the Architecture: tag in my packages wrong? BTW: kernel module packages really ought to be named/versioned such that I can have more than one kmod-sched installed at the same time, for different kernels. Thanx! b. signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
