The updated spec is available in the kde4-solaris repo.
Friday, December 23, 2011
Calligra 2.4 beta 5 on Solaris
Calligra just became buildable again. There's just a handful of patches needed when building with Solaris Studio 12.3 and most of them are already applied in upstream, thanks to helpful Calligra developers.
The updated spec is available in the kde4-solaris repo.
The updated spec is available in the kde4-solaris repo.
Tuesday, November 1, 2011
Qt autotests - SFE vs KDE4
Qt comes with an extensive number of self tests and it's interesting to run them from time to time. In the FOSSqt.spec file of the kde4-solaris project, they can be turned on by defining run_autotests to 1, similarly in the SFEqt-gpp.spec of our SFE brethren.
A great number of them is failing on Solaris for various reasons - be it compiler issues, code bugs, or anything else, there's simply too many failures to demotivate anyone from trying to fix it.
So I thought it might be more interesting to compare the results from our build and SFE's - that way the difference would be more or less based on compiler differences (SFE uses gcc) and not anything else.
So here comes the comparison of the results for Qt 4.7.4:
Our Qt ran 491 tests, SFE's 489. There were 77 differences.
17 of the differences were irrelevant (difference in pointer address, test duration, slightly different messages, etc.). This includes tst_bic, tst_gestures, tst_maketestselftest, tst_modeltest, tst_q_func_info, tst_qcontiguouscache, tst_qdbusperformance, tst_qelapsedtimer, tst_qgraphicsitem, tst_qmainwindow, tst_qmenu, tst_qmutex, tst_qobjectperformance, tst_qscriptjstestsuite, tst_qscriptv8testsuite,
36 cases where we fail and SFE passes: tst_collections,
tst_compiler (mere prejudice, we should try to override the stupid #if defined(Q_CC_SUN) there),
tst_mediaobject (something's wrong with our phonon),
tst_q3sqlcursor, tst_q3sqlselectcursor, tst_qitemmodel, tst_qsql, tst_qsqldatabase, tst_qsqldriver, tst_qsqlquery, tst_qsqlquerymodel, tst_qsqlrelationaltablemodel, tst_qsqltablemodel, tst_qsqlthread, (hm, sqlite not set up properly),
tst_qaccessibility (a big fail here),
tst_qapplication (may be caused just by some difference in how the tests were run),
tst_qdatetime, tst_qdatetimeedit (caused by different environment when running the test - need to run it in the CET timezone),
tst_qdom, tst_qtextcodec, tst_qxmlsimplereader (mmm, asian encodings!),
tst_qgraphicsscene (this one is weird),
tst_qicoimageformat, tst_qicon, tst_qimage, tst_qimagereader, tst_qimagewriter, tst_qpixmap (deserves investigation, image format support),
tst_qmake (weird, need to have a look - perhaps bad mkspec used?)
tst_qmovie
tst_qnetworkconfiguration, tst_qnetworkconfigurationmanager, tst_qnetworksession (!)
tst_qwebpage
tst_uic, tst_uic3 (likely QTBUG-21523)
2 tests that SFE builds but we don't: tst_qdbusmarshall (QTBUG-22106), tst_qtconcurrentmap (QTBUG-12987)
4 tests that we build but SFE doesn't: tst_guiapplauncher, tst_qglthreads, tst_qwidget_window, tst_qwidget
20 tests where SFE fails while we pass:
tst_qabstractslider
tst_qcolumnview
tst_qcompleter
tst_qdialog
tst_qeventloop
tst_qfilesystemmodel
tst_qgl
tst_qglbuffer
tst_qgraphicsproxywidget
tst_qgraphicstransform
tst_qgraphicsview (not really a pass, but a few more tests are run in our build)
tst_qmdiarea
tst_qmessagebox (X Error: BadWindow)
tst_qprocess
tst_qreadwritelock
tst_qscriptengine
tst_qstring (no wide character support in the g++ build? Strange ... )
tst_qthread
tst_qtimeline
tst_xmlpatternsdiagnosticsts
It looks like the tests that included some performance measurements (tst_qcontiguouscache, tst_qdbusperformance, tst_qmutex, tst_qprocess) show better numbers for our bits, but I'd be far from interpreting it in that way. Both tests were run in a VirtualBox environment and the load on the host was quite different on the two occasions.
Webrev of the results (to save space only the udiff diffs were preserved)
The results bzipped
The tests source for reference
A great number of them is failing on Solaris for various reasons - be it compiler issues, code bugs, or anything else, there's simply too many failures to demotivate anyone from trying to fix it.
So I thought it might be more interesting to compare the results from our build and SFE's - that way the difference would be more or less based on compiler differences (SFE uses gcc) and not anything else.
So here comes the comparison of the results for Qt 4.7.4:
Our Qt ran 491 tests, SFE's 489. There were 77 differences.
17 of the differences were irrelevant (difference in pointer address, test duration, slightly different messages, etc.). This includes tst_bic, tst_gestures, tst_maketestselftest, tst_modeltest, tst_q_func_info, tst_qcontiguouscache, tst_qdbusperformance, tst_qelapsedtimer, tst_qgraphicsitem, tst_qmainwindow, tst_qmenu, tst_qmutex, tst_qobjectperformance, tst_qscriptjstestsuite, tst_qscriptv8testsuite,
36 cases where we fail and SFE passes: tst_collections,
tst_compiler (mere prejudice, we should try to override the stupid #if defined(Q_CC_SUN) there),
tst_mediaobject (something's wrong with our phonon),
tst_q3sqlcursor, tst_q3sqlselectcursor, tst_qitemmodel, tst_qsql, tst_qsqldatabase, tst_qsqldriver, tst_qsqlquery, tst_qsqlquerymodel, tst_qsqlrelationaltablemodel, tst_qsqltablemodel, tst_qsqlthread, (hm, sqlite not set up properly),
tst_qaccessibility (a big fail here),
tst_qapplication (may be caused just by some difference in how the tests were run),
tst_qdatetime, tst_qdatetimeedit (caused by different environment when running the test - need to run it in the CET timezone),
tst_qdom, tst_qtextcodec, tst_qxmlsimplereader (mmm, asian encodings!),
tst_qgraphicsscene (this one is weird),
tst_qicoimageformat, tst_qicon, tst_qimage, tst_qimagereader, tst_qimagewriter, tst_qpixmap (deserves investigation, image format support),
tst_qmake (weird, need to have a look - perhaps bad mkspec used?)
tst_qmovie
tst_qnetworkconfiguration, tst_qnetworkconfigurationmanager, tst_qnetworksession (!)
tst_qwebpage
tst_uic, tst_uic3 (likely QTBUG-21523)
2 tests that SFE builds but we don't: tst_qdbusmarshall (QTBUG-22106), tst_qtconcurrentmap (QTBUG-12987)
4 tests that we build but SFE doesn't: tst_guiapplauncher, tst_qglthreads, tst_qwidget_window, tst_qwidget
20 tests where SFE fails while we pass:
tst_qabstractslider
tst_qcolumnview
tst_qcompleter
tst_qdialog
tst_qeventloop
tst_qfilesystemmodel
tst_qgl
tst_qglbuffer
tst_qgraphicsproxywidget
tst_qgraphicstransform
tst_qgraphicsview (not really a pass, but a few more tests are run in our build)
tst_qmdiarea
tst_qmessagebox (X Error: BadWindow)
tst_qprocess
tst_qreadwritelock
tst_qscriptengine
tst_qstring (no wide character support in the g++ build? Strange ... )
tst_qthread
tst_qtimeline
tst_xmlpatternsdiagnosticsts
It looks like the tests that included some performance measurements (tst_qcontiguouscache, tst_qdbusperformance, tst_qmutex, tst_qprocess) show better numbers for our bits, but I'd be far from interpreting it in that way. Both tests were run in a VirtualBox environment and the load on the host was quite different on the two occasions.
Webrev of the results (to save space only the udiff diffs were preserved)
The results bzipped
The tests source for reference
Thursday, September 1, 2011
KDE 4.7.0 with Solaris Studio 12.3 beta
KDEpim, the last package of the KDE 4.7.0 suite I care for (bindings never really worked and I've given up hope there) just built using the Solaris Studio 12.3 beta compiler.
Unfortunately, just as with Studio 12.1, one cannot login into the KDE session, it freezes somewhere in the splash screen, but the apps seem to be running fine when launched from GNOME.
Unfortunately, just as with Studio 12.1, one cannot login into the KDE session, it freezes somewhere in the splash screen, but the apps seem to be running fine when launched from GNOME.
Tuesday, August 9, 2011
4W LED bulb from DX
I got my hands at the 4W LED bulb from DealExtreme.
I put it to a directional reading lamp that normally hosts a 60W incandescent and the result was not really satisfying.
While the reviews at DX (most of them apparently written by the seller) say the light output is the same as a 40W incandescent, this is simply not true. Unfortunately I don't have any 25W nor 40W bulbs to compare, but I don't doubt a 25W one would still outshine it.
With the LED bulb the lamp can really be only used for reading and nothing more, but it's good enough at that (if you're close enough). Another plus is that it fits well in the lamp - a fluorescent compact bulb would be unacceptable here and there's no heat and no risk of broken glass in case of an accident.
Below are pictures of a white wall taken with Canon A85 in manual mode, using the same white balance, aperture and exposure values. (The spot in the top right is a defect that developed in the past year or so, I just don't have the A590 at hand ATM)
As a ghetto scientific method of light output measurement I also took a look at the histograms that GIMP kindly provides. It looks like the LED bulb is very weak in the blue part of the spectrum and the median value 2.5x higher (likely even more as part of the red channel is burned out in the 60W one) for the incandescent supports my estimate that the light output is at best comparable to a 25W incandescent.
I put it to a directional reading lamp that normally hosts a 60W incandescent and the result was not really satisfying.
While the reviews at DX (most of them apparently written by the seller) say the light output is the same as a 40W incandescent, this is simply not true. Unfortunately I don't have any 25W nor 40W bulbs to compare, but I don't doubt a 25W one would still outshine it.
With the LED bulb the lamp can really be only used for reading and nothing more, but it's good enough at that (if you're close enough). Another plus is that it fits well in the lamp - a fluorescent compact bulb would be unacceptable here and there's no heat and no risk of broken glass in case of an accident.
Below are pictures of a white wall taken with Canon A85 in manual mode, using the same white balance, aperture and exposure values. (The spot in the top right is a defect that developed in the past year or so, I just don't have the A590 at hand ATM)
As a ghetto scientific method of light output measurement I also took a look at the histograms that GIMP kindly provides. It looks like the LED bulb is very weak in the blue part of the spectrum and the median value 2.5x higher (likely even more as part of the red channel is burned out in the 60W one) for the incandescent supports my estimate that the light output is at best comparable to a 25W incandescent.
 |
| 4W LED |
 |
| 60W incancescent |
 |
| 4W histogram |
 | |
| 60W histogram |
Saturday, July 16, 2011
Sun Java on Fedora 15
For the next time I need it: https://www.martineve.com/2011/06/08/six-lines-to-get-sun-java-running-on-fedora-15-x64/
because the upstream instructions are hopelessly useless...
because the upstream instructions are hopelessly useless...
Saturday, July 9, 2011
KDE 4.7 RC1
Some screenshots from KDE 4.7 RC1.
I don't have konsole yet as it was split into another package and so far only the bare minimum required for KDE gdm-integration is ready.
I don't have konsole yet as it was split into another package and so far only the bare minimum required for KDE gdm-integration is ready.
Sunday, July 3, 2011
OS upgrade
Over the weekend I've migrated to Fedora 15. I've briefly considered going back to Mandriva, but since Mageia forked off it, bot distros are weaker than the original one. Of course Fedora is not a miracle either, it's nowhere near the level of comfort I was used to from Mandriva and I've already been hit by a bug in the kernel, but at least I can expect every possible piece of software to be available with decent stability.
Subscribe to:
Posts (Atom)