s well. Such a straightworward solution has never
occured to me for some reason.
- Anton
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ted (the recipe doesn't get
rebuilt when the file changes, looks like calculate_file_sha256 doesn't
run unless PATH_TO_FILE has changed) and at the same time if I
'cleanall' the recipe and change the file before rebuilding I get a lot
of "metadata is not deterministic"
a server as a part of building the image is already hacky enough, I
know. I'll see what can be done, I might just merge all the three tasks
into one.
Thanks,
Anton
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
at they re-run next time I run `bitbake some-image`. Is it
possible? I've seen some "invalidate_task" functions in bb.siggen and in
bb.runqueue, but I'm not sure about how to use them in a recipe/bbclass.
Thanks,
Anton Gerasimov
--
__
n
'gcc' instead of that monster. Or maybe how to add it to HOSTTOOLS
dynamically based on whatever output of 'gcc --print-multiarch' is.
There is a couple of other recipes unsing swig in meta-openembedded, but
they don't se
to, or just maintain arch-fixes
branch of github.com/an146/openbmc and have someone else to adapt the
fixes to Yocto.
Thanks,
Anton
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
From: Anton Gerasimov
The difference between what we see in pseudo and what happens without
pseudo can be seen by typing:
mkdir setfattr-test
setfattr -n system.posix_acl_default -v 0x0200 setfattr-test
getfattr -n system.posix_acl_default setfattr-test
Under some kernel
/24/2017 04:05 PM, Seebs wrote:
> On Fri, 24 Feb 2017 15:48:15 +0100
> an...@advancedtelematic.com wrote:
>
>> From: Anton Gerasimov
>>
>> The difference between what we see in pseudo and what happens without
>> pseudo can be seen by typing:
>>
>>
From: Anton Gerasimov
The difference between what we see in pseudo and what happens without
pseudo can be seen by typing:
mkdir setfattr-test
setfattr -n system.posix_acl_default -v 0x0200 setfattr-test
getfattr -n system.posix_acl_default setfattr-test
Under some kernel
