On Fri, Mar 13, 2015 at 12:12:19AM -0700, Alan Irwin wrote: > On 2015-03-12 01:46-0700 Alan W. Irwin wrote: > > > For Debian stable, I got most of the required Qt5 build-depends by > > installing the build-depends of the Qt4 source package, then following > > up by iterating epa_builds to get the extra ones needed for the > > epa_build of Qt5. But I think the whole deal could be completed by > > just one "apt-get build-dep" command for you with no further > > iterations required since the Debian unstable version of Qt5 is > > virtually identical to what is used by epa_build. > > Hi Andrew: > > The configuration changes for the epa_build of Qt5 that I pushed > (commit id = cfc6e135) on Tuesday made sure virtually all components > of Qt5 were built, but those extra components did not solve the memory > management issue (in fact introduced some extra warnings related to > dbus, etc.,) so now I have experimentally gone the other way (commit > id = fd4ef4a) and reduced the epa_build of Qt5 to the absolute minimum > components needed by PLplot. (For example, dbus is excluded.) As a > result of these changes, the time required here to epa_build Qt5 has > been reduced from 2 hours to 13.5 minutes! As expected from previous > experience with the insensitivity of the memory management issue to > Qt5 build configuration, the valgrind results are essentially the same > as before; relatively clean for all Qt file devices that I sampled, > and a single invalid read error on plend for -dev qtwidget. > > To access that dramatic speedup in the epa_build of Qt5 (and many > fewer library dependencies of that build) use the latest master tip > version of PLplot.
Thanks. Actually I've been running into further problems even after fixing the dependencies as you suggested. 1) The cairo build fails (seems to be due to a bug in cairo build scripts exposed in gcc-4.9.0 - see http://sourceforge.net/p/mingw-w64/bugs/396/) 2) The libharu build succeeds, but the hpdf_pdfa.h include file is not installed so the plplot build of the pdf driver fails. I don't have time to investigate further. Just installing the debian packages is a workaround. I did get Qt5 to build under epa (this is before your latest commit) and so I did a separate build, put pointing cmake to this epa version. This worked and the valgrind test results are below. I did not see any invalid read errors. I did get a warning about xbd though, and return did not seem to work to exit the plot page. I had to use the right mouse button instead. This may well be related to my pbuilder environment, though I didn't get the message with the debian package. Anyway, the key message is that even with an epa_build of Qt5 I do not see the error so it is not an intrinsic Qt5 / plplot problem, but something different between our setups is causing problems. Andrew root@andrew-laptop:~/software/plplot/build_test# valgrind examples/c/x01c -dev qtwidget ==5793== Memcheck, a memory error detector ==5793== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==5793== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==5793== Command: examples/c/x01c -dev qtwidget ==5793== PLplot library version: 5.10.0 xkbcommon: ERROR: failed to add default include path auto Qt: Failed to create XKB context! Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ . ==5799== Warning: invalid file descriptor 1024 in syscall close() ==5799== Warning: invalid file descriptor 1025 in syscall close() ==5799== Warning: invalid file descriptor 1026 in syscall close() ==5799== Warning: invalid file descriptor 1027 in syscall close() ==5799== Use --log-fd=<number> to select an alternative log fd. ==5799== Warning: invalid file descriptor 1028 in syscall close() ==5799== Warning: invalid file descriptor 1029 in syscall close() ==5799== ==5799== HEAP SUMMARY: ==5799== in use at exit: 240,274 bytes in 974 blocks ==5799== total heap usage: 5,483 allocs, 4,509 frees, 854,919 bytes allocated ==5799== ==5799== LEAK SUMMARY: ==5799== definitely lost: 2,476 bytes in 10 blocks ==5799== indirectly lost: 24 bytes in 1 blocks ==5799== possibly lost: 0 bytes in 0 blocks ==5799== still reachable: 237,774 bytes in 963 blocks ==5799== suppressed: 0 bytes in 0 blocks ==5799== Rerun with --leak-check=full to see details of leaked memory ==5799== ==5799== For counts of detected and suppressed errors, rerun with: -v ==5799== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==5793== ==5793== HEAP SUMMARY: ==5793== in use at exit: 40,997 bytes in 166 blocks ==5793== total heap usage: 39,484 allocs, 39,318 frees, 12,951,762 bytes allocated ==5793== ==5793== LEAK SUMMARY: ==5793== definitely lost: 2,254 bytes in 31 blocks ==5793== indirectly lost: 313 bytes in 5 blocks ==5793== possibly lost: 0 bytes in 0 blocks ==5793== still reachable: 38,430 bytes in 130 blocks ==5793== suppressed: 0 bytes in 0 blocks ==5793== Rerun with --leak-check=full to see details of leaked memory ==5793== ==5793== For counts of detected and suppressed errors, rerun with: -v ==5793== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1) ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
