On Jan 21, 2008 4:40 PM, Ken Moffat <[EMAIL PROTECTED]> wrote: > On Sun, Jan 20, 2008 at 11:01:29PM +0000, Ken Moffat wrote: > > > > Thanks for this, and your other response - I'll play with the > > patches once I'm back on LFS-6.3 x86. > > > After I looked at the patch, I started to think it might be trying > to fix a different problem. The MOZILLA_NOT_LINKED_CFLAGS doesn't > sound like what I think I'm building. To clarify, at the end of > configure I get the following report: > > configure: Totem was configured with the following options: > configure: ** Using the GStreamer-0.10 backend > configure: ** Easy codec installation support enabled > configure: nvtv support disabled > configure: vanity compilation disabled > configure: ** GNOME version enabled > configure: ** Browser plugin enabled (using firefox) > configure: ** Basic browser plugin enabled > configure: ** GMP (Windows Media) plugin enabled > configure: ** Complex (Real) plugin enabled > configure: ** NarrowSpace (QuickTime) plugin enabled > configure: ** MullY (DivX) plugin enabled > configure: ** Nautilus properties page enabled > configure: Media player keys support disabled > configure: LIRC support disabled > configure: HAL support disabled > configure: ** XTest (legacy screensaver) support enabled > configure: ** D-Bus (gnome-screensaver) support enabled > configure: ** XVidmode support enabled > configure: ** XFree86 multimedia keys support enabled > configure: End options > > I'm surprised by 'Nautilus properties page enabled', and also by > 'legacy screensaver', but that's what it finds.
I don't know what "Nautilus properties page" is, but I think "legacy screensaver" just means it will fall back to using libXScrnSaver if it doesn't find the DBus interface to gnome-screensaver at runtime. > FWIW, I couldn't persuade 'patch' to apply your patch to 2.18.2, > which is what is in blfs-svn, even after I sorted out the line-wrap > at the end - the hunk is at line 379 instead of 466, but even after > editing that it still wouldn't apply for reasons that escape me. Yeah, that was against 2.20.3, which I thought you mentioned you were using. Maybe the variables are named something different in 2.18.x. > The "quick and dirty fix" needs "cat >> browser-plugin/Makefile.in" > instead of "cat > ...", I think. Anyway, it still doesn't help, > the error messages with fresh source still begin > > totem-plugin-viewer.c:38:22: error: libsn/sn.h: No such file or > directory > totem-plugin-viewer.c:587: error: expected ')' before '*' token > totem-plugin-viewer.c:594: error: expected ')' before '*' token > totem-plugin-viewer.c:601: error: expected ')' before '*' token > totem-plugin-viewer.c: In function 'free_startup_timeout': > totem-plugin-viewer.c:662: error: 'sn_launcher_context_unref' > undeclared (first use in this function) > totem-plugin-viewer.c:662: error: (Each undeclared identifier is > reported only once > totem-plugin-viewer.c:662: error: for each function it appears in.) > totem-plugin-viewer.c: In function 'startup_timeout': > totem-plugin-viewer.c:690: error: 'SnLauncherContext' undeclared > (first use in this function) > totem-plugin-viewer.c:690: error: 'sn_context' undeclared (first use > in this function) So, clearly it's not picking up the startup-notification CFLAGS. So, take a look at browser-plugin/Makefile.am. Look for totem_plugin_viewer_CFLAGS. In 2.20.3, it was using $(BROWSER_PLUGIN_CFLAGS), which gets generated using the pkg-config check in configure.ac. So, the hack is to find some variable it's using for totem_plugin_viewer_CFLAGS and tack on your extra information onto the end of browser-plugin/Makefile.in (not Makefile.am unless you want to regenerate the autotools). You could probably even just use `echo "totem_plugin_viewer_CFLAGS += $(pkg-config --cflags libstartup-notification-1.0)" >> browser-plugin/Makefile.in'. And the libraries into totem_plugin_viewer_LDADD. Or, you can just kludge the whole thing in through configure. export CPPFLAGS=$(pkg-config --cflags libstartup-notification-1.0) export LIBS=$(pkg-config --libs libstartup-notification-1.0) ./configure ... -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
