Correct, I can also confirm the backport works in getting it compiled.
Thanks.
On 28-09-2020 18:53, Martin Jansa wrote:
I was able to reproduce this in one of my build setups and confirm
that backporting this commit helps (and haven't found any other issues
while building our images).
I've se
I was able to reproduce this in one of my build setups and confirm that
backporting this commit helps (and haven't found any other issues while
building our images).
I've sent the backport request now.
On Mon, Sep 28, 2020 at 1:46 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
>
On Mon, 2020-09-28 at 10:34 +0200, Robert wrote:
> I tried the latest uninative from the same link, it will remove the
> warning but it doesn't solve the problem.
> If something else is wrong/different I would very much like a
> suggestion where to start looking for this difference.
> Finding somet
I tried the latest uninative from the same link, it will remove the
warning but it doesn't solve the problem.
If something else is wrong/different I would very much like a suggestion
where to start looking for this difference.
Finding something that isn't there is not easy :-\
On 28-09-2020 04:
For uninative you can just use latest dunfell with
https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=0f01fb2286335dd0da0c7be3f56c36a0fced3e42
For dpkg you can just try latest, but I'm not seeing it failing with
glibc-2.32 in ubuntu-20.04, something else might be wrong/different i
Hello list,
The warning in the subject has turned into an error.
I'm building a Yocto project based on poky-dunfell-23.0.2
I get this error:
ERROR: dpkg-native-1.19.7-r0 do_compile: oe_runmake failed
| ../../../dpkg-1.19.7/lib/compat/strsignal.c: In function ‘test_strsignal’:
| ../../../dpkg-1
