Target-specific configuration, specifically busybox

View: New views
3 Messages — Rating Filter:   Alert me  

Target-specific configuration, specifically busybox

by Marian Aldenhövel-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I am struggling with the per-target-configuration of packages in T2.

Specifically I'd like to customize the set of busybox applets being
built.

In t2/packages/base/busybox.conf I found there is a mechanism to include
per-package busybox.config files. I checked the stock targets and found
a few examples.

So I built my t2/target/kbox/busybox.config and put in it

O CONFIG_IFUPDOWN

hoping to remove the ifup and ifdown applets from the build. They will
be provided by the rocknet package in my target. Unfortunately this does
not seem to make any difference to busybox.

To verify I checked in the src.busybox.... directory.

What am I missing here?

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

Re: Target-specific configuration, specifically busybox

by Michael Tross-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi Marian,

On 06.04.2008 19:59, Marian Aldenhövel wrote:

> Hi,
>
> I am struggling with the per-target-configuration of packages in T2.
>
> Specifically I'd like to customize the set of busybox applets being
> built.
>
> In t2/packages/base/busybox.conf I found there is a mechanism to include
> per-package busybox.config files. I checked the stock targets and found
> a few examples.
>
> So I built my t2/target/kbox/busybox.config and put in it
>
> O CONFIG_IFUPDOWN
>
> hoping to remove the ifup and ifdown applets from the build. They will
> be provided by the rocknet package in my target. Unfortunately this does
> not seem to make any difference to busybox.
>
> To verify I checked in the src.busybox.... directory.
>
> What am I missing here?

The final busybox configuration file is copied into the build root
filesystem, you may verify your setup in
$root/$prefix/doc/busybox/busybox.config. In general the busybox applet
selection from the target directory works fine, maybe there are other
dependencies which implicitly set CONFIG_IFUPDOWN.

Michael



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

Re: Target-specific configuration, specifically busybox

by Marian Aldenhövel-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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