Some observations on things that build when you think they shouldn’t... This
is something I noticed a while ago and can construct an example, but have
been unable to understand why things work this way – bug or feature?
Let's say you have a package - call it utility xyzzy. In the Makefile, you
declare 2 additional packages: lib-x and lib-y along with the xyzzy utility.
lib-x is dependent on libfoo and libbar. lib-y is only dependent on libfoo
only. The xyzzy utility is dependent on lib-y and NOT lib-x. However, if I
select xyzzy and hence lib-y is selected by default, when you build, libbar
will be built (but not installed) even though it not selected in the build
config as you have observed.
/ted
On Mon, Nov 17, 2014 at 9:16 PM, Robert P. J. Day <rpj...@crashcourse.ca>
wrote:
i am out of ideas here ... i'm doing a full build for my archer c7
router and, when a package fails to build, i simply deselect that
package via "make menuconfig" (and, of course, any other packages that
select it) and restart the build.
at the moment, given that rrdtool failed to build, i deselected
it, but the build again failed trying to build rrdtool. i've verified
through "make menuconfig" that it is indeed deselected. here are the
lines in .config related to rrdtool:
$ grep rrdtool .config
CONFIG_PACKAGE_lighttpd-mod-rrdtool=m
CONFIG_PACKAGE_collectd-mod-rrdtool=m
# CONFIG_PACKAGE_rrdtool is not set
# CONFIG_PACKAGE_rrdtool1 is not set
$
i'm baffled ... given that rrdtool is clearly not selected for
building, why does a simple "make" insist on trying to build it? what
triviality am i overlooking?
rday
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
