All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: yocto-patches@lists.yoctoproject.org
Subject: Re: [yocto-patches] [meta-rockchip][PATCH] linux-yocto-dev: fix build
Date: Tue, 11 Jun 2024 13:18:43 -0400	[thread overview]
Message-ID: <20240611171843.GB34413@localhost> (raw)
In-Reply-To: <CADkTA4OV-gAFN+=Af1XDUwczqLTJWPKcdJs3wBwyUP2HaKjBWA@mail.gmail.com>

On Tue 2024-06-11 @ 11:17:31 AM, Bruce Ashfield via lists.yoctoproject.org wrote:
> On Tue, Jun 11, 2024 at 11:01 AM Bruce Ashfield
> <bruce.ashfield@gmail.com> wrote:
> >
> > On Tue, Jun 11, 2024 at 10:29 AM Quentin Schulz via
> > lists.yoctoproject.org
> > <quentin.schulz=cherry.de@lists.yoctoproject.org> wrote:
> > >
> > > Hi Trevor,
> > >
> > > On 6/11/24 4:06 PM, Trevor Woerner via lists.yoctoproject.org wrote:
> > > > The linux-yocto-dev build was failing with:
> > > >       | ERROR: modpost: vmlinux: local symbol 'security_path_rmdir' was exported
> > > >
> > > > Disabling some filesystem-related security options fixes the build.
> > > >
> > >
> > > Is this the case for every board, including non-Rockchip ones?
> > >
> > > Is Bruce aware of those issues? Shouldn't this rather be fixed in
> > > oe-core instead?
> >
> > Ross had mentioned something like this a week or so ago,
> > but I haven't seen it locally yet.
> >
> > It's an aufs6 export that is causing the issue, I'm looking into
> > it now.
> 
> I see the issue with the exports. One slipped outside of an ifdef
> and is causing issues.
> 
> It should all be fixed shortly.

w00t! Thanks :-)


      reply	other threads:[~2024-06-11 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 14:06 [meta-rockchip][PATCH] linux-yocto-dev: fix build Trevor Woerner
2024-06-11 14:29 ` [yocto-patches] " Quentin Schulz
2024-06-11 14:56   ` Trevor Woerner
2024-06-11 15:03     ` Bruce Ashfield
2024-06-11 15:01   ` Bruce Ashfield
2024-06-11 15:17     ` Bruce Ashfield
2024-06-11 17:18       ` Trevor Woerner [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=20240611171843.GB34413@localhost \
    --to=twoerner@gmail.com \
    --cc=yocto-patches@lists.yoctoproject.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.