On Wed, Oct 19, 2011 at 10:28 AM, Thomas Adam <tho...@fvwm.org> wrote: > 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?
Nope. > > 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. It did not do so on my system. > >> 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 *] > % Again, not so on my system. I did exactly the same thing you did -- piped the output of configure --help through grep (I used -i to avoid case issues) and it turned up only the --with-fribidi-bindir=DIR > > 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. I certainly don't blame you for that. What you are doing makes sense. It would be nice to understand what the issues are with configure -- why you are getting different results on debian than I'm getting on slackware. However, I don't think fvwm is for me -- I did get it built and tried it for a bit. But it's dauntingly complex and the default setup is not acceptable to me -- I'm a minimalistic kind of guy (I ran dwm for a long time and would continue to do so, but I've run into a couple of annoying problems with it and also there are a couple of patches that are not in the main stream code that I consider essential, creating a maintenance headache; I still might go back to it). I really don't have the time right now to wade through all the fvwm documentation and configure it in a way that would be satisfactory to me (though I'm guessing that's possible to do). At the moment, I'm running, believe it or not, twm. I have a .twmrc that creates close to the right environment for me. My concern with twm is less its behavior than the fact that it is no longer maintained. The X world could change in ways that could make twm even more obsolete than it already is. So I'm probably not settled on a wm at this point. Having said that, if you'd like a bit of help trying to debug the Slackware/configure issues, I'll be happy to try to provide some assistance. /Don > > The same principle would apply for any library FVWM tries to link against, > FWIW -- libpng is becoming another PITA in that regard. > > -- Thomas Adam >
