On Tue, Oct 18, 2011 at 11:51:43AM -0400, Donald Allen wrote: > 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?
It is checked at configure time as it happens. It's possible though that you might have a non-standard install of a newer fribidi library somewhere which the standard search path isn't finding? But I've tested it here iwth 0.10.9 -- the configure check discards that, as it falls below the miniumum version FVWM tries to use. > Slackware 13.37 installs fribidi-0.10.9. Yes, I know. See: http://www.linuxquestions.org/questions/slackware-14/ot-new-stable-fvwm-release-875239/page3.html#post4328755 and any of the other posts surrounding that. > 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. It mentions its negation, and also ./configure mentions that options in general have --enable-* --disable-* pairs: [thomas@debian][fvwm.git][branch-2_6 *] % ./configure --help | grep bidi --disable-bidi disable bi-directional text support --with-fribidi-bindir=DIR directory of fribidi-config if not in PATH [thomas@debian][fvwm.git][branch-2_6 *] % So far, it's only Slackware which is falling behind with the newer version of fribidi, FWIW. Other distros long since switched to 0.19.2 a while ago, and I have zero interest in supporting an older version with more and more #ifdef hacks needed. The same principle would apply for any library FVWM tries to link against, FWIW -- libpng is becoming another PITA in that regard. -- Thomas Adam
