Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 932731 - sys-devel/gcc-14: lost keywords on loong (kde-frameworks/kcoreaddons-5.116.0: cmake: /usr/lib/gcc/loongarch64-unknown-linux-gnu/13/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by cmake))
Summary: sys-devel/gcc-14: lost keywords on loong (kde-frameworks/kcoreaddons-5.116.0:...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: Loong Linux
: Normal normal
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on: 932732
Blocks:
  Show dependency tree
 
Reported: 2024-05-25 13:01 UTC by HougeLangley
Modified: 2024-05-25 14:41 UTC (History)
2 users (show)

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


Attachments
emerge --info (loongarch-emerge-info.log,7.60 KB, text/x-log)
2024-05-25 13:01 UTC, HougeLangley
Details

Note You need to log in before you can comment on or make changes to this bug.
Description HougeLangley 2024-05-25 13:01:36 UTC
Created attachment 894354 [details]
emerge --info

Full log:


[32m * [39;49;00mPackage:    kde-frameworks/kcoreaddons-5.116.0:5/5.116
[32m * [39;49;00mRepository: gentoo
[32m * [39;49;00mMaintainer: kde@gentoo.org
[32m * [39;49;00mUpstream:   https://bugs.kde.org/
[32m * [39;49;00mUSE:        dbus elibc_glibc kernel_linux loong
[32m * [39;49;00mFEATURES:   preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking kcoreaddons-5.116.0.tar.xz to /var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work
>>> Source unpacked in /var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work
>>> Preparing source in /var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0 ...
 [32m*[0m Source directory (CMAKE_USE_DIR): "/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0"
 [32m*[0m Build directory  (BUILD_DIR):     "/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0_build"
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0 ...
 [32m*[0m Source directory (CMAKE_USE_DIR): "/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0"
 [32m*[0m Build directory  (BUILD_DIR):     "/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0_build"
cmake -C /var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0_build/gentoo_common_config.cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/usr -DBUILD_TESTING=OFF -DBUILD_QCH=no -DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DKDE_INSTALL_DOCBUNDLEDIR=/usr/share/help -D_KDE4_DEFAULT_HOME_POSTFIX=4 -DCMAKE_DISABLE_FIND_PACKAGE_FAM=ON -DCMAKE_DISABLE_FIND_PACKAGE_Qt5DBus=OFF -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0_build/gentoo_toolchain.cmake /var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0
cmake: /usr/lib/gcc/loongarch64-unknown-linux-gnu/13/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by cmake)
 [31;01m*[0m ERROR: kde-frameworks/kcoreaddons-5.116.0::gentoo failed (configure phase):
 [31;01m*[0m   cmake failed
 [31;01m*[0m 
 [31;01m*[0m Call stack:
 [31;01m*[0m     ebuild.sh, line  136:  Called src_configure
 [31;01m*[0m   environment, line 2422:  Called ecm_src_configure
 [31;01m*[0m   environment, line 1410:  Called cmake_src_configure
 [31;01m*[0m   environment, line 1050:  Called die
 [31;01m*[0m The specific snippet of code:
 [31;01m*[0m       "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
 [31;01m*[0m 
 [31;01m*[0m If you need support, post the output of `emerge --info '=kde-frameworks/kcoreaddons-5.116.0::gentoo'`,
 [31;01m*[0m the complete build log and the output of `emerge -pqv '=kde-frameworks/kcoreaddons-5.116.0::gentoo'`.
 [31;01m*[0m The complete build log is located at '/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/temp/build.log'.
 [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/temp/environment'.
 [31;01m*[0m Working directory: '/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0_build'
 [31;01m*[0m S: '/var/tmp/portage/kde-frameworks/kcoreaddons-5.116.0/work/kcoreaddons-5.116.0'
Comment 1 HougeLangley 2024-05-25 13:28:25 UTC
I have just discovered that the system has been updated and reinstalled with GCC version 13.

My guess is that the current situation arises from a few days ago when I ran emerge -e @world, followed by a complete run again with -e world to assess the state now.
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-05-25 14:03:01 UTC
commit 069fa4b6dcf92b64705a2d2201946efd734b4ee4
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Thu May 23 21:18:27 2024 +0200

    sys-devel/gcc: unkeyword 14.1.1_p20240518 for ~loong, ~m68k

    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

The commit mentions build issues but I don't know what they are.
Comment 3 HougeLangley 2024-05-25 14:11:25 UTC
(In reply to Sam James from comment #2)
> commit 069fa4b6dcf92b64705a2d2201946efd734b4ee4
> Author: Andreas K. Hüttel <dilfridge@gentoo.org>
> Date:   Thu May 23 21:18:27 2024 +0200
> 
>     sys-devel/gcc: unkeyword 14.1.1_p20240518 for ~loong, ~m68k
> 
>     Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
> 
> The commit mentions build issues but I don't know what they are.

Thank you for your reply. I believe it may be due to my previous emergence of @world in the gcc-14 environment that caused this issue. I have since rolled back my system to gcc-13, and I am now re-emerging with @world.
Comment 4 Larry the Git Cow gentoo-dev 2024-05-25 14:29:57 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=22a8daea3068c6edb5f7d2cbb475bc369e190f9f

commit 22a8daea3068c6edb5f7d2cbb475bc369e190f9f
Author:     Andreas K. Hüttel <dilfridge@gentoo.org>
AuthorDate: 2024-05-25 14:29:09 +0000
Commit:     Andreas K. Hüttel <dilfridge@gentoo.org>
CommitDate: 2024-05-25 14:29:45 +0000

    sys-devel/gcc: keyword 14.1.1_p20240518 for ~loong
    
    Bug: https://bugs.gentoo.org/932732
    Closes: https://bugs.gentoo.org/932731
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 sys-devel/gcc/gcc-14.1.1_p20240518.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Comment 5 Andreas K. Hüttel archtester gentoo-dev 2024-05-25 14:32:17 UTC
Apologies. I had some suspicions and verbal reports about SIGILL, and gcc was failing to build on the stage builders (under qemu).

On inspection, this looks like a qemu problem, so restored the keyword now.
Comment 6 HougeLangley 2024-05-25 14:41:03 UTC
(In reply to Andreas K. Hüttel from comment #5)
> Apologies. I had some suspicions and verbal reports about SIGILL, and gcc
> was failing to build on the stage builders (under qemu).
> 
> On inspection, this looks like a qemu problem, so restored the keyword now.

Thanks