All of lore.kernel.org
 help / color / mirror / Atom feed
* Disabling ipv6
@ 2016-02-10  9:28 Chris Trobridge
  0 siblings, 0 replies; 6+ messages in thread
From: Chris Trobridge @ 2016-02-10  9:28 UTC (permalink / raw)
  To: yocto

[-- Attachment #1: Type: text/plain, Size: 2501 bytes --]

I hit this issue experimenting with disabling ipv6, as Todd did originally, with an odd error about not being able to build the native sdk.
It's not a problem for me but is there a recommended way for disabling a libc distro feature like ipv6 without creating a whole new distro?  Does libc really require ipv6?  I can see it's the features in DISTRO_FEATURES_LIBC that are critical.
For the purposes of this experiment I added to local.conf to get it working:DISTRO_FEATURES_remove = "ipv6"DISTRO_FEATURES_LIBC_remove = "ipv6"
But I expect I will create a new distro at some point.
Cheers,Chris
On Tuesday 27 October 2015 08:45:26 Burton, Ross wrote:> On 26 October 2015 at 20:16, Todd Efflam <todd.efflam at gmail.com> wrote:> > Thanks for the tip.  We tried adding this to the local.conf file but> > it failed with the following error:> > ERROR: Nothing PROVIDES 'glibc'> > ERROR: glibc was skipped: missing required distro feature 'ipv6' (not> > in DISTRO_FEATURES)> > Ouch.  That's surely not right.> > The commit that introduced this was:> > commit 97899bc908a421295d814801ff86edeb9304d2fd> Author: Chen Qi <Qi.Chen at windriver.com>> Date:   Thu Jul 3 11:23:42 2014 +0800> >     eglibc: check for required distro features> >     If users accidently override the DISTRO_FEATURES in local.conf,>     then build failures occur for lack of libc functions.> >     All features in DISTRO_FEATURES_LIBC should be in DISTRO_FEATURES.>     That's why this patch let the recipe inherit distro_features_check>     class and set REQUIRED_DISTRO_FEATURES to "${DISTRO_FEATURES_LIBC}".> >     [YOCTO #6381]> > But the entire point of the logic in glibc-options is to make these> options, well, optional.> > It looks like the required_distro_features use in eglibc is misguided.  Can> you comment out the REQUIRED_DISTRO_FEATURES assignment in glibc.inc and> verify that it then builds fine without ipv6 enabled?
Ah yes, I meant to get back to this at some point as I didn't really like how this was fixed previously either (see https://bugzilla.yoctoproject.org/show_bug.cgi?id=6381 for details of the problem). It seems to me that we should:
1) Fix the glibc recipes so that they handle an empty libc configuration or error out much earlier with a sensible message if that's not possible
2) Properly detect when DISTRO_FEATURES has been "zapped" via += in local.conf or elsewhere and show an error/warning about that.
Cheers,Paul
-- 
Paul EggletonIntel Open Source Technology Centre
 		 	   		  

[-- Attachment #2: Type: text/html, Size: 3831 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Disabling ipv6
  2015-10-27  8:45     ` Burton, Ross
@ 2015-10-27  8:54       ` Paul Eggleton
  0 siblings, 0 replies; 6+ messages in thread
From: Paul Eggleton @ 2015-10-27  8:54 UTC (permalink / raw)
  To: yocto

On Tuesday 27 October 2015 08:45:26 Burton, Ross wrote:
> On 26 October 2015 at 20:16, Todd Efflam <todd.efflam@gmail.com> wrote:
> > Thanks for the tip.  We tried adding this to the local.conf file but
> > it failed with the following error:
> > ERROR: Nothing PROVIDES 'glibc'
> > ERROR: glibc was skipped: missing required distro feature 'ipv6' (not
> > in DISTRO_FEATURES)
> 
> Ouch.  That's surely not right.
> 
> The commit that introduced this was:
> 
> commit 97899bc908a421295d814801ff86edeb9304d2fd
> Author: Chen Qi <Qi.Chen@windriver.com>
> Date:   Thu Jul 3 11:23:42 2014 +0800
> 
>     eglibc: check for required distro features
> 
>     If users accidently override the DISTRO_FEATURES in local.conf,
>     then build failures occur for lack of libc functions.
> 
>     All features in DISTRO_FEATURES_LIBC should be in DISTRO_FEATURES.
>     That's why this patch let the recipe inherit distro_features_check
>     class and set REQUIRED_DISTRO_FEATURES to "${DISTRO_FEATURES_LIBC}".
> 
>     [YOCTO #6381]
> 
> But the entire point of the logic in glibc-options is to make these
> options, well, optional.
> 
> It looks like the required_distro_features use in eglibc is misguided.  Can
> you comment out the REQUIRED_DISTRO_FEATURES assignment in glibc.inc and
> verify that it then builds fine without ipv6 enabled?

Ah yes, I meant to get back to this at some point as I didn't really like how 
this was fixed previously either (see 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6381 for details of the 
problem). It seems to me that we should:

1) Fix the glibc recipes so that they handle an empty libc configuration or 
error out much earlier with a sensible message if that's not possible

2) Properly detect when DISTRO_FEATURES has been "zapped" via += in local.conf 
or elsewhere and show an error/warning about that.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Disabling ipv6
  2015-10-26 20:16   ` Todd Efflam
@ 2015-10-27  8:45     ` Burton, Ross
  2015-10-27  8:54       ` Paul Eggleton
  0 siblings, 1 reply; 6+ messages in thread
From: Burton, Ross @ 2015-10-27  8:45 UTC (permalink / raw)
  To: Todd Efflam; +Cc: yocto

[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]

On 26 October 2015 at 20:16, Todd Efflam <todd.efflam@gmail.com> wrote:

> Thanks for the tip.  We tried adding this to the local.conf file but
> it failed with the following error:
> ERROR: Nothing PROVIDES 'glibc'
> ERROR: glibc was skipped: missing required distro feature 'ipv6' (not
> in DISTRO_FEATURES)
>

Ouch.  That's surely not right.

The commit that introduced this was:

commit 97899bc908a421295d814801ff86edeb9304d2fd
Author: Chen Qi <Qi.Chen@windriver.com>
Date:   Thu Jul 3 11:23:42 2014 +0800

    eglibc: check for required distro features

    If users accidently override the DISTRO_FEATURES in local.conf,
    then build failures occur for lack of libc functions.

    All features in DISTRO_FEATURES_LIBC should be in DISTRO_FEATURES.
    That's why this patch let the recipe inherit distro_features_check
    class and set REQUIRED_DISTRO_FEATURES to "${DISTRO_FEATURES_LIBC}".

    [YOCTO #6381]

But the entire point of the logic in glibc-options is to make these
options, well, optional.

It looks like the required_distro_features use in eglibc is misguided.  Can
you comment out the REQUIRED_DISTRO_FEATURES assignment in glibc.inc and
verify that it then builds fine without ipv6 enabled?

Cheers,
Ross

[-- Attachment #2: Type: text/html, Size: 2537 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Disabling ipv6
  2015-10-23 23:43 ` Burton, Ross
@ 2015-10-26 20:16   ` Todd Efflam
  2015-10-27  8:45     ` Burton, Ross
  0 siblings, 1 reply; 6+ messages in thread
From: Todd Efflam @ 2015-10-26 20:16 UTC (permalink / raw)
  To: Burton, Ross; +Cc: yocto

On Fri, Oct 23, 2015 at 4:43 PM, Burton, Ross <ross.burton@intel.com> wrote:
> In your distro configuration either define your own DISTRO_FEATURES entirely
> from scratch, or use DISTRO_FEATURES_remove = "ipv6".

Thanks for the tip.  We tried adding this to the local.conf file but
it failed with the following error:
ERROR: Nothing PROVIDES 'glibc'
ERROR: glibc was skipped: missing required distro feature 'ipv6' (not
in DISTRO_FEATURES)

I'm guessing this is because the feature hasn't actually been added to
the build yet.  We tried instead adding it to our custom layer's
layer.conf file but got the same error.  Finally, we added it to our
core-image-minimal.bbappend file and the image compiled, however ipv6
was still present in the image.  Any idea on which file we should add
this to?  I know you said in our distro config, is that the layer.conf
file?  We've been using core-image-minimal as our base image and
appending/adding our own recipes to this.  Thanks again for your help.

Best,
Todd


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Disabling ipv6
  2015-10-23 23:28 Todd Efflam
@ 2015-10-23 23:43 ` Burton, Ross
  2015-10-26 20:16   ` Todd Efflam
  0 siblings, 1 reply; 6+ messages in thread
From: Burton, Ross @ 2015-10-23 23:43 UTC (permalink / raw)
  To: Todd Efflam; +Cc: yocto

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]

On 24 October 2015 at 00:28, Todd Efflam <todd.efflam@gmail.com> wrote:

> We're trying to disable ipv6 in our build and are able to do so by
> directly editing the file
> meta/conf/distro/include/default-distrovars.inc and deleting "ipv6"
> from "DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace
> lib..."
>
> Is there a better way to disable ipv6 so that we can do this from
> within our own branch?
>

In your distro configuration either define your own DISTRO_FEATURES
entirely from scratch, or use DISTRO_FEATURES_remove = "ipv6".

Ross

[-- Attachment #2: Type: text/html, Size: 1024 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Disabling ipv6
@ 2015-10-23 23:28 Todd Efflam
  2015-10-23 23:43 ` Burton, Ross
  0 siblings, 1 reply; 6+ messages in thread
From: Todd Efflam @ 2015-10-23 23:28 UTC (permalink / raw)
  To: yocto

Hello,
We're trying to disable ipv6 in our build and are able to do so by
directly editing the file
meta/conf/distro/include/default-distrovars.inc and deleting "ipv6"
from "DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace
lib..."

Is there a better way to disable ipv6 so that we can do this from
within our own branch?

Thanks,
Todd


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2016-02-10  9:28 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-10  9:28 Disabling ipv6 Chris Trobridge
  -- strict thread matches above, loose matches on Subject: below --
2015-10-23 23:28 Todd Efflam
2015-10-23 23:43 ` Burton, Ross
2015-10-26 20:16   ` Todd Efflam
2015-10-27  8:45     ` Burton, Ross
2015-10-27  8:54       ` Paul Eggleton

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.