On Tue, Oct 18, 2011 at 12:03 PM, Markus Hutmacher <postf...@mhutmacher.de> wrote: > Am 18.10.2011 17:51, schrieb Donald Allen: >> >> On Tue, Oct 18, 2011 at 10:48 AM, Thomas Adam<tho...@fvwm.org> wrote: >>> >>> On Tue, Oct 18, 2011 at 10:00:58AM -0400, Donald Allen wrote: >>>> >>>> I just downloaded fvwm 2.6.3 and attempted to build it, which resulted >>>> in >>>> >>>> gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include/freetype2 >>>> -pthread -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 >>>> -I/usr/lib64/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 >>>> -I/usr/include/cairo -I/usr/include/libpng14 -I/usr/include/pixman-1 >>>> -I/usr/include/freetype2 -Wall -Wno-implicit-int -g -O2 -MT >>>> safemalloc.o -MD -MP -MF .deps/safemalloc.Tpo -c -o safemalloc.o >>>> safemalloc.c >>>> mv -f .deps/safemalloc.Tpo .deps/safemalloc.Po >>>> gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include/freetype2 >>>> -pthread -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 >>>> -I/usr/lib64/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 >>>> -I/usr/include/cairo -I/usr/include/libpng14 -I/usr/include/pixman-1 >>>> -I/usr/include/freetype2 -Wall -Wno-implicit-int -g -O2 -MT >>>> FBidi.o -MD -MP -MF .deps/FBidi.Tpo -c -o FBidi.o FBidi.c >>>> FBidi.c: In function 'FBidiConvert': >>>> FBidi.c:53:2: error: 'FriBidiParType' undeclared (first use in this >>>> function) >>> >>> It's been mentioned a few times, but you must compile FVWM against >>> fribidi >>> 0.19.2. >> >> An oversight that this is not checked at configure time? >> >> Slackware 13.37 installs fribidi-0.10.9. >> >> Or disable it at configure time if you don't need it. >>>> >>>> I did subsequently try configure --with-gnome=no and got the same >>>> compilation error. >>> >>> You would do when you're looking to disable fribidi, and not GNOME. See >>> the >>> option again. What made you think this had anything to do with GNOME? >> >> I have absolutely no idea what FBidi.c does or what fribidi does, >> gnome or otherwise. But I ran configure --help and noted the >> --with-gnome option. Since I don't use gnome, I decided to try turning >> the option off, on the off-chance that it might improve things. It >> certainly couldn't hurt, since I was giving configure a more accurate >> picture of the build environment. >> >> I disabled configuring with fribidi, no thanks to configure --help, >> which makes no mention of --enable-bidi (I looked at the configure >> file itself) and was able to get it built. Thanks for getting me >> pointed in the right direction. >> >> /Don Allen >> >>> -- Thomas Adam >>> > Hallo Don, > > I've once built fvwm-2.6 on Slackware (when 13.37 was new) and ran into the > same issue. I remember that I simple upgraded fribidi to the necessary > version. You can use the Slackbuildscript from the official > Slackware-sources. > > Slackware comes with a relatively old version of fribidi because in Pat's > opinion the newer versions are not stable enough (well, in fact he ran into > issues with other packages depending on fribidi). But I had no difficulties > using the newer version of fribidi on my system.
Thanks. I took a different approach and just disabled fribidi (--enable-bidi=no is the magic incantation to configure), since I don't need it. Same result -- I got it built and it's running as I type. /Don > > Markus > > -- > > Regards > Markus Hutmacher > >
