Summary: | app-emulation/qemu-8.2.1 fails to compile: ERROR: -static-pie not available due to missing toolchain support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Virtualization Team <virtualization> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ajak, dilfridge |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Agostino Sarubbo
2024-02-19 16:18:41 UTC
Created attachment 885424 [details]
build.log
build log and emerge --info
ERROR: -static-pie not available due to missing toolchain support That's weird, because the ebuild only adds that flag if the toolchain suports it: # We always want to attempt to build with PIE support as it results # in a more secure binary. But it doesn't work with static or if # the current GCC doesn't have PIE support. if [[ ${static_flag} != "none" ]] && use ${static_flag}; then conf_opts+=( --static --disable-pie ) else tc-enables-pie && conf_opts+=( --enable-pie ) fi While the configure script has: if compile_prog "-Werror -fPIE -DPIE" "$pie_ldflags"; then pie="yes" elif test "$pie" = "yes"; then error_exit "-static-pie not available due to missing toolchain support" else echo "Disabling PIE due to missing toolchain support" pie="no" fi Can you share the associated config.log? really strange because on the same environment I can't reproduce anymore. So I suppose that it was cause by something else. Let's mark as WORKSFORME for now |