> %% Regarding FVWM: Various; you wrote:
> gmg> Incidentally, both versions compiled just fine except for
> gmg> needing to have lots of work done to all the Makefiles, which
> gmg> was a pain.
> You shouldn't need any work done to the makefiles, so this is
> suspicious. However, you don't give nearly enough information for us to
> help you.
The changes had to do with MANPATH not being set the way I wanted it,
XPMINCLUDE not being used, and my not setting FVWMDIR properly.
> What version of UNIX are you using? What compiler? What make? What
> version of XPM? What version of X11? What kinds of things did you have
> to do to the makefile? Why didn't xmkmf do those for you (do you have
> xmkmf)? Are you sure you modified your .xinitrc file correctly to
> invoke fvwm (or are you using XDM or something)? Did fvwm install in
> the right place?
I'm using Solaris 2.4, my compiler is "/usr/local/SUNWspro/SC3.0/bin/cc".
make is "/usr/ccs/bin/make" (I know pathnames aren't usually helpful, but
that's the best I can do). I'm using OpenWin. I already mentioned what I had
to do to the Makefiles. My .xinitrc does properly invoke fvwm. If it didn't,
I wouldn't have been able to use pl34. fvwm did install in the right place.
> You should always redirect output to a file when starting X; that helps
> greatly. For example, I use this little script to start X on my system:
> #!/bin/sh
> exec startx > $HOME/.Xerrorlog 2>&1
I use xinit, but it should work the same. I'll try it next time.
Gail
--
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 Thu Sep 28 1995 - 14:13:15 BST