Hi
> The final busybox configuration file is copied into the build root
> filesystem, you may verify your setup in
I checked that and IFUPDOWN is still selected in there.
> In general the busybox applet selection from the target directory works fine
I firmly believe in this being my own fault.
> maybe there are other dependencies which implicitly set CONFIG_IFUPDOWN.
I tried to grep the unpacked busybox source-package for 'select IFUPDOWN', I
believe that would give me direct dependencies. But there are none.
I then did a make menuconfig in that source directory and removed the applets
interactively. Then did a diff between the resulting .config and the one
logged by the T2 build.
This gave me:
< CONFIG_IFUPDOWN=y
< CONFIG_IFUPDOWN_IFSTATE_PATH="/var/run/ifstate"
< CONFIG_FEATURE_IFUPDOWN_IP=y
< CONFIG_FEATURE_IFUPDOWN_IP_BUILTIN=y
---
> # CONFIG_IFUPDOWN is not set
> CONFIG_IFUPDOWN_IFSTATE_PATH=""
> # CONFIG_FEATURE_IFUPDOWN_IP is not set
> # CONFIG_FEATURE_IFUPDOWN_IP_BUILTIN is not set
636,638c636,638
< CONFIG_FEATURE_IFUPDOWN_IPV4=y
< CONFIG_FEATURE_IFUPDOWN_IPV6=y
< CONFIG_FEATURE_IFUPDOWN_MAPPING=y
---
> # CONFIG_FEATURE_IFUPDOWN_IPV4 is not set
> # CONFIG_FEATURE_IFUPDOWN_IPV6 is not set
> # CONFIG_FEATURE_IFUPDOWN_MAPPING is not set
So I checked my $target/busybox.config again. I had
O CONFIG_IFUPDOWN
And now added
O CONFIG_IFUPDOWN_IFSTATE_PATH
O CONFIG_FEATURE_IFUPDOWN_IP
O CONFIG_FEATURE_IFUPDOWN_IP_BUILTIN
O CONFIG_FEATURE_IFUPDOWN_IPV4
O CONFIG_FEATURE_IFUPDOWN_IPV6
O CONFIG_FEATURE_IFUPDOWN_MAPPING
And rebuilt.
Bingo. It does not build ifup and ifdown into busybox.
Thank you very much! That takes me an important step further.
Ciao, MM
--
Marian Aldenhövel, Rosenhain 23, 53123 Bonn
http://www.marian-aldenhoevel.de"I ran some quick calculations on it. He's about 80% on the right
track. That leaves him only 20% dead when he crashes." Bob C
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2