Created attachment 273353 [details] Build log. Midori was crashing on me, so I was attempting to re-compile webkit-gtk with debug flags. This is with MAKEOPTS="-j1", but my usual (non-debug) make.conf fails too. CCLD Programs/GtkLauncher ./.libs/libwebkit-1.0.so: undefined reference to `findEntity(char const*, unsigned int)' ./.libs/libwebkit-1.0.so: undefined reference to `findColor(char const*, unsigned int)' ./.libs/libwebkit-1.0.so: undefined reference to `findProp(char const*, unsigned int)' ./.libs/libwebkit-1.0.so: undefined reference to `findValue(char const*, unsigned int)' ./.libs/libwebkit-1.0.so: undefined reference to `findDoctypeEntry(char const*, unsigned int)' collect2: ld returned 1 exit status make[1]: *** [Programs/GtkLauncher] Error 1
Created attachment 273355 [details] emerge -pv webkit-gtk
Created attachment 273357 [details] emerge --info
Given that the general values and package values don't match, attach your make.conf.
Created attachment 273359 [details] make.conf Here you go. I override the compilation settings at the bottom. The ones that used to work no longer work either.
Given quite a few forum posts, you should first check if commenting those "Troubleshooting" values helps - due to quirky build system, that '-O2' might be required and 'LDFLAGS="-ggdb"' is an invalid value anyway.
It fails even with the troubleshooting section commented out. It worked at one point, because I have webkit-gtk installed. But recompiling with those same CFLAGS, LDFLAGS, etc. no longer works.
Created attachment 273367 [details] Successful build log from March 6th. Here's the build log from the last time it worked. You can tell from one of the gcc invocations that I hadn't enabled any of the troubleshooting stuff.
Switching to hardened gcc and disabling the troubleshooting stuff just allowed it to compile. I'm quite confused. This may be related or a dupe of bug 295318.
Looking at bug 357469, I'm pretty sure it's a dupe now. I bet what happened is, in the past, I just specified USE=debug on the command line even with the troubleshooting stuff commented out.
*** This bug has been marked as a duplicate of bug 295318 ***