On Wed, 2023-06-28 at 00:55 -0700, [email protected] wrote: > Hi, > A bug is triggered when using docker + Ubuntu 20.04.3 LTS. The > bug message is : > > File: 'xxx/build/poky/meta/classes/kernel-module-split.bbclass', > lineno: 68, function: extract_modinfo > 0064: raise msg > 0065: cmd = "%sobjcopy -j .modinfo -O binary %s %s" % > (d.getVar("HOST_PREFIX") or "", tmpkofile, tmpfile) > 0066: else: > 0067: cmd = "%sobjcopy -j .modinfo -O binary %s %s" % > (d.getVar("HOST_PREFIX") or "", file, tmpfile) > *** 0068: subprocess.check_call(cmd, shell=True) > Exception: subprocess.CalledProcessError: Command 'aarch64-poky- > linux-objcopy -j .modinfo -O binary ../keymaps/rc-alink-dtu-m.ko > ../tmpwhs5uwlt' returned non-zero exit status 1. > > The "rc-alink-dtu-m.ko" file is damaged, and can't analysis by > file command : > $ file -b rc-alink-dtu-m.ko > data > and the damaged is caused by > build/poky/meta/classes/package.bbclass perform_packagecopy() > cmd = 'tar --exclude=./sysroot-only -cf - -C %s -p -S . | tar > -xf - -C %s' % (dest, dvar) > > remove the "-S " can fix the bug. > notes: this bug only appears in Ubuntu 20.04.3 LTS, and Ubuntu > 20.04.6 LTS do not have the issue.
Do you have the tar versions for the two distro versions? Was this a bug that was fixed in tar? I'm not sure we can easily work around this, it may be better to error if a build is attempted with a known broken tar version? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60467): https://lists.yoctoproject.org/g/yocto/message/60467 Mute This Topic: https://lists.yoctoproject.org/mt/99828392/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
