Bug 228033

Summary: astro/marble org.kde.plasma.worldclock.appdata.xml absent f16c detect failure
Product: Ports & Packages Reporter: mikhail.rokhin
Component: Individual Port(s)Assignee: freebsd-kde (group) <kde>
Status: Closed DUPLICATE    
Severity: Affects Many People CC: adridg, tcberner
Priority: --- Flags: bugzilla: maintainer-feedback? (kde)
Version: Latest   
Hardware: Any   
OS: Any   
See Also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227977
Attachments:
Description Flags
CPU_Features
none
AstroMarble none

Description mikhail.rokhin 2018-05-06 23:50:17 UTC 
Found  KF5Plasma ...
couldn't generate metainfo for org.kde.plasma.worldclock: Incompatible processor - no f16c support

So it fails at Registering stage claiming there's no such xml-file.

But it's Core i7-3610QM having such feature and in other KDE ports it is detected properly.

ports tree , kernel & world latest.

Thank you for development.
Comment 1 Tobias C. Berner freebsd_committer freebsd_triage 2018-05-07 05:15:02 UTC 
Hi there

To me this looks like you "tuned" your make.conf badly.


mfg Tobias
Comment 2 mikhail.rokhin 2018-05-07 11:42:54 UTC 
(In reply to Tobias C. Berner from comment #1)
There's nothing special in make.conf , but

CPUTYPE?=ivybridge

Again, some other ports, using CMake, detect this f16c feature properly. 
I will try to catch them - they are in deps of KDE4/5
Comment 3 mikhail.rokhin 2018-05-07 12:17:34 UTC 
Created attachment 193143 [details]
CPU_Features
Comment 4 mikhail.rokhin 2018-05-07 15:45:37 UTC 
(In reply to Tobias C. Berner from comment #1)
The same results with empty make.conf

The problem is within CMake detection algorithm.
Comment 5 mikhail.rokhin 2018-05-07 18:34:40 UTC 
Created attachment 193159 [details]
AstroMarble

f16c detect failure screen-shot
Comment 6 Adriaan de Groot freebsd_committer freebsd_triage 2018-05-07 20:49:58 UTC 
CMake has nothing to do with this, except that during configuration with CMake, the individual CMakeLists.txt is calling (a macro that calls) kpackagetool, which is a Qt-using-application. Qt produces this error message.

*** This bug has been marked as a duplicate of bug 227977 ***