When emerging chromium-9999, it fails with the following error: x86_64-pc-linux-gnu-ar: out/Release/obj.target/i18n_api/v8/src/extensions/experimental/i18n-extension.o: No such file or directory make: *** [out/Release/obj.target/v8/src/extensions/experimental/libi18n_api.a] Error 1 make: *** Waiting for unfinished jobs.... emake failed I suppose it's due to system V8 use. ================================================================= Package Settings ================================================================= www-client/chromium-9999 was built with the following: USE="cups gecko-mediaplayer gnome gnome-keyring (multilib) -test" CFLAGS="-O2 -pipe -march=native -ggdb -DGENTOO_CHROMIUM_ENABLE_GECKO_MEDIAPLAYER" CXXFLAGS="-O2 -pipe -march=native -ggdb -DGENTOO_CHROMIUM_ENABLE_GECKO_MEDIAPLAYER"
I get the same error. I disabled system v8 in my overlay and got it to build successfully. I guess I have my weekend project! :)
I've tracked this down to this webkit changeset: http://trac.webkit.org/changeset/78095/trunk Looks like this will take some work to untangle.
(In reply to comment #2) > I've tracked this down to this webkit changeset: > http://trac.webkit.org/changeset/78095/trunk Great, thank you! > Looks like this will take some work to untangle. Not necessarily, we can just disable ENABLE_JAVASCRIPT_I18N_API in features.gypi, and if necessary patch out this gyp change: + ['javascript_engine=="v8"', { + 'dependencies': [ + '<(chromium_src_dir)/v8/src/extensions/experimental/experimental.gyp:i18n_api', + ], + }],
(In reply to comment #3) > Not necessarily, we can just disable ENABLE_JAVASCRIPT_I18N_API in > features.gypi, and if necessary patch out this gyp change: Yup, I already have a patch for WebCore.gyp. For the ENABLE_JAVASCRIPT_I18N_API part, is there a way to do that with a gyp -D flag, or do I need to patch/sed features.gyp (or build/features_override.gypi)? I thought this would be more complicated because I was going get the feature working rather than disabling it. I'll poke around some more anyway.
(In reply to comment #4) > For the ENABLE_JAVASCRIPT_I18N_API part, is there a way to do that with a gyp > -D flag, or do I need to patch/sed features.gyp (or > build/features_override.gypi)? I think you'd have to patch it, but in a way that allows control via -D flags. Some examples can be found in http://codesearch.google.com/codesearch/p#OAMlx_jo-ck/src/build/features_override.gypi&exact_package=chromium > I thought this would be more complicated because I was going get the feature > working rather than disabling it. I'll poke around some more anyway. Maybe we can compile dev-lang/v8 with those experimental features compiled in. That generally sounds good.
Should be fixed, thanks for reporting.
