Bug 814830 – dev-qt/qtwebengine cannot install into symlinked /usr

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description piotr5 2021-09-25 17:22:04 UTC]

the build-log shows towards the end:

[...]
/usr/lib64/qt5/bin/qmake -install qinstall /systemd/var/tmp/portage/dev-qt/qtwebengine-5.15.2_p20210824-r1/work/qtwebengine-5.15.2_p20210824_build/src/webenginewidgets/qtwebenginewidgets-config.h /systemd/var/tmp/portage/dev-qt/qtwebengine-5.15.2_p20210824-r1/image/systemd/usr/include/qt5/QtWebEngineWidgets/qtwebenginewidgets-config.h
make[2]: Leaving directory '/systemd/var/tmp/portage/dev-qt/qtwebengine-5.15.2_p20210824-r1/work/qtwebengine-5.15.2_p20210824_build/src/webenginewidgets'
[...]
 * ERROR: dev-qt/qtwebengine-5.15.2_p20210824-r1::gentoo failed (install phase):
 *   dev-qt/qtwebengine-5.15.2_p20210824-r1 failed to build anything. Please report to https://bugs.gentoo.org/

obviously the installer then looks for 
image/usr/include/qt5/QtWebEngineWidgets/qtwebenginewidgets-config.h
finding instead
image/systemd/usr/include/qt5/QtWebEngineWidgets/qtwebenginewidgets-config.h
which it didn't expect. in past I had same bug with rust but it was fixed without me reporting, so I suspect this is an actual bug and not my own misbehaviour...

Reproducible: Always

Steps to Reproduce:
1.externally mount your gentoo drive and move /usr into /systemd/usr 
2.create a symlink from /systemd/usr to /usr and optionally inform portage that this symlink is legit by setting UNINSTALL_IGNORE=/usr in make.conf like I did
3.reboot into the gentoo system altered that way and emerge dev-qt/qtwebengine
4.wait patiently for it to finish ;)
Actual Results:  
above failure

Expected Results:  
proper installation into the /usr symlink and thereby into /systemd/usr or at least check out $UNINSTALL_IGNORE to see if the expected root-directory is registered to be a symlink and translate the expected image/ files accordingly...

sorry if this is a dup, I remember reporting it in the forums.
low severity since it's an edge-case and can be circumvented by chroot before emerge -- except that this is for me the only package with such a problem.

UNINSTALL_IGNORE="/bin /etc /lib32 /lib64 /opt /run /sbin /usr /var"
shows I essentially put the whole gentoo system into /systemd in order to crossbuild and run any number of different linux systems on the same filesystem.

[Comment 1 Sam James 2021-09-25 17:28:01 UTC]

It would help to have the full build.log and emerge --info.

[Comment 2 Jonas Stein 2021-09-26 09:36:44 UTC]

Thank you for the report. We need to have all information at hand before ticket assignment. Please provide
* the complete build.log as attachment and
* paste the emerge info 
as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket

Please reopen this ticket (Status:UNCONFIRMED) afterwards.