Emerging boinc 6.2.15 on ppc32 works if wxwidgets not present, even when no GUI USE flags are set. I am guessing that if boinc's configure finds wxwidgets it on a ppc arch it assumes MacOS then squirts out code that fails to compile. The top part of these errors are shown below. I attach the full thing in a minute. --- Configuring BOINC 6.2.15 (Release) --- --- Build Components: (client only) --- checking build system type... powerpc-unknown-linux-gnu checking host system type... powerpc-unknown-linux-gnu checking target system type... powerpc-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for powerpc-unknown-linux-gnu-gcc... powerpc-unknown-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes /error ...skipping ccountInfoPage.o -MD -MP -MF .deps/boinc_gui-AccountInfoPage.Tpo -c -o boinc_gui-AccountInfoPage.o `test -f 'AccountInfoPage. cpp' || echo './'`AccountInfoPage.cpp In file included from AccountInfoPage.cpp:24: stdwx.h:58:55: error: wx/accel.h: No such file or directory stdwx.h:61:59: error: wx/settings.h: No such file or directory stdwx.h:65:63: error: wx/bitmap.h: No such file or directory stdwx.h:66:52: error: wx/toolbar.h: No such file or directory ... AccountInfoPage.cpp:539: error: 'wxCommandEvent' was not declared in this scope AccountInfoPage.cpp:539: error: expected primary-expression before ')' token AccountInfoPage.cpp:539: error: expected ',' or ';' before '{' token make[2]: *** [boinc_gui-AccountInfoPage.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/sci-misc/boinc-6.2.15/work/boinc-6.2.15/clientgui' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/sci-misc/boinc-6.2.15/work/boinc-6.2.15' make: *** [all] Error 2 * * ERROR: sci-misc/boinc-6.2.15 failed. * Call stack: ... Reproducible: Always Steps to Reproduce: In my case, on ppc32's without wxwidgets, no problem. On the machine where they are present it's arty ~ # eix -I wx [I] app-admin/eselect-wxwidgets Available versions: 0.8 Installed versions: 0.8(12:37:48 08/05/08) Homepage: http://www.gentoo.org Description: Manage the system default for wxWidgets packages. [I] x11-libs/wxGTK Available versions: (2.6) *2.6.4.0-r1 2.6.4.0-r4 (2.8) 2.8.8.1 ~2.8.9.1-r2 ~2.8.9.1-r3 {X debug doc gnome gstreamer joystick odbc opengl pch sdl unicode} Installed versions: 2.8.8.1(2.8)(10:17:12 10/18/08)(-X -debug -doc -gnome -gstreamer -odbc -opengl -pch -sdl) Homepage: http://wxwidgets.org/ Description: GTK+ version of wxWidgets, a cross-platform C++ GUI toolkit. Found 2 matches. arty ~ # eselect wxwidgets list Available wxWidgets profiles: [1] base-unicode-release-2.8 * In both the machines where the ebuild fails and works, the flags are the same: [ebuild R ] sci-misc/boinc-6.2.15 USE="-X (-bindist) -server unicode" LINGUAS="-ar -be -bg -ca -cs -da -de -el -en_US -es -eu -fi -fr -hr -hu -it -ja -lt -lv -nb -nl -pl -pt -pt_BR -ro -ru -sk -sl -sv_SE -tr -uk -zh_CN -zh_TW" Note that X is NOT selected in either case. Actual Results: ebuild fails. Expected Results: Working boinc as when no wxwidgets are around.
Created attachment 174422 [details] emerge --info on machine where ebuild works
Created attachment 174423 [details] emerge --info on machine where ebuild fails
Created attachment 174424 [details] emerge log (fails)
Created attachment 174426 [details] emerge env (fails)
Please test 6.4.5. I have nowhere to test on this arch :]
(In reply to comment #5) > Please test 6.4.5. I have nowhere to test on this arch :] > I can confirm 6.4.5-r1 works with x11-libs/wxGTK-2.6.4.0-r4 and quicky ~ # eselect wxwidgets list Available wxWidgets profiles: [1] gtk2-ansi-release-2.6 [2] gtk2-unicode-release-2.6 * I have not tested with the newer and stable wxGTK-2.8.9.1-r3, but the problem I initially found was that any wxWidgets around caused problems. That no longer is the case so I think this bug can be closed. THANKS FOR ALL THE HARD WORK!
