It is necessary to compile gpac-0.4.1_pre* and gpac-0.4.2 with USE='-wxwindows' for linking to succeed with gcc-4* on PPC. # sudo emerge -q -pv gpac [ebuild R ] media-video/gpac-0.4.2 USE="aac ffmpeg javascript jpeg mad ogg opengl png sdl ssl theora truetype vorbis wxwindows* xml xvid -amr -debug -oss" g++ -fno-strict-aliasing -Wall -I/var/tmp/portage/gpac-0.4.2/work/gpac/include -I/usr/lib/wx/include/gtk2-un icode-release-2.6 -I/usr/include/wx-2.6 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILE S -DNO_GCC_PRAGMA -c -o menubtn.o menubtn.cpp gcc -Wl,--warn-common -o ../../bin/gcc/Osmo4 wxOsmo4.o wxGPACControl.o fileprops.o Playlist.o menubtn.o -L../ ../bin/gcc -lgpac -pthread -L/usr/X11R6/lib -lwx_gtk2u_core-2.6 -lwx_baseu-2.6 -lz /usr/lib/gcc/powerpc-unknown-linux-gnu/4.1.1/../../../../powerpc-unknown-linux-gnu/bin/ld: dynamic variable `_SDA_BASE_@@WXU_2.6' is zero size /usr/lib/gcc/powerpc-unknown-linux-gnu/4.1.1/../../../../powerpc-unknown-linux-gnu/bin/ld: /usr/lib/gcc/power pc-unknown-linux-gnu/4.1.1/../../../crt1.o(.rodata+0x0): unresolvable R_PPC_ADDR32 relocation against symbol `_SDA_BASE_@@WXU_2.6' /usr/lib/gcc/powerpc-unknown-linux-gnu/4.1.1/../../../../powerpc-unknown-linux-gnu/bin/ld: final link failed: Nonrepresentable section on output collect2: ld returned 1 exit status make[2]: *** [Osmo4] Error 1 make[2]: Leaving directory `/var/tmp/portage/gpac-0.4.2/work/gpac/applications/osmo4_wx' make[1]: *** [apps] Error 2 make[1]: Leaving directory `/var/tmp/portage/gpac-0.4.2/work/gpac/applications' make: *** [apps] Error 2
Created attachment 100385 [details] emerge --info
Created attachment 100386 [details] portage log of gpac-0.4.2 failing with USE=wxwindows
*** Bug 152902 has been marked as a duplicate of this bug. ***
rebuild wx please...
Confirmed. My genlop -l shows that I effectively did: (1) build of wxGTK 2.4* and 2.6* (2) upgrade only binutils (3) compile against wxGTK (4) notice failure to link Recompiling wxGTK with new binutils then allows new packages to link against it. (Unusual behavior IMHO.) Change to whatever resolution you think most appropriate :).
Worked for me after the upgrade. It's weird behaviour, but I don't think that we can "fix" it. Feel free to reopen if you have an idea as to how to catch the problem.