Re: FVWM: Re: 2.5.x questions (Was: i can't run fvwm 2.4)
I tried the above. Make install works fine but if you make -k install-strip then the problem occurs. Dont know if this is the same thing, but is the make -k install-strip to remove the dedebug symbol tables? I just change -g -O2 in configure to -O3. -- 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]
Re: FVWM: Re: 2.5.x questions (Was: i can't run fvwm 2.4)
On 04 Sep 2002 22:07:19 -0700, elliot sowadsky wrote: I tried the above. Make install works fine but if you make -k install-strip then the problem occurs. Hmm, I can't reproduce this problem. /usr/bin/install -c -s ... exits with error, but does install a script with +x permissions for me. Anyway, eventually we'll switch to autoconf-2.53 when creating releases and make install-strip will work well even without -k parameter. Dont know if this is the same thing, but is the make -k install-strip to remove the dedebug symbol tables? I just change -g -O2 in configure to -O3. Yes, more or less the same effect may be done by: env CFLAGS=-O3 ./configure or (before make install): make CFLAGS=-O3 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]
FVWM: Re: 2.5.x questions (Was: i can't run fvwm 2.4)
On Tue, 3 Sep 2002, Mikhael Goikhman wrote: On 03 Sep 2002 12:02:41 +, Bruce M Beach wrote: 1) I am at this point using 2.5.2 more or less because I have to. I think your short description (in another thread) is not enough to understand the problem. Please add more details to that message. What is the mouse-menu problem and what to do exactly to reproduce it. It wasn't really a bug report. I was just commenting on the two development releases fvwm-2.5.2 and fvwm-2.5.3 since Dominik is rewriting this area it wouldn't make sense to submit a bug report at this time. 2) It looks like the following are not getting execute permission when installed. For instance: sh-2.05b# fvwm-bug sh: /usr/local/bin/fvwm-bug: Permission denied A chmod fixes it. fvwm-bug fvwm-menu-desktop ... Seems unlikely to me that they are installed without a+x. Please do the following: #cd fvwm_installation_dir cd bin/ make uninstall # as root ... I tried the above. Make install works fine but if you make -k install-strip then the problem occurs. This depends on how you start the fvwm executable. If you call it in ~/.xinitrc without redirection to a file, the output will be together with the X output, possibly on your virtual console. Thanks for the info. The above idea does what I want. i.e startx /var/log/win_system_log 21 gives me everything. What I had in mind was the thread on the bash syntax. If a log was running I would have immediately seen /bin/sh: -c: line 1: syntax error near unexpected token `;' and now that I have have the log running I notice that I have a million errors in my fvwm2rc script. Bruce -- 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]
FVWM: Re: 2.5.x questions (Was: i can't run fvwm 2.4)
On 03 Sep 2002 12:02:41 +, Bruce M Beach wrote: 1) I am at this point using 2.5.2 more or less because I have to. I used a very early version of fvmw for years with no problems and then upgraded to xwindows 4.2 which caused significant problems with the mouse-menu interaction. An upgrade to fvwm-2.4.8 did not solve the problems whereas the alpha version fvwm-2.5.2 did. I've used fvwm-2.5.2 for a while now and for my use it works fine. With fvwm-2.5.3 the problems started again. I think your short description (in another thread) is not enough to understand the problem. Please add more details to that message. What is the mouse-menu problem and what to do exactly to reproduce it. 2) It looks like the following are not getting execute permission when installed. For instance: sh-2.05b# fvwm-bug sh: /usr/local/bin/fvwm-bug: Permission denied A chmod fixes it. fvwm-bug fvwm-config fvwm-convert-2.4 fvwm-convert-2.6 fvwm-menu-desktop fvwm-menu-directory fvwm-menu-headlines fvwm-menu-xlock fvwm-perllib Seems unlikely to me that they are installed without a+x. Please do the following: #cd fvwm_installation_dir cd bin/ make uninstall # as root make make install # as root Then send the output of make install and ls -l /usr/local/bin/fvwm-*. 3) I built with the following configure options --enable-debug-msgs --enable-command-log and it builds fine but I don't understand where the messages get piped to. syslogd? an fvwm console? This depends on how you start the fvwm executable. If you call it in ~/.xinitrc without redirection to a file, the output will be together with the X output, possibly on your virtual console. Display managers like xdm/gdm/kdm may redirect the output to a file. I don't think these debugging options are very useful to you, the output is noisy and hides the real error messages that may appear on stderr. 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]
