> Gesendet: Mittwoch, 27. November 2024 um 10:10 > Von: "Ron Economos" <re@xxxxxxxx> > An: "Frank Wunderlich" <frank-w@xxxxxxxxxxxxxxx>, masahiroy@xxxxxxxxxx > CC: nicolas@xxxxxxxxx, nathan@xxxxxxxxxx, linux-kbuild@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx > Betreff: Re: Aw: Re: build issue in builddeb (dpkg-checkbuilddeps: error: Unmet build dependencies: libssl-dev) in 6.12 > > On 11/26/24 09:12, Frank Wunderlich wrote: > > > Gesendet: Donnerstag, 21. November 2024 um 23:09 > > > Von: "Masahiro Yamada" <masahiroy@xxxxxxxxxx> > > > An: "Frank Wunderlich" <frank-w@xxxxxxxxxxxxxxx> > > > CC: re@xxxxxxxx, nicolas@xxxxxxxxx, nathan@xxxxxxxxxx, linux-kbuild@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx > > > Betreff: Re: build issue in builddeb (dpkg-checkbuilddeps: error: Unmet build dependencies: libssl-dev) in 6.12 > > > > > > On Fri, Nov 22, 2024 at 2:09 AM Frank Wunderlich > > > <frank-w@xxxxxxxxxxxxxxx> wrote: > > > > > > > > Hi, > > > > > > > > i noticed this issue with debian package build-system in final 6.12. > > > > > > > > LOCALVERSION=-main board=bpi-r2 ARCH=arm CROSS_COMPILE=ccache arm-linux-gnueabihf- > > > > make[1]: Entering directory '/media/data_ext/git/kernel/build' > > > > GEN debian > > > > dpkg-buildpackage --build=binary --no-pre-clean --unsigned-changes -R'make -f debian/rules' -j1 -a$(cat debian/arch) > > > > dpkg-buildpackage: info: source package linux-upstream > > > > dpkg-buildpackage: info: source version 6.12.0-00061-g837897c10f69-3 > > > > dpkg-buildpackage: info: source distribution noble > > > > dpkg-buildpackage: info: source changed by frank <frank@frank-u24> > > > > dpkg-buildpackage: info: host architecture armhf > > > > dpkg-source --before-build . > > > > dpkg-checkbuilddeps: error: Unmet build dependencies: libssl-dev > > > > > > This error message means, you need to install "libssl-dev:armhf" > > > > > > > > > > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting > > > > dpkg-buildpackage: warning: (Use -d flag to override.) > > > > make[3]: *** [/media/data_ext/git/kernel/BPI-R2-4.14/scripts/Makefile.package:126: bindeb-pkg] Error 3 > > > > > > > > it was ok in at least rc1 and libssl-dev is installed > > > > > > > > > Presumably, you already installed libssl-dev for your build machine > > > (i.e. "libssl-dev:amd64" if your build machine is x86_64). > > > > > > But, you have not installed "libssl-dev" for the architecture > > > your are building for (i.e, "libssl-dev:armhf") > > > > Hi > > > > thank you for answer, why is this lib required for the arch? it makes my pipeline very complex > > just to add the repos for the arch...seems the lib is not yet used, only checked if installed. > > > > looks like ubuntu 24 seems to have changed the sources.list for apt, so there is no single-line to > > be added > > > > this is the default apt-source in ubuntu 24: > > > > $ cat /etc/apt/sources.list.d/ubuntu.sources > > Types: deb > > URIs: http://de.archive.ubuntu.com/ubuntu/ > > Suites: noble noble-updates noble-backports > > Components: main restricted universe multiverse > > Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg > > > > Types: deb > > URIs: http://security.ubuntu.com/ubuntu/ > > Suites: noble-security > > Components: main restricted universe multiverse > > Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg > > > > if i just add the arches > > > > sudo dpkg --add-architecture armhf > > sudo dpkg --add-architecture arm64 > > > > apt seems to add the repos on update, but i still cannot install the packages > > > > $ LANG=C sudo apt install libssl-dev:armhf > > Reading package lists... Done > > Building dependency tree... Done > > Reading state information... Done > > E: Unable to locate package libssl-dev:armhf > > > > $ LANG=C sudo apt install libssl-dev:arm64 > > Reading package lists... Done > > Building dependency tree... Done > > Reading state information... Done > > E: Unable to locate package libssl-dev:arm64 > > > > if i revert the commit below, my build is successful without installing the lib. > > > > afaik the -dev are source-packages (headers) which should be architecture independ, or am i missing something? > > > > regards Frank > > > > > > > > > > basicly i use this command after setting crosscompiler > > > > > > > > LOCALVERSION="${gitbranch}" board="$board" KDEB_COMPRESS=gzip make bindeb-pkg > > > > > > > > if i Revert "kbuild: deb-pkg: add pkg.linux-upstream.nokernelheaders build profile" > > > > > > > > i can compile again..any idea why this happens? my build-system is ubuntu 24.4 and github actions with ubuntu-latest. > > > > > > > > https://github.com/frank-w/BPI-Router-Linux/actions/runs/11955322294/job/33327423877 > > > > > > > > regards Frank</frank@frank-u24> > > > > > > > > > > > > -- > > > Best Regards > > > Masahiro Yamada > > Here's what worked for me in /etc/apt/sources.list.d/ubuntu.sources for > 24.04. > > Types: deb > URIs: http://ports.ubuntu.com/ubuntu-ports > Suites: noble noble-updates noble-backports > Components: main universe restricted multiverse > Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg > Architectures: riscv64 > thx for ubuntu 24 i have it done similar (took the whole day to get both systems to the point apt-sources to be added the right way), had to modify the ubuntu.sources to add the arch for host system (amd64) and add additional file with ports.ubuntu.com for the crosscompile-target (armhf/arm64) https://github.com/frank-w/BPI-Router-Linux/actions/runs/12047237222/job/33589357798#step:6:1 tried most time to get current ubuntu-latest for github actions running which is still ubuntu-22.04, but ran into installing issues where libssl3 cannot be installed for the desired arch...if i add it manually it depends on libc for the arch and so on... example for ubuntu-latest / ubuntu-22.04 https://github.com/frank-w/BPI-Router-Linux/actions/runs/12038757178/job/33565113600 https://github.com/frank-w/BPI-Router-Linux/actions/runs/12038757178/workflow#L56 > The library is used here: > > https://github.com/torvalds/linux/blob/master/scripts/sign-file.c#L25 > > That file is now cross-compiled. but why needs signing-file to be crosscompiled? the target files (kernel and maybe the deb-file) have to be crosscompiled, but imho not tools for signing them. After building kernel for target-arch and creating deb isn't it possible to sign it using a amd64 (host arch) openssl binary? the openssl-binary does not land on target-platform...only used as part of build-chain, or am i wrong? btw. not sure why my webmailer creates html-tags in plaintext-mails...have reported it to the vendor, but not got any response yet, so sorry for that (have replaced quote-chars manually, hope they stay as single chars and not reconverted to entities). regards Frank </frank-w@xxxxxxxxxxxxxxx></frank-w@xxxxxxxxxxxxxxx></masahiroy@xxxxxxxxxx></frank-w@xxxxxxxxxxxxxxx></re@xxxxxxxx>
