Re: Build failure: mozilla-plugin
Hi all, trying to build classpath cvs fails for me right now, because I don't have package mozilla-plugin installed on my Linux system. (I do have mozilla, but I don't have any plugins except Suns JRE and flash-blocked flash.) Anyway, I think that classpath should be buildable without any mozilla dependencies. Try --disable-plugin. I also stepped over this some days ago. This build failure is a little crude (at least for me it was), because ./configure did _not_ complain about a missing firefox-dev package or so, but completed successfully. Later in the build I got a couple of error messages that are not exceptionally useful, until I figured out that I was only missing a mozilla header file package. I already reported this as bug: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29346 And I think we should really solve this before release, as it will certainly confuse people who want to compile classpath and don't happen to have all the required packages installed. Something similar happens with a missing c++ compiler: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29345 /Roman
Re: Build failure: mozilla-plugin
Tom Tromey wrote: Tom == Thomas Fitzsimmons [EMAIL PROTECTED] writes: Anyway, I think that classpath should be buildable without any mozilla dependencies. Tom Try --disable-plugin. For eclipse-based builds it would be friendlier if, by default, configure would search for the needed libraries and then simply not compile things if dependencies are missing. I considered this approach. I'd rather it be clear that certain features of GNU Classpath are disabled if one does not have the proper dependencies installed. An alternative to configure failing outright that I've seen in other projects is printing out a long list of: feature x: enabled feature y: disabled lines at the end of the configure run. Even then though, it's not clear to a person wanting to build the plugin (which should be the majority of GNU Classpath developers) why it is disabled. The current configure failure makes it very clear that he needs the Mozilla development libraries to have a full-featured GNU Classpath build. Also I noticed we are doing this: AC_SUBST(PLUGIN_DIR, $HOME/.mozilla/plugins/) That seems weird, especially for distro use. (Also according to GNU standards we shouldn't install anything outside $prefix.) I think we probably need another option to set this install directory. Finally... I see this in the plugin Makefile.am: install-libLTLIBRARIES: $(lib_LTLIBRARIES) $(INSTALL) -d -m0755 $(DESTDIR)@PLUGIN_DIR@ $(INSTALL) .libs/libgcjwebplugin.so $(DESTDIR)@PLUGIN_DIR@ Overriding an internal rule is not supported by automake. If we really, really want to do this, then the correct approach is a new directory variable. Yes, these are a little weird. I copied them directly from gcjwebplugin. I like this as the default behaviour because it means that make make install actually installs the plugin in a useable way. What about a --with-plugin-directory option that defaults to $HOME/.mozilla/plugins? Then packagers could override this with /usr/lib/mozilla/plugins. Tom
Re: Build failure: mozilla-plugin
Tom == Thomas Fitzsimmons [EMAIL PROTECTED] writes: Anyway, I think that classpath should be buildable without any mozilla dependencies. Tom Try --disable-plugin. For eclipse-based builds it would be friendlier if, by default, configure would search for the needed libraries and then simply not compile things if dependencies are missing. Also I noticed we are doing this: AC_SUBST(PLUGIN_DIR, $HOME/.mozilla/plugins/) That seems weird, especially for distro use. (Also according to GNU standards we shouldn't install anything outside $prefix.) I think we probably need another option to set this install directory. Finally... I see this in the plugin Makefile.am: install-libLTLIBRARIES: $(lib_LTLIBRARIES) $(INSTALL) -d -m0755 $(DESTDIR)@PLUGIN_DIR@ $(INSTALL) .libs/libgcjwebplugin.so $(DESTDIR)@PLUGIN_DIR@ Overriding an internal rule is not supported by automake. If we really, really want to do this, then the correct approach is a new directory variable. Tom
Re: Build failure: mozilla-plugin
Norman Hendrich wrote: Hello all, trying to build classpath cvs fails for me right now, because I don't have package mozilla-plugin installed on my Linux system. (I do have mozilla, but I don't have any plugins except Suns JRE and flash-blocked flash.) Anyway, I think that classpath should be buildable without any mozilla dependencies. Try --disable-plugin. Tom
Re: Build failure: mozilla-plugin
Hello Tom, Try --disable-plugin. oops... ok, works. Thanks. Guess I should have grep'ed for plugin instead of mozilla in ChangeLog*. Perhaps a better error message is in order? - Norman
Re: Build failure: mozilla-plugin
Thomas Fitzsimmons wrote: Norman Hendrich wrote: Hello all, trying to build classpath cvs fails for me right now, because I don't have package mozilla-plugin installed on my Linux system. (I do have mozilla, but I don't have any plugins except Suns JRE and flash-blocked flash.) Anyway, I think that classpath should be buildable without any mozilla dependencies. Try --disable-plugin. fx:drums fingers -- 犬 Chris Burdess They that can give up essential liberty to obtain a little safety deserve neither liberty nor safety. - Benjamin Franklin PGP.sig Description: This is a digitally signed message part
