[ebuild N ] app-text/gnomesword-2.3.6 USE="spell xulrunner -debug -firefox -seamonkey" --snip-- checking for xgettext... (cached) /usr/bin/xgettext checking for GTKHTML... no checking for GTKHTML... no checking for GTKHTML... yes checking for gawk... (cached) gawk checking which gecko to use... libxul checking for compiler -fshort-wchar option... yes checking whether to enable C++ RTTI... no checking whether we have a gtk 2 gecko build... configure: error: This program needs a gtk 2 gecko build I think it's interesting I do have www-client/mozilla-firefox-3.0.2 and net-libs/xulrunner-1.9.0.2 and net-libs/xulrunner-1.8.1.16 .
Created attachment 166880 [details] gnomesword-2.3.6-config.log
Looks like it's not looking in the right place for mozilla-config.h and I can't find where the include path is set: configure:25145: checking whether we have a gtk 2 gecko build configure:25174: x86_64-pc-linux-gnu-g++ -o conftest -march=nocona -O2 -pipe -I/usr/include/xulrunner-1.9 conftest.cpp >&5 conftest.cpp:40:28: error: mozilla-config.h: No such file or directory conftest.cpp: In function 'int main()': conftest.cpp:44: error: 'MOZ_DEFAULT_TOOLKIT' was not declared in this scope configure:25177: $? = 1 configure: program exited with status 1 -- $ equery b mozilla-config.h [ Searching for file(s) mozilla-config.h in *... ] net-libs/xulrunner-1.8.1.16 (/usr/lib64/xulrunner/include/mozilla-config.h) net-libs/xulrunner-bin-1.8.1.16 (/opt/xulrunner/include/mozilla-config.h) net-libs/xulrunner-1.9.0.3 (/usr/include/xulrunner-1.9/unstable/mozilla-config.h) mail-client/mozilla-thunderbird-2.0.0.17 (/usr/lib64/mozilla-thunderbird/include/mozilla-config.h)
(In reply to comment #2) > Looks like it's not looking in the right place for mozilla-config.h and I can't > find where the include path is set: > > configure:25145: checking whether we have a gtk 2 gecko build [...] I'm not sure if this is of any help but I'm not sure how to track the problem. I've been keeping my eye on this bug with no responses so I figured I'd try building it myself from the official tarball. This built/worked fine for me as root, you could install in your home dir as a user if you prefer: ./configure --with-gecko=xulrunner --prefix=/opt/gnomesword My entire system is currently compiled with GCC 4.3.2, Gnome 2.22.ish, Firefox 3.03 and it's respective xulrunner ebuild dependency. Perhaps it's something with the use flag(s) not being passed down properly to the configure script?
my bad, i just realized it was built against xulrunner 1.8.1.17 which happened to be slotted in and remaining. i realized this when i removed it and gnomesword stopped working.
2.4.1 of gnomesword is out. I couldn't see from the project's site docs if it now works against newer gtk gecko builds.
It seems to compile and work when I add "--with-gecko=xulrunner" to G2CONF. Did not try 2.4.1 beyond testing a little bit...and the gcc43 patch no longer works. It's easy enough to change, but I didn't do it.
(In reply to comment #6) > Did not try 2.4.1 beyond testing a little bit...and the gcc43 patch no longer > works. It's easy enough to change, but I didn't do it. 2.4.1 is in the tree now, can you try that one
(In reply to comment #7) > 2.4.1 is in the tree now, can you try that one I can confirm that it only builds by appending "--with-gecko=xulrunner" to G2CONF. Maybe it deserves a distinct bug report. Ain't it?
perhaps the default logic searching for xulrunner needs to be modified or over-ridden to force the --use-gecko=xulrunner flag when two copies of xulrunner are present .. I'm not sure how this would work ..
(In reply to comment #6) > It seems to compile and work when I add "--with-gecko=xulrunner" to G2CONF. Alright, fixed, added that in gnomesword-2.4.1-r1 Please test and let me know if its working for you
(In reply to comment #10) > (In reply to comment #6) > > It seems to compile and work when I add "--with-gecko=xulrunner" to G2CONF. > > Alright, fixed, added that in gnomesword-2.4.1-r1 > > Please test and let me know if its working for you > Compiles and seems to work so far, but I haven't really stressed it yet. Thanks!
