Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 759127 - dev-libs/nss-3.59: line 49: shlibsign: command not found
Summary: dev-libs/nss-3.59:
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Mozilla Gentoo Team
Depends on:
Blocks: crossdev-bugs
  Show dependency tree
Reported: 2020-12-08 21:47 UTC by Aisha Tammy
Modified: 2023-06-29 21:33 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

emerge --info.txt (emerge --info.txt,5.87 KB, text/plain)
2020-12-08 21:47 UTC, Aisha Tammy
build.log (build.log.tgz,21.00 KB, application/x-compressed-tar)
2020-12-08 21:48 UTC, Aisha Tammy

Note You need to log in before you can comment on or make changes to this bug.
Description Aisha Tammy 2020-12-08 21:47:55 UTC
Created attachment 677302 [details]
emerge --info.txt

nss fails on crossdev host compiling for amd64
Comment 1 Aisha Tammy 2020-12-08 21:48:10 UTC
Created attachment 677305 [details]
Comment 2 Thomas Deutschmann (RETIRED) gentoo-dev 2020-12-08 23:23:43 UTC
Wondering if is not firing for you...
Comment 3 Aisha Tammy 2020-12-09 00:22:51 UTC
CBUILD didn't have nss at all so... not sure if that sed would've helped.
Comment 4 Aisha Tammy 2020-12-09 01:32:53 UTC
sorry I forgot to mention this, but installing nss on CBUILD fixes the problem.

There definitely needs to be a way to tell portage that some packages want themselves to be present in BDEPEND on CBUILD.
Comment 5 Raul Rangel 2023-06-29 15:44:04 UTC
Hrmm, I just ran into this as well.
shlibsign -v -i /build/arm64-generic/tmp/portage/dev-libs/nss-3.68.2-r3/work/nss-3.68.2/nss-.arm64/cmd/shlibsign/../../dist/Linux6.1_aarch64_clang_glibc_PTH_64_OPT.OBJ/lib/
/build/arm64-generic/tmp/portage/dev-libs/nss-3.68.2-r3/work/nss-3.68.2/nss-.arm64/cmd/shlibsign/./ line 37: shlibsign: command not found

I would add `BDEPEND+=" dev-libs/nss"` to the ebuild, but this dependency only applies when cross compiling... I wonder what the correct way to handle this is. Should we add a new `USE` flag `cross-compile` that portage will set when the CBUILD != CHOST? Then we could do `BDEPEND+=" cross-compile? ( dev-libs/nss )"`.
Comment 6 Raul Rangel 2023-06-29 21:33:45 UTC
If anyone was curious, this is the hack I put in place in our (chromiumos) build system: