Closed Bug 383348 Opened 17 years ago Closed 6 years ago

configure should fail if you don't have gconf, gnome-vfs

Categories

(Firefox Build System :: General, defect)

x86
Linux
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mrbkap, Assigned: reznord)

References

Details

(Keywords: helpwanted)

Attachments

(1 file, 1 obsolete file)

I've noticed that every time I right click in my debug build on Linux, I get:

*** e = [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame :: chrome://browser/content/utilityOverlay.js :: getShellService :: line 285"  data: no]

Talking to gavin on IRC, he mentioned that the lack of a shell service on Linux is expected, and that we might just want to remove the dump that is filling my console with unnecessary spam.
This turned out to be because I didn't have gconf and friends installed. I'm rebuilding my tree now after installing them, and hopefully the console spam will go away. It would have been nice if configure had printed a warning that I was missing these. Currently, it silently just disables the affected modules.
Summary: Console spam on right clicks → configure silently fails if you don't have gconf, gnome-vfs
Component: General → Build Config
QA Contact: general → build.config
luser pointed out on IRC that we need to add an error message here (like is done with the other checks) instead of just silently disabling: http://mxr.mozilla.org/seamonkey/source/configure.in#4982.
Summary: configure silently fails if you don't have gconf, gnome-vfs → configure should fail if you don't have gconf, gnome-vfs
(In reply to comment #2)
> luser pointed out on IRC that we need to add an error message here (like is
> done with the other checks) instead of just silently disabling:
> http://mxr.mozilla.org/seamonkey/source/configure.in#4982.

More permanent link:
http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/configure.in&rev=1.1918&root=/cvsroot#4856
Attached patch don't fail, but do complain (obsolete) — Splinter Review
Attachment #318937 - Flags: review?(ted.mielczarek)
The build should fail, a complaint isn't enough.
Comment on attachment 318937 [details] [diff] [review]
don't fail, but do complain

No, I really think we should error. This is the only sane way to do things.
Attachment #318937 - Flags: review?(ted.mielczarek) → review-
we should consider to provide a kde adaption layer for the basic desktop integration features that we deliver through gconf gnome-vfs atm.

Maybe the Ubuntu spec on this: https://wiki.ubuntu.com/Firefox3KDEIntegrationIntrepid
Over in bug 506452, I didn't have the libgconf2-dev and libgnomevfs2-dev packages
installed, so the build system chose not to compile mozgnome at all instead of
warning me at configure stage.  I installed libgconf2-dev and libgnomevfs2-dev
and rebuilt, expecting that the problem would be solved, but it wasn't.  Turns
out that I needed to manually add these two lines to my .mozconfig file
manually.

mk_add_options MOZ_GCONF_CFLAGS=-I/usr/include/gconf/2
mk_add_options MOZ_GNOMEVFS_CFLAGS=-I/usr/include/gnome-vfs-2.0

I think the build system should be able to pick these directories up automatically.
Version: unspecified → Trunk
It should, I think you just needed to reconfigure or possibly remove config.cache.
Attached patch patch?Splinter Review
I'm not sure what to do about the MOZ_EXTENSIONS interaction.
Attachment #318937 - Attachment is obsolete: true
It looks like I am hitting this bug while testing on ubuntu 12.04 VMs in our EC2 cloud.
Hi, I would like to take on this bug. Can you please assign this to me?
Assignee: nobody → allamsetty.anup
Triaging, old bug, not applicable closing.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: