poky.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Noufal" <noufal.poyiloor@gmail.com>
To: poky@lists.yoctoproject.org
Subject: Error while creating ipk (do_package_write_ipk) packages for Linux kernel source #bitbake #poky #yocto
Date: Sat, 10 Dec 2022 08:53:11 -0800	[thread overview]
Message-ID: <nUVr.1670691191955937069.aIh7@lists.yoctoproject.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]

Hi Team,

As part of my project, I am using yocto dunfell branch as my build environment.

I am experiencing an issue while creating IPK packages for Linux source as given below.

```

PATH=$<paths> opkg-build -Z xz -a "--memlimit=50% --threads=128" kernel-module-atmel-5.4.198

<dir>/linux/5.4.198/deploy-ipks/generic32' returned non-zero exit status 127.

16:54:05  Subprocess output:<tmp-dir>/linux//5.4.198+git2b99183f1c3663c9c7344a6b3b17f52c81b6746c-r0/recipe-sysroot-native/usr/bin/opkg-build: line 313: <dir>/linux /5.4.198/recipe-sysroot-native/usr/bin/gzip: No such file or directory

```

*Line 313 of opkg-build is as follows:*

```

( cd $pkg_dir/$CONTROL && tar $ogargs $tsortargs --no-recursion --mtime=@$build_date -c $tarformat -T $tmp_dir/control_list | pigz $zipargs > $tmp_dir/control.tar.gz )

```

My build environment is ubuntu 20.04 docker container. Also am building multiple images within the same build directory in sequence and shared sstate. With this, one of the build is failing for do_package_write_ipk.

The error is randomly observed and gzip is not found under the directory linux/ recipe-sysroot-native/usr/bin/gzip even if the build is success or failed. I have verified only the single image which was failing during sequence build, and it was success with no gzip binary under the directory linux/ recipe-sysroot-native/usr/bin/gzip. But HOSTTOOLS_DIR has all these packages available.

Is this because during sequence build with shared sstate, PATH from where the gzip binary is slected inside opkg-build script is getting messed up sometimes or something else?

Also How can I verify the gzip tool path selected by the opkg-build script?

Can any one help me to resolve this issue?

Thanks,

Noufal P

[-- Attachment #2: Type: text/html, Size: 6541 bytes --]

                 reply	other threads:[~2022-12-10 16:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nUVr.1670691191955937069.aIh7@lists.yoctoproject.org \
    --to=noufal.poyiloor@gmail.com \
    --cc=poky@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).