[OE-core] appears to be inconsistency re: base-files between oe-core and meta-angstrom

[Martin Jansa]

On Thu, Aug 29, 2013 at 07:37:17AM -0400, Robert P. J. Day wrote:
> On Thu, 29 Aug 2013, Martin Jansa wrote:
> 
> > On Thu, Aug 29, 2013 at 07:00:45AM -0400, Robert P. J. Day wrote:
> > > On Thu, 29 Aug 2013, Martin Jansa wrote:
> > >
> > > > On Thu, Aug 29, 2013 at 06:29:17AM -0400, Robert P. J. Day wrote:
> > > > >
> > > > >   trying to build a "hardware-bringup-image" defined in angstrom layer
> > > > > and running into:
> > > > >
> > > > > ERROR: QA Issue: Fixup Perms: Unable to correct directory link, target already exists: /var/log -> /var/volatile/log
> > > > > ERROR: QA Issue: Fixup Perms: Unable to correct directory link, target already exists: /var/run -> /run
> > > > > ERROR: QA Issue: Fixup Perms: Unable to correct directory link, target already exists: /var/tmp -> /var/volatile/tmp
> > > > >
> > > > > this would *appear* to be because oe-core defines, in
> > > > > base-files_3.0.14.bb:
> > > > >
> > > > > volatiles = "log tmp"
> > > > > ... snip ...
> > > > >         for d in ${volatiles}; do
> > > > >                 ln -sf volatile/$d ${D}${localstatedir}/$d
> > > > >         done
> > > > >         ln -snf ../run ${D}${localstatedir}/run
> > > > >         ln -snf ../run/lock ${D}${localstatedir}/lock
> > > > >
> > > > > which seems to want to create /var/{run,log,tmp} as symlinks, but over
> > > > > in meta-angstrom, we have base-files_3.0.14.bbappend which seems to
> > > > > want to create them as actual directories instead:
> > > >
> > > > Expectations from base-files .bbappend and FILESYSTEM_PERMS_TABLES need
> > > > to be consistent, is it possible that you're using .bbappend from
> > > > angstrom and not FILESYSTEM_PERMS_TABLES set by angstrom config?
> > > >
> > > > conf/distro/include/angstrom-core-tweaks.inc:FILESYSTEM_PERMS_TABLES = "fs-perms-angstrom.txt"
> > >
> > >   ah, i suspect that's what's happening. so what's the correct way to
> > > set up this OE build? i'm trying to build the angstrom
> > > "hardware-bringup-image" using a current oe-core, and my bblayers.conf
> > > file looks like:
> > >
> > > BBLAYERS ?= " \
> > >   /home/rpjday/oe/dist/layers/oe-core/meta \
> > >   /home/rpjday/oe/dist/layers/meta-openembedded/meta-oe \
> > >   /home/rpjday/oe/dist/layers/meta-angstrom \
> > >   /home/rpjday/oe/dist/layers/meta-ti \
> > >   "
> >
> > What's your DISTRO value? distroless oe-core?
> 
>   distroless. i realize i *could* set a value for DISTRO, but it would
> seem that i shouldn't have to in order to avoid a build error.
> 
>   in any event, you clearly see exactly what's causing the error --
> that the base-files bbappend file from meta-angstrom is clashing with
> the base-files recipe from oe-core. if you want me to try anything
> different, i have lots of time today to test. if you want me to select
> a DISTRO, i can certainly do that.

You can add that line from angstrom-core-tweaks into your local.conf,
but it depends on distro maintainer if he wants to support different
DISTROs in distro layer.

In other words, everything in distro layer can usually assume correct
distro configuration, when you're using some recipes from distro layer
with your own distro or distroless config then you're on your own
unsupported combination.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20130829/784fc7c8/attachment-0002.sig>