Can't build wxGTK (as prerequisite of Audacity). Error output follows: c++ -c "-DwxINSTALL_PREFIX=\"/usr\"" -D__WXGTK__ -DGTK_NO_CHECK_CASTS -D_REE NTRANT -MMD -march=i686 -pipe -fomit-frame-pointer -funroll-loops -O2 -I. -I./l ib/wx/include/gtk-2.2 -I./include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -Wall -fPIC -o joystick.o ./src/g tk/joystick.cpp {standard input}: Assembler messages: {standard input}:763: Error: symbol `.LEHB4327' is already defined {standard input}:778: Error: symbol `.LEHE4327' is already defined make: *** [joystick.o] Error 1 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 27, Exitcode 2 !!! (no error message)
Have you recently updated your portage tree? There is a joystick fix already available. emerge rsync emerge audacity That should give you a "nearly bug free" build of wxGTK-2.2.9. :)
Thanks for that. The new ebuild did apply a patch to the joystick module. However, the emerge still fails: c++ -c "-DwxINSTALL_PREFIX=\"/usr\"" -D__WXGTK__ -DGTK_NO_CHECK_CASTS -D_REENTRANT -MMD -march=i686 -pipe -fomit-frame-pointer -funroll-loops -DZEXPORT='' -O2 -I. -I./lib/wx/include/gtk-2.2 -I./include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -Wall -fPIC -o joystick.o ./src/gtk/joystick.cpp {standard input}: Assembler messages: {standard input}:763: Error: symbol `.LEHB4327' is already defined {standard input}:778: Error: symbol `.LEHE4327' is already defined make: *** [joystick.o] Error 1
I'm not exactly sure how to attack this error as the only log message I have is from the assembler output from standard input... I have seen nothing on the wxGTK developer mailing list regarding this problem and I cannot reproduce the error myself. I will be posting to the mailing list as soon as I get some vital info from you. As soon as I get a response or if I get any ideas I will post here. If you can tell me what version of binutils and gcc, processor type, and make options you are using, that should be enough basic information to supply to the list.
compiling without "-fomit-frame-pointer -funroll-loops" fixed it for me
Can I get the bug reporter's confirmation that this change in compiler options fixes the problem? I do not set -fomit-frame-pointer nor -funroll-loops in my default compiling options as it sets things too aggressive for some programs to compile without error.
Yes - taking out '-funroll-loops' and '-fomit-frame-pointer' results in successful build. Thanks!