Bug 949126 – dev-qt/qtbase-6.9.9999 - unrecognized line '../lib64/qt6/bin/qmake bin/qmake6' in '' , Called _qt6-build_create_user_facing_links

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description jospezial 2025-01-31 18:18:00 UTC]

Created attachment 918010 [details]
emerge --info

https://codereview.qt-project.org/c/qt/qtbase/+/616345
"Make user tools symlinks relative"

I think qt6-build.eclass needs to be adapted maybe to this and all the other related upstream changes that have landed in dev, picked to 6.8 6.9 and will land in next releases.

-- Installing: /var/tmp/portage/dev-qt/qtbase-6.9.9999/image/usr/lib64/libQt6DeviceDiscoverySupport.prl
-- Installing: /var/tmp/portage/dev-qt/qtbase-6.9.9999/image/usr/lib64/libQt6Sql.prl
-- Starting SBOM generation in build dir: /var/tmp/portage/dev-qt/qtbase-6.9.9999/work/qtbase-6.9.9999_build/qt_sbom/staging-qtbase.spdx.in
-- Finalizing SBOM generation in install dir: /var/tmp/portage/dev-qt/qtbase-6.9.9999/image/usr/lib64/qt6/sbom/qtbase-6.9.0.spdx
-- Installing: /var/tmp/portage/dev-qt/qtbase-6.9.9999/image/usr/lib64/cmake/Qt6CoreTools/Qt6CoreToolsAdditionalTargetInfo.cmake
-- Installing: /var/tmp/portage/dev-qt/qtbase-6.9.9999/image/usr/lib64/cmake/Qt6WidgetsTools/Qt6WidgetsToolsAdditionalTargetInfo.cmake
-- Installing: /var/tmp/portage/dev-qt/qtbase-6.9.9999/image/usr/lib64/cmake/Qt6DBusTools/Qt6DBusToolsAdditionalTargetInfo.cmake
-- Installing: /var/tmp/portage/dev-qt/qtbase-6.9.9999/image/usr/lib64/cmake/Qt6GuiTools/Qt6GuiToolsAdditionalTargetInfo.cmake
 * ERROR: dev-qt/qtbase-6.9.9999::gentoo failed (install phase):
 *   unrecognized line '../lib64/qt6/bin/qmake bin/qmake6' in ''
 * 
 * Call stack:
 *     ebuild.sh, line  136:  Called src_install
 *   environment, line 2561:  Called qt6-build_src_install
 *   environment, line 2428:  Called _qt6-build_create_user_facing_links
 *   environment, line  612:  Called die
 * The specific snippet of code:
 *                   die "unrecognized line '${link}' in '${links}'";

I have enabled custom-cflags for qt but that seems unrelated.

[ebuild   R   *]        dev-qt/qtbase-6.9.9999:6/6.9.9999::gentoo  USE="X concurrent cups custom-cflags%* dbus gtk gui icu libinput libproxy network nls odbc opengl sql sqlite ssl syslog udev vulkan wayland widgets xml (zstd) -accessibility -brotli -eglfs -evdev -gles2-only -gssapi -journald -mysql -oci8 -postgres -renderdoc -sctp -test -tslib" 0 KiB

[Comment 1 jospezial 2025-01-31 18:20:19 UTC]

Created attachment 918011 [details]
build.log gzipped

[Comment 2 Ionen Wolkens 2025-01-31 23:31:19 UTC]

Thanks, when I last used 6.8.9999 I was specifically using EGIT_BRANCH=6.8.2 in preparation for release didn't notice this.

[Comment 3 Ionen Wolkens 2025-01-31 23:54:16 UTC]

This actually works out better for us, we were doing bit of a hack to support potential paths with spaces, but a relative path shouldn't have any and can simplify this now.

$ cat user_facing_tool_links.txt
../lib64/qt6/bin/qmake bin/qmake6

[Comment 4 Larry the Git Cow 2025-02-01 00:40:14 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7827b36dd37936a36d455fbd910d620ecbf11381

commit 7827b36dd37936a36d455fbd910d620ecbf11381
Author:     Ionen Wolkens <[e-mail]>
AuthorDate: 2025-02-01 00:04:57 +0000
Commit:     Ionen Wolkens <[e-mail]>
CommitDate: 2025-02-01 00:34:21 +0000

    qt6-build.eclass: update for user_facing_tool_links.txt changes
    
    Still keep a bash loop given want to keep the sanity check and it
    spares us from doing `cd "${D}${QT6_PREFIX}"` for a `xargs ln` to
    work, but it let us simplify a little bit.
    
    Keeping old version in its own block so it's easy to drop later.
    
    Also drop the empty ${links} variable from the sanity check, dates
    back to old unused code.
    
    Closes: https://bugs.gentoo.org/949126
    Signed-off-by: Ionen Wolkens <[e-mail]>

 eclass/qt6-build.eclass | 29 ++++++++++++++++++++++-------
 1 file changed, 22 insertions(+), 7 deletions(-)

[Comment 5 Ionen Wolkens 2025-02-01 00:40:47 UTC]

On a side-note, haven't updated/tested 6.9.9999 since it was branched, so it could have more issues (in fact I tested with 6.8.9999 right now given I had ccache for it ;p)

Feel free to report if anything else that prevent using it, but otherwise I'll look at changes + do test builds when we're close to 6.9.0-rc in preparation like usual (which planning to add to the tree unkeyworded).