On Mon, 11 Jul 2022 17:46 +0200, Gregory Anders wrote:
On Friday, July 08, 2022 08:12 AM MDT, Khem Raj <raj.k...@gmail.com> wrote:
On Fri, Jul 8, 2022 at 2:25 AM Gregory Anders <g...@gpanders.com> wrote:
> On Thu, 07 Jul 2022 16:26 +0100, Richard Purdie wrote:
> >On Thu, 2022-07-07 at 06:39 -0700, Gregory Anders wrote:
> >> Problem solved: the issue was actually that I was using a network
> >> sstate cache,
> >> and the cached output of gcc-cross did not contain gfortran.
> >> Disabling the
> >> sstate cache for gcc-cross causes gfortran to be included in the
> >> sysroot and
> >> now all is working as expected.
> >
> >You shouldn't have to disable the sstate cache but glad you got it
> >working. Which release series is that with?
>
> I am using Xilinx's Petalinux tool, which uses honister under the
> hood. Xilinx maintains an sstate cache for Petalinux, which is quite
> convenient for cutting down build times, but apparently setting the
> FORTRAN variable does not invalidate the sstate cache entry for the
> gcc-cross recipe (which it should, as it affects the build outputs).
Perhaps it’s using locked sstate which might be the reason
I didn't know the sstate could be locked -- how would one unlock it? Could you
point me toward some relevant docs?
After some cursory searching the only thing I've found is the 'locked-sigs.inc'
file. And indeed, Petalinux does ship with a locked-sigs.inc file which
includes a signature for gcc-cross-arm. But adding gcc-cross-arm to
SIGGEN_UNLOCKED_RECIPES doesn't seem to have any effect.
I think I've finally figured this out and just wanted to provide some
closure for posterity's sake.
My initial "solution" of clearing the SSTATE_MIRRORS variable was not
actually correct. It turns out I was not actually even clearing it
correctly, and when I "fixed" it to correctly clear the variable it
caused a build error.
The solution was, in fact, to add gcc-cross-arm to
SIGGEN_UNLOCKED_RECIPES. I simply added this line to my configuration:
SIGGEN_UNLOCKED_RECIPES += "gcc-cross-arm gcc-runtime libgcc"
In my last message, I said that this had no effect. I can only guess
that it appeared that way because some other part of the build was being
cached. After clearing everything in the build directory and
re-building, it seems to work as expected.
Thanks to everyone who offered help.
Greg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57502): https://lists.yoctoproject.org/g/yocto/message/57502
Mute This Topic: https://lists.yoctoproject.org/mt/92216663/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
