Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 695542 - dev-libs/libgcrypt-1.8.5 fails to build in other --root
Summary: dev-libs/libgcrypt-1.8.5 fails to build in other --root
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Mikle Kolyada
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-24 12:48 UTC by Phillip Susi
Modified: 2021-09-18 04:10 UTC (History)
4 users (show)

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


Attachments
build.log (build.log,11.73 KB, text/x-log)
2019-09-24 12:48 UTC, Phillip Susi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Phillip Susi 2019-09-24 12:48:29 UTC
Created attachment 590870 [details]
build.log

I'm trying to run emerge --root=/path/to/empty/directory @system, and libgcrypt 1.8.3 is failing to build, because it says it can not find libgpg-error.  Over on the forums, Hu said "For what it is worth, the problem seems to be that the ebuild set GPG_ERROR_CONFIG="${EROOT}/usr/bin/${CHOST}-gpg-error-config", and configure accepted that on faith. Your problem is that either (1) the ebuild shouldn't be using that path or (2) Portage should have installed that tool into the root first"

Installing libgpg-error to the new root did not resolve the issue.
Comment 1 Phillip Susi 2019-09-24 17:04:01 UTC
After installing libgpg-error to the chroot, it is under not x86_64-pc-linux-gnu-gpg-error-config but simply gpg-error-config, so that looks like why it still doesn't work.  I think the problem is that the ebuild shouldn't be throwing $CHOST in there.
Comment 2 Arfrever Frehtes Taifersar Arahesis 2019-09-25 00:31:02 UTC
${ROOT} and ${EROOT} should not be used in src_* phases.

Suggested change:
- GPG_ERROR_CONFIG="${EROOT}/usr/bin/${CHOST}-gpg-error-config"
+ GPG_ERROR_CONFIG="${ESYSROOT}/usr/bin/${CHOST}-gpg-error-config"
Comment 3 Phillip Susi 2019-09-25 12:41:23 UTC
That alone won't fix it since there is no $CHOST- prefix on gpg-error-config.  I'm not sure why it is adding that prefix when built with --root=, and doesn't seem to otherwise.