https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
Adriaan de Groot changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #23 from mikhail.rok...@gmail.com ---
(In reply to Adriaan de Groot from comment #22)
Thank you.
CPUTYPE?=SandyBridge solved the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #22 from Adriaan de Groot ---
Feel free to send patches.
The Qt configure process is convoluted enough already, and FreeBSD isn't an
officially supported platform anyway. We're not really interested in supporting
even more obsc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #21 from mikhail.rok...@gmail.com ---
(In reply to Adriaan de Groot from comment #20)
What do you think about some intelligence in Qt5 - it can detect not only CPU ,
but really accessible flags/features , so in the case such auto
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #20 from Adriaan de Groot ---
.. and I'm going to repeat that VirtualBox *doesn't support* f16c, even when
the physical host processor does. I see exactly the same issue you do when I
build a Qt on my Skylake box with CPUTYPE=iv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #19 from Tobias C. Berner ---
(In reply to mikhail.rokhin from comment #18)
No, there does not need to be an option for this. -- If adridg and I are
correct, you are simply using packages for a CPU type your CPU does not
suppor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #18 from mikhail.rok...@gmail.com ---
(In reply to Tobias C. Berner from comment #17)
Do you think there must be explicit port option via `make config`, whether to
use CPU arch. advantages or not ?
--
You are receiving this mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #17 from Tobias C. Berner ---
Hi Mikhail
I deleted qt5\* and its dependencies astro/marble on my Intel NUC (i3-6100U
[=skylake]) with CPUTYPE?=ivybridge.
No problem.
mfg Tobias
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #16 from Adriaan de Groot ---
You have built Qt with specific CPU features [1]; you are using that Qt on a
processor that does not have those specific CPU features [2]. Build Qt without
relying on the specific features that your
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #15 from mikhail.rok...@gmail.com ---
(In reply to Adriaan de Groot from comment #13)
Does it mean, that I will never have KDE5 with my Core i7-3610QM or there is a
way to switch off f16c obligatory?
"Try running *any* program t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #14 from Adriaan de Groot ---
Well, I lose that bet since clearly you **can** run kpackagetool5 on the
relevant host without it falling over due to Qt CPU feature detection. So then
the question becomes: what's different during
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #13 from Adriaan de Groot ---
You're hitting exactly one problem: Qt is built, expecting a CPU that supports
F16C (that's CPUID feature flag 29 in ECX). Your CPU does not support it (or it
would be listed in the Features2 line o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #12 from Adriaan de Groot ---
*** Bug 228033 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #11 from Adriaan de Groot ---
*** Bug 228041 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #10 from mikhail.rok...@gmail.com ---
(In reply to Adriaan de Groot from comment #5)
" Basically, you've told your build of Qt to only work on processors with
feature f16c. "
Unfortunately, there's no way to manually set CPU_Fla
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #9 from mikhail.rok...@gmail.com ---
Created attachment 193161
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193161&action=edit
/usr/local/bin/kpackagetool5 --appstream-metainfo . --appstream-metainfo-output
bogus
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #8 from mikhail.rok...@gmail.com ---
(In reply to Adriaan de Groot from comment #5)
Created attachment 193160
AudioPlasma5
AudioPlasma5
f16c detect failure screen-shot
Created attachment 193159 [details]
AstroMarble
f16c de
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #7 from mikhail.rok...@gmail.com ---
Created attachment 193160
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193160&action=edit
AudioPlasma5
AudioPlasma5
f16c detect failure screen-shot
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
--- Comment #6 from Tobias C. Berner ---
*** Bug 228041 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
Adriaan de Groot changed:
What|Removed |Added
CC||adr...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
mikhail.rok...@gmail.com changed:
What|Removed |Added
Summary|audio/plasma5-plasma-pa |audio/plasma5-plasma-pa
21 matches
Mail list logo
