Bug 228033 - astro/marble org.kde.plasma.worldclock.appdata.xml absent f16c detect failure
Summary: astro/marble org.kde.plasma.worldclock.appdata.xml absent f16c detect failure
Status: Closed DUPLICATE of bug 227977
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-kde (group)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-06 23:50 UTC by mikhail.rokhin
Modified: 2018-05-07 20:49 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (kde)

Attachments
CPU_Features (109.44 KB, image/jpeg)
2018-05-07 12:17 UTC, mikhail.rokhin 		no flags Details
AstroMarble (71.00 KB, image/jpeg)
2018-05-07 18:34 UTC, mikhail.rokhin 		no flags 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 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 ***