jhenders_at_wu.bogon.com (John Henders) writes:
> In <87u3y4zype.fsf_at_cyteen.pp.icon.fi> cyteen_at_avalon.icon.fi (Juri Pakaste) writes:
> >Juri Pakaste <cyteen_at_avalon.icon.fi> writes:
>
> >> (I have a Linux/ELF system). I'm having trouble with getting fvwm
> >> 2.0.4[12] (I upgraded my system just recently, so I haven't tried any
> >> of the earlier betas with it) to work with pixmaps. I have defined
> >> "HasXpm YES" in Fvwm.tmpl and get no errors while
> >> building. The xpm library seems to be linked into the binary:
>
> >Oh well, these things happen when you're a bit too tired; I forgot to
> >mention that it actually complains about having no Xpm support.
>
> If you do in fact have an ELF libXpm, do you have libXpm.so symlinked to
> it? Does fvwm compile? If these are true, you may be running into the
Yes and yes. In fact, I recompiled fvwm and the problems have
disappeared. I have no idea at all why it didn't work the first time
but works now. The first time I compiled it I made a debian package
out of it, but I can't see how it could have caused the strange
behaviour. The default debian packaging script calls make with the
option LDFLAGS=-s, but the fvwm makefile doesn't use a variable called
LDFLAGS. So AFAIK that shouldn't cause any problems. (Well, I don't
know it the -s option would be a problem, as the explanation on the
manpage doesn't tell me much.)
But at least fvwm works now, so I'm not complaining :).
--
// Juri Pakaste
// jurip_at_icon.fi
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Apr 29 1996 - 09:33:34 BST