All of lore.kernel.org
 help / color / mirror / Atom feed
From: Priya Agarwal <priyaiitmandi@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Error while trying to enable selinux support in custom image
Date: Tue, 17 Feb 2015 16:58:37 +0530	[thread overview]
Message-ID: <CALTPfpFroYMcfnn-SQZGYxsROm0nnD7g85K-h9Vv-OvWAD4m6w@mail.gmail.com> (raw)
In-Reply-To: <CALTPfpHrYrWhPje7ippkoTUwPgBAuzmhcTKWa0Knec-iSLtgBQ@mail.gmail.com>

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

I think I'll have to edit bblayers.conf to include path to meta-python and
networking-layer. However where is the path to networking layer. Is it same
as meta-networking.


On Tue, Feb 17, 2015 at 4:03 PM, Priya Agarwal <priyaiitmandi@gmail.com>
wrote:

> Hi,
>
> I want to add SELinux support in my custom imgae I am building for
> Freescale's T4240QDS Machine.
> I followed the steps given in FAQ section included in meta-selinux
> directory.
>
> However I am getting this error. How do I remove this.
>
> ERROR: Layer 'selinux' depends on layer 'meta-python', but this layer is
> not enabled in your configuration
> ERROR: Layer 'selinux' depends on layer 'networking-layer', but this layer
> is not enabled in your configuration
>
> I need to do this urgently.
> Thank You.
>
> Regards
>

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

      parent reply	other threads:[~2015-02-17 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 10:33 Error while trying to enable selinux support in custom image Priya Agarwal
2015-02-17 10:51 ` Priya Agarwal
     [not found]   ` <9BACABF0C6B14A4D8C33B42A795119BE1C4ED3BD@POCITMSEXMB06.LntUniverse.com>
2015-02-17 11:13     ` Priya Agarwal
     [not found]       ` <9BACABF0C6B14A4D8C33B42A795119BE1C4ED43E@POCITMSEXMB06.LntUniverse.com>
2015-02-17 11:28         ` Priya Agarwal
2015-02-17 11:28 ` Priya Agarwal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALTPfpFroYMcfnn-SQZGYxsROm0nnD7g85K-h9Vv-OvWAD4m6w@mail.gmail.com \
    --to=priyaiitmandi@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.