On 25 Oct 2003 11:39:24 -0700, Jan Kostal wrote: > > On Fri, 24 Oct 2003, Mikhael Goikhman wrote: > > > On 24 Oct 2003 23:47:57 +0200, Kostal wrote: > > > > > > > Make sure the files in question really are xpm files. > > > > > > It is on my home computer so I will test that as soon as I am at home, > > > however, those files are installed from the standard package > > > fvwm-icons. Do you still think they may not be real xpm files? > > > > If these are XPM files, then you didn't compiled XPM support in. > > > > Run fvwm-config --info, or try to load these images using fvwm-root. > > I see ....... You are right: > > When I run > $ fvwm-config --info > I get > Package: fvwm > Version: 2.4.16 > > Instalation options: > bindir: /usr/local/bin > > Support for features: > xpm: no > ..................... > But during installation it looked all fine: > in-the-fvwm.src-directory: > # ./configure > aaa > # cat aaa | grep -i xpm > checking for XpmReadFileToXpmImage in -lXpm... yes > checking X11/xpm.h usability... yes > checking X11/xpm.h presence... yes > checking for X11/xpm.h... yes > checking for Xpm 3.4g or better... yes > With XPM support? yes > ......................... > What went wrong? Any ideas now?
You didn't say that you didn't define your own prefix and configure says: Executables: /usr/local/bin You also didn't convince us you did "make install" after that. Or maybe you did, but it failed without write permissions to /usr/local. The only sure thing is the /usr/local/bin/fvwm executable on your system is not that you built with the "XPM support? yes" output above. Regards, Mikhael. -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
