Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 865101 - dev-qt/qtmultimedia-5.15.5-r1: error: inlining failed in call to ‘always_inline’ ‘__m128i _mm_shuffle_epi8(__m128i, __m128i)’: target specific option mismatch
Summary: dev-qt/qtmultimedia-5.15.5-r1: error: inlining failed in call to ‘always_inli...
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Qt Bug Alias
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-13 14:48 UTC by HougeLangley
Modified: 2022-08-16 12:44 UTC (History)
0 users

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

Attachments
Build Log (qtmultimedia-emerge-build-full-log.log,380.64 KB, text/plain)
2022-08-13 14:48 UTC, HougeLangley 		Details
emerge --info (qtmultimedia-emerge-info.log,8.05 KB, text/plain)
2022-08-13 14:48 UTC, HougeLangley 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description HougeLangley 2022-08-13 14:48:33 UTC 
Created attachment 799491 [details]
Build Log

emerge -avuDN @world

[ebuild   R    ] dev-qt/qtmultimedia-5.15.5-r1:5/5.15::gentoo  USE="alsa gstreamer pulseaudio* qml widgets -debug -gles2-only -openal -test" 0 KiB

emerge -pqv '=dev-qt/qtmultimedia-5.15.5-r1::gentoo'
[ebuild   R   ] dev-qt/qtmultimedia-5.15.5-r1  USE="alsa gstreamer pulseaudio* qml widgets -debug -gles2-only -openal -test"
Comment 1 HougeLangley 2022-08-13 14:48:50 UTC 
Created attachment 799493 [details]
emerge --info
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-08-13 14:54:35 UTC 
I think Qt does some detection of whether your CPU supports various instructions, but then because you're not using -march=foo, you get this.
Comment 3 HougeLangley 2022-08-13 14:56:41 UTC 
(In reply to Sam James from comment #2)
> I think Qt does some detection of whether your CPU supports various
> instructions, but then because you're not using -march=foo, you get this.

ok, maybe I should add march=xxx again?
Comment 4 HougeLangley 2022-08-13 15:00:07 UTC 
Another way, maybe empty tree will solve this problem.
Comment 5 HougeLangley 2022-08-13 17:32:14 UTC 
I have been rollback to march=skylake, the problem solved temporarily.

I will try 'empty tree' without march=skylake. May I keep this issue open when I finish this job ?
Comment 6 HougeLangley 2022-08-16 12:44:03 UTC 
Empty tree will solve problem.