GNOME Bugzilla – Bug 307418
looks only for mozilla-nss/nspr; should also look for firefox-nss/nspr(?)
Last modified: 2013-09-14 16:50:03 UTC
I've been trying to build e-d-s against firefox, both from packages and from a patched jhbuild. Both fail looking for nspr.h. As far as I can tell from the configure logs this is because the configure test only looks for mozilla-nss, whereas firefox-nss is what is registered with package config (both by the packaged and jhbuilt firefoxes), and what provides nspr.h (which is definitely present.) As best as I can tell from the current build and from poking at configure.in, the manual autoconf test for nspr.h is succeeding, but then somehow the build itself is not finding it. No clue why this is happening, or how to fix it. I'll attach config.status, config.log, and the build/configure log shortly.
Created attachment 47666 [details] A log of the build. This is a log of the build, showing particularly the exact failure mode.
Created attachment 47667 [details] config.log file
Created attachment 47668 [details] config.status Config.status. Let me know if there is anything else you need.
Have you tried using the --with-nspr-includes=PATH and --with-nspr-libs=PATH e-d-s autogen.sh's options when build it?
EDS' configure.in's pkg-config check does this: PKG_CHECK_MODULES(NSS, mozilla-nss, have_nss="yes", have_nss="no") But on firefox, it needs to check for "firefox-nss", and on xulrunner for "xulrunner-nss". And then later you have to also adapt the mozilla_nspr="mozilla-nspr" line accordingly.
Same for Evolution...
Is this bug being worked on? It seems to me this is blocking Firefox1.5/Epiphany for GNOME 2.14.
It seems to me too. See http://jhbuild.bxlug.be/builds/2006-05-11-0001/logs/epiphany/#configure for a build log showing the exact error message.
Eh, that is just epiphany that recently dropped support for ancient mozilla versions. This bug report is about evolution-data-server not able to find firefox headers.
Luis, Currently, e-d-s configure.in is checking for nss, mozilla-nss, or firefox-nss. The check is done in the following way: > AC_MSG_CHECKING(Mozilla NSS pkg-config module name) > mozilla_nss_pcs="nss mozilla-nss firefox-nss" > for pc in $mozilla_nss_pcs; do > if $PKG_CONFIG --exists $pc; then > AC_MSG_RESULT($pc) > mozilla_nss=$pc > break; > fi > done The same holds for nspr. If there are other possibilities (xulrunner-nss, for instance) it should be only needed to add them to the mozilla_{nss,nspr}_pcs variable. Can you please check if the bug is still reproducible? My bet is that it isn't (but I may be missing something).
(In reply to comment #10) > Can you please check if the bug is still reproducible? My bet is that it isn't > (but I may be missing something). /me forgot to mention that this holds for both HEAD and gnome-2-14 branches.
I think it should check for xulrunner- and seamonkey- nss/nspr too.
I can't check now; I haven't been building things for a while. It would be great if someone could take this up with the folks who are building things at http://mail.gnome.org/mailman/listinfo/gnome-packaging-list
Patches to add support for xulrunner and seamonkey available at bugs #348197 (e-d-s) and #348198 (evo). e-d-s is able to build against xulrunner (using the modulest for jhbuild suggested in bug #324546 comment 4). evo is untested by now.
Created attachment 69432 [details] [review] Also looks for xulrunner and seamonkey NSS/NSPR This is the obvious patch; I have been using it for months without any problem. Please consider it, thanks.
This has been fixed for {,mozilla-,firefox-}{nspr,nss} for quite a while already, both evolution and e-d-s, both HEAD and gnome-2-14 branch. Yay... ;) Bug 348197 and bug 349198 have been committed to HEAD, too. Thanks for the patches, everyone. Closing RESOLVED FIXED.
(In reply to comment #16) > Bug 348197 and bug 349198 have been committed to HEAD, too. Obviously, make that "bug 348197 and bug 348198"... :)