[poky] sstate info

[McClintock Matthew-B29882]

On Fri, Jan 13, 2012 at 12:19 PM, Gary Thomas <gary at mlbassoc.com> wrote:
> While you're looking at gcc, I noticed something else.  I have
> multiple MACHINE configurations which are all the same basic
> hardware (OMAP3530), the only difference being kernel settings
> and other minor target variations.  As far as things like the
> compiler and common ARM tools, they are identical.
>
> I tried sharing the sstate between two of these and for the
> most part, all was well - only the truly machine dependent
> recipes were rebuilt.  Except for gcc-cross-4.6.2 which seems
> to have a dependency on the MACHINE variable.  This cascaded
> into also building a few other packages (glib, libtool, shadow?
> and udev)  [note: I was building a board with SDK tools which
> may have brought some of these in].  Does this seem reasonable
> to you?  I would hope that these packages, which are placed
> in the architecture (armv7a-vfp-neon-amltd-linux-gnueabi) tree
> should *not* depend on MACHINE.
>
> Thanks for your help with this.

More than likely the MACHINE variable should not be a dependency.
Which variable is depending on MACHINE? You should do some more
investigation.

-M