[Fx30-CatM 4G R14 Linux build] Some warning during Patch application

IoT Gateways FX30
#1

Dear all,

I am building the Fx30-CatM R14 (Linux part) release swi-fx30-catm_3.0.0 without any modifications.

I have retreaved the linux sources with leaf, running the following command (on Ubuntu 18.04):

    $> leaf setup fx30-catm -p swi-fx30-catm_3.0.0
    $> leaf getsrc legato
    $> leaf getsrc swi-linux
    $> cd swi-linux
    $> make MACH=mdm9x28 PROD=fx30

And I obtain several warning traces indicating a problem in the patches applications.

WARNING: linux-libc-headers-3.18.140-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-if_ether-move-muslc-ethhdr-protection-to-uapi-file.patch
patching file include/uapi/linux/if_ether.h
Hunk #1 succeeded at 141 with fuzz 2 (offset 4 lines).

Now at patch 0001-if_ether-move-muslc-ethhdr-protection-to-uapi-file.patch
WARNING: linux-libc-headers-3.18.140-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0004-Avoid-in6_addr-redefinition.patch
patching file include/uapi/linux/if_bridge.h
Hunk #1 succeeded at 15 with fuzz 2.
patching file include/linux/netfilter.h
Hunk #1 succeeded at 5 (offset 1 line).

Now at patch 0004-Avoid-in6_addr-redefinition.patch
WARNING: system-core-1.0-r1 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch fix-big-endian-build.patch
patching file adb/usb_linux_client.c
Hunk #1 succeeded at 35 with fuzz 2 (offset 1 line).

Now at patch fix-big-endian-build.patch
WARNING: alsa-intf-1.0-r1 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0006-Wait-for-Audio-stream-to-end.patch
patching file libalsa-intf/aplay.c
Hunk #1 succeeded at 604 with fuzz 2 (offset 60 lines).

Now at patch 0006-Wait-for-Audio-stream-to-end.patch

Should I be worried by those warnings?

Regards, Christian.

#2

As far as the yocto image can be built, it should be ok

#3

Hi @lpacyk,

Could you please help take a look at these warnings that Christian has observed?

I don’t recall these during validation of the leaf packages.

Thanks,
Chris

#4

Hello @CGuyot did you follow the steps described in “First time setup” on GitHub - Legato Docs?

I recreated your commands and did not run into any of the errors. Could you possible provide all the logs from start to finish? It would help debug the issue.

#5

Hello @lpacyk,

Yes I did followed the instructions to set-up GitHub.
I have re-started the operations from a clean Ubuntu 18.04 (installed in a VirtualBox VM) to double check.
I obtain the same result. Here is a full trace of the build with information about the configuration attached.

trace-build-1.txt (19.1 KB)

Thanks to let me know if I have made an error somewhere.
Regards, Christian.

#6

@cchenry Can you take a look at the above build logs and see if those warnings are anything of concern?

I took a look at my old build logs and I see these same warnings but the build appears to succeed.