This was the commit that introduced the DIRFILES variable:
https://git.yoctoproject.org/poky/commit/?id=2f42ef8d8fb1febf28252b98884cebabc931f720

Given that it's undocumented, untested, rpm-specific, and currently
broken, and looks like a workaround for security label conflicts
elsewhere I'm inclined to remove the code paths that use it
altogether.

Alex

On Sun, 25 Feb 2024 at 19:34, Jeremy Puhlman via
lists.openembedded.org <[email protected]>
wrote:
>
>
>
> On 2/25/2024 10:32 AM, Jeremy Puhlman wrote:
> >
> >
> > On 2/25/2024 9:22 AM, Jeremy Puhlman wrote:
> >>
> >>
> >> On 2/24/2024 2:13 PM, Richard Purdie wrote:
> >>> On Fri, 2024-02-23 at 12:33 -0800, Jeremy Puhlman via
> >>> lists.openembedded.org wrote:
> >>>> It says usr//usr in the comment, but when I ran on a clean build it
> >>>> started complaining about opt//opt as well. Its not really clear why
> >>>> it is looking for those directories, and I am sure this is not likely
> >>>> the correct solution, but I wanted to get it out here so someone who
> >>>> has kicked this area of code might know what may be happening.
> >>> Unfortunately there are layers of different pieces which could be the
> >>> issue, such as pseudo in combination with the host distro libraries and
> >>> uninative.
> >>>
> >>> Can you create a test case which reproduces the issue?
> >> Yeah, I was going to try to get to it, but time got away from me.
> >> Hopefully I should
> >> be able to get some time later today.
> >
> > Trying to reduce the recipe to bare bones, I narrowed it down the the
> > DIRFILES setting.
> > Deep in the top level class configuration for the layer, it sets
> > DIRFILES="1", which looks
> > wrong given the code. OTOH, nothing else in any of the layers we are
> > using sets the value
> > to anything, so what ever recent changes that were made there are
> > untested by anything.
> >
> > Turning that off should resolve my issue, but it looks like that code
> > path may be vestigial at
> > this point.
> >
> As an aside, adding:
> DIRFILES = "${bindir}"
> To something like the bash recipe, reproduces the behavior.
>
> >>
> >>>   Does it always
> >>> happen with this recipe?
> >> Yes. Originally it was happening in our distro setup, minimizing it
> >> to just poky and the
> >> meta-oe/meta-python, it happens with the recipe with the default
> >> distro as well.
> >>
> >>>   Does it happen on different host distros?
> >> I have not tried that, so far it was just rocky 8.
> >>
> >>>   Are
> >>> you using uninative?
> >> Yes. It happens with the default poky distro, too.
> >>
> >>> What about buildtools-tarball?
> >> We always use buildtools-extended-tarball, to isolate as much as
> >> possible from the host.
> >>
> >>>
> >>> Cheers,
> >>>
> >>> Richard
> >>
> >
>
> --
> Jeremy Puhlman
> [email protected]
>
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196200): 
https://lists.openembedded.org/g/openembedded-core/message/196200
Mute This Topic: https://lists.openembedded.org/mt/104536226/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to