OpenWrt Forum Archive

Topic: strange package dependencies

The content of this topic has been archived on 22 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

I'm having a problem with some strange dependencies in an older release (r32854), but this have also happened to me in the latest trunk:

I compile the binaries, I choose some I2C kernel module packages to be part of the image (kmod-i2c-algo-bit and kmod-i2c-core), but it seems they are not included. I then go to the trunk/bin/atheros/packages and download the .ipk files to the router and then try to install it manually. However, some of them fail because it seems there is a dependency of a specific kernel version.

Well, if everything was compiled all together, why am I having this dependency problem?


root@OpenWrt:/# wget http://192.168.2.10/kmod-i2c-core_3.3.8-1_atheros.ipk
Connecting to 192.168.2.10 (192.168.2.10:80)
kmod-i2c-core_3.3.8- 100% |*******************************|   729   0:00:00 ETA
root@OpenWrt:/# wget http://192.168.2.10/kmod-i2c-algo-bit_3.3.8-1_atheros.ipk
Connecting to 192.168.2.10 (192.168.2.10:80)
kmod-i2c-algo-bit_3. 100% |*******************************|  4368   0:00:00 ETA
root@OpenWrt:/#
root@OpenWrt:/# opkg install kmod-i2c-core_3.3.8-1_atheros.ipk
Installing kmod-i2c-core (3.3.8-1) to root...
Configuring kmod-i2c-core.
root@OpenWrt:/# opkg install kmod-i2c-algo-bit_3.3.8-1_atheros.ipk
Installing kmod-i2c-algo-bit (3.3.8-1) to root...
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-                i2c-algo-bit:
 *      kernel (= 3.3.8-1-3ce16ba1a832aa4aaace48620d7e9b54) *
 * opkg_install_cmd: Cannot install package kmod-i2c-algo-bit.

Any suggestion? What are the minimum kernel modules to have a PCF8574 working?

Thanks in advance,
Jabss

"make clean" first to ensure that the kernel and all the modules surely get built at the same time. The dependecy logic regarding kernel options was changed a few months ago to a too strict dependency checking and it is pretty difficult to get it right for kmod modules unless you compile everything from scratch on the same run.

Alternatively use opkg's force option to ignore dependencies for modules you know to be suitable.

Also regularly use make defconfig or make menuconfig to make sure that all changes in module dependencies get taken into the .config

(Last edited by hnyman on 3 Aug 2012, 11:49)

The discussion might have continued from here.