Re: How to get my auto repeat back?

2003-11-23 Thread Harold L Hunt II
Jeff,

You got this version:

http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg6.html

If so, remove all flags that you have added (e.g. -kb, +kb, etc.) 
and stop using your config file if you were not using it before.  I 
think you should be back to normal.

Harold

Jeffrey C Honig wrote:
As happened to many people, the recent changes to the server disabled
the windows autorepeat and left it up to X.
I'm using ``fullscreen'' mode with ``-engine 1'', no XF86Config-4 file
and am unable to get autorepeat to work.
I tried the ``+kb'' argument to Xwin, with and w/o that ``xset r rate
200 40'' says that there is not an extension present for handling rate.
I really miss auto-repeat.  How can I find it again?

Thanks.

Jeff




Re: How to get my auto repeat back?

2003-11-23 Thread Jeffrey C Honig
 You got this version:

 http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg6.html

 If so, remove all flags that you have added (e.g. -kb, +kb, etc.)
 and stop using your config file if you were not using it before. I
 think you should be back to normal.

Already have it.  I've removed all keyboard related options.  And I have
never installed a config file.  Still no auto-repeat.  :-(

My arguments to Xwin are:

 -clipboard -fullscreen -emulate3buttons -nowinkill -unixkill -engine 1


Thanks.

Jeff

-- 
Jeffrey C. Honig [EMAIL PROTECTED]
http://www.honig.net/jch
GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml


Re: How to get my auto repeat back?

2003-11-23 Thread Harold L Hunt II
Okay, now try with -kb.

Harold

Jeffrey C Honig wrote:
You got this version:


http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg6.html


If so, remove all flags that you have added (e.g. -kb, +kb, etc.)
and stop using your config file if you were not using it before. I
think you should be back to normal.


Already have it.  I've removed all keyboard related options.  And I have
never installed a config file.  Still no auto-repeat.  :-(
My arguments to Xwin are:

 -clipboard -fullscreen -emulate3buttons -nowinkill -unixkill -engine 1

Thanks.

Jeff




Re: How to get my auto repeat back?

2003-11-23 Thread Harold L Hunt II
Jeff,

Also, please run the following from a Cygwin bash prompt and send in the 
resulting cygcheck.out fiel (it may take a minute or two to finish running):

cygcheck -c  cygcheck.out 21

Harold



Re: How to get my auto repeat back?

2003-11-23 Thread Harold L Hunt II
Igor Pechtchanski wrote:

On Sun, 23 Nov 2003, Harold L Hunt II wrote:


Jeff,

Also, please run the following from a Cygwin bash prompt and send in the
resulting cygcheck.out fiel (it may take a minute or two to finish running):
cygcheck -c  cygcheck.out 21

Harold


Harold,

The above is the right command if you want to make sure all the files from
all the installed packages are present.  If all you want are the installed
package versions, you should use cygcheck -cd (or cygcheck
--check-setup --dump-only).
Igor,

In this case I do want to actually check if all files are present.

Harold



Re: How to get my auto repeat back?

2003-11-23 Thread Igor Pechtchanski
On Sun, 23 Nov 2003, Harold L Hunt II wrote:

 Igor Pechtchanski wrote:

  On Sun, 23 Nov 2003, Harold L Hunt II wrote:
 
 Jeff,
 
 Also, please run the following from a Cygwin bash prompt and send in the
 resulting cygcheck.out fiel (it may take a minute or two to finish running):
 
 cygcheck -c  cygcheck.out 21
 
 Harold
 
 
  Harold,
 
  The above is the right command if you want to make sure all the files from
  all the installed packages are present.  If all you want are the installed
  package versions, you should use cygcheck -cd (or cygcheck
  --check-setup --dump-only).

 Igor,

 In this case I do want to actually check if all files are present.

 Harold

Sure, just thought I'd get that info into the archives.  BTW, two notes
about the above functionality: (a) some packages, notably apache, will
show up as incomplete due to a directory rename in the postinstall script,
so it's probably better to specify exactly which packages you'd like to
check, and (b) cygcheck will not check whether the files are the same as
in the distribution tarball, just whether they are present.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster.  -- Patrick Naughton


Re: FW: I've given up on XF86, can' t make my AltGr keys work

2003-11-23 Thread Alexander Gottwald
Benjamin Riefenstahl wrote:

  If someone could donate an old sparc or HP-UX machine I'd be willing
  to debug the problems with xdmcp, fonts and keyboardlayouts with
  those machines.

 Wouldn't it be enough to get a temporary SSH account on a Sparc
 machine to reproduce this and debug the X server side?

For the testing I need a machine where I have full (root) access. Maybe the
yearly our-university-sells-old-hardware-auction has some HP-UX boxes.

Anyway, such a sparc or HP-UX would be a nice donation *g*

bye
ago
-- 
 [EMAIL PROTECTED]
 http://www.gotti.org   ICQ: 126018723


Re:DDD 3.3.8 segmentation error, related to Motif?

2003-11-23 Thread Fred Ma
On Fri, 21 Nov 2003 Brian Ford ford at vss dot fsi dot com wrote:
 
 On Fri, 21 Nov 2003 [EMAIL PROTECTED] wrote:
 
   bt08pm: /usr/X11R6/include/Xm/  ddd --lesstif-version 93
 Warning: This DDD requires a Motif 2.1 library (using Motif
  -1617156.-609)
 
 Could you post cygcheck `type ddd`?
 
   bt08pm: /usr/bin/  ddd --configuration
 GNU DDD 3.3.8 (i686-pc-cygwin)
 Copyright (C) 1995-1999 Technische Universität Braunschweig, Germany.
 Copyright (C) 1999-2001 Universität Passau, Germany.
 Copyright (C) 2001 Universität des Saarlandes, Germany.
 
 Compiled with GCC 3.2 20020927 (prerelease)
 
 Why not the current Cygwin gcc?

I'm having similar problems trying to build ddd-3.3.8 immediately
after update cygwin (1.5.5-1) and all components.  This includes
lesstif 0.93.91-4, Xfree86-lib-compat 4.3.0-2, and XFree86-prog
4.3.0-2.  The last two are what comes up on a search for libXt in
Cygwin's Setup Package Search.  The configure output also
claims  Motif...libraries in default path, headers in default
path.

The reason gcc-3.2 is used is because the most recent (I believe
it's 3.3.x) causes fatal link errors during the make step.  The
suspected cause that I've read is that some cygwin components are
built with gcc-3.2.

The exact error happens when I run make check:

   make[1]: Entering directory `/home/fmadmin/INSTROOT/ddd-3.3.8/ddd'
   MALLOC_CHECK_=2 \
   DDD_HOME=./.. \
   XUSERFILESEARCHPATH=%N XAPPLRESDIR=. \
   ./ddd.exe  cxxtest.exe
   Warning: This DDD requires a Motif 2.1 library (using Motif -6281.-729)
   Continue at own risk.

   Internal error (Segmentation fault).

   Oops!  You have found a bug in DDD.

   If you can reproduce this bug, please send a bug report
   to [EMAIL PROTECTED], giving a subject like

   DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault' signal

I've attached cycheck -cvs output.  Thanks for any suggestions
of what further things to try.

Fred
-- 
Fred Ma
Dept. of Electronics, Carleton University
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6Cygwin Package Information
Last downloaded files to: C:\WINNT\Profiles\Administrator\Desktop
Last downloaded files from: http://mirrors.rcn.net/pub/sourceware/cygwin

Package VersionStatus
_update-info-dir00223-1OK
a2ps4.13-1 OK
ash 20031007-1 OK
base-files  2.6-1  OK
base-passwd 1.1-1  OK
bash2.05b-16   OK
binutils20030901-1 OK
bzip2   1.0.2-5OK
clear   1.0-1  OK
cron3.0.1-11   OK
crypt   1.1-1  OK
cvs 1.11.6-3   OK
cygipc  2.02-1 OK
cygrunsrv   0.96-2 OK
cygutils1.2.2-1OK
cygwin  1.5.5-1OK
cygwin-doc  1.3-6  OK
diffutils   2.8.4-1OK
ed  0.2-1  OK
editrights  1.01-1 OK
enscript1.6.3-3OK
expat   1.95.6-2   OK
fileutils   4.1-2  OK
findutils   4.1.7-4OK
fontconfig  2.2.0-1OK
freetype2   2.1.5-1OK
gawk3.1.3-4OK
gcc 3.2-3  OK
gcc-g++ 3.3.1-3OK
gcc-mingw-core  20031020-1 OK
gcc-mingw-g++   20031020-1 OK
gdb 20030919-1 OK
gdbm1.8.3-7OK
gettext 0.12.1-3   OK
ghostscript 7.05-2 OK
ghostscript-base7.05-2 OK
ghostscript-x11 7.05-2 OK
gnugo   3.4-1  OK
grep2.5-1  OK
groff   1.18.1-2   OK
gzip1.3.5-1OK
jpeg6b-11  OK
keychain1.9-1  OK
less381-1  OK
lesstif 0.93.91-4  OK
libbz2_11.0.2-5OK
libcharset1 1.9.1-3OK
libdb3.13.1.17-2   OK
libdb4.14.1.25-1   OK
libfontconfig-devel 2.2.0-1OK
libfontconfig1  2.2.0-1OK
libfreetype2-devel  2.1.5-1OK
libfreetype26   2.1.5-1OK
libgdbm 1.8.0-5OK
libgdbm-devel   1.8.3-7OK
libgdbm31.8.3-3OK
libgdbm41.8.3-7OK
libgettextpo0   0.12.1-3   OK
libiconv2   1.9.1-3OK
libintl

DDD needs a porter [Was: DDD 3.3.8 segmentation error, related to Motif?]

2003-11-23 Thread Harold L Hunt II
Fred,

Fred Ma wrote:
On Fri, 21 Nov 2003 Brian Ford ford at vss dot fsi dot com wrote:

On Fri, 21 Nov 2003 [EMAIL PROTECTED] wrote:

bt08pm: /usr/X11R6/include/Xm/  ddd --lesstif-version 93
  Warning: This DDD requires a Motif 2.1 library (using Motif
-1617156.-609)
Could you post cygcheck `type ddd`?


bt08pm: /usr/bin/  ddd --configuration
  GNU DDD 3.3.8 (i686-pc-cygwin)
  Copyright (C) 1995-1999 Technische Universität Braunschweig, Germany.
  Copyright (C) 1999-2001 Universität Passau, Germany.
  Copyright (C) 2001 Universität des Saarlandes, Germany.
  Compiled with GCC 3.2 20020927 (prerelease)
Why not the current Cygwin gcc?


I'm having similar problems trying to build ddd-3.3.8 immediately
after update cygwin (1.5.5-1) and all components.  This includes
lesstif 0.93.91-4, Xfree86-lib-compat 4.3.0-2, and XFree86-prog
4.3.0-2.  The last two are what comes up on a search for libXt in
Cygwin's Setup Package Search.  The configure output also
claims  Motif...libraries in default path, headers in default
path.
XFree86-prog-4.3.0-2 is ancient.  XFree86-prog-4.3.0-12 is the current 
release:

http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg5.html

libXt refers to the static Xt library; the new shared Xt library isn't 
called libXt, so you won't find it in a package search for the new 
versions.  It is best if you just run setup.exe and let it automatically 
select packages that have new versions.

With that being said, if you are successfully compiling ddd and still 
have the same problem, then you have proven that the problem has nothing 
to do with the shared Xt library, since your are linking against the 
static Xt library that is distributed with XFree86-prog-4.3.0-2.

The reason gcc-3.2 is used is because the most recent (I believe
it's 3.3.x) causes fatal link errors during the make step.  The
suspected cause that I've read is that some cygwin components are
built with gcc-3.2.
The exact error happens when I run make check:

   make[1]: Entering directory `/home/fmadmin/INSTROOT/ddd-3.3.8/ddd'
   MALLOC_CHECK_=2 \
   DDD_HOME=./.. \
   XUSERFILESEARCHPATH=%N XAPPLRESDIR=. \
   ./ddd.exe  cxxtest.exe
   Warning: This DDD requires a Motif 2.1 library (using Motif -6281.-729)
   Continue at own risk.
   Internal error (Segmentation fault).

   Oops!  You have found a bug in DDD.

   If you can reproduce this bug, please send a bug report
   to [EMAIL PROTECTED], giving a subject like
I said before that there appear to be flags that tell ddd that it is 
being compiled and linked against LessTif instead of Motif.  Either 
these flags don't exist (as the emails that I found suggest), or you 
guys aren't trying them if they do exist.  If they do exist, then that 
should at least get you closer to a working ddd.

I have now realized something that should have been said from the start:

DDD needs a porter

Somebody needs to take it upon themself to port DDD and make appropriate 
fixes to make it work on Cygwin/X.  This has not been done to date, as 
far as I can recall, and it is likely to need to be done before ddd will 
just work.  I don't see a lot happening with DDD until someone steps 
forward to port it properly.

We can all continue to offer tips, but I don't think we are going to get 
anywhere.

Harold



Re: Updated: XFree86-xserv-4.3.0-24

2003-11-23 Thread Takuma Murakami
Dear Harold and Alexander,

Thank you for working on my stupid change.
I noticed a problem with it.

When -kb option is set, winconfig.c:417 should flag
g_winInfo.xkb.disable field.  However, it is enclosed in
the condition (kbd != NULL) at line 387 so it won't be
executed if no primary keyboard is specified.

Therefore Windows autorepeat is still disabled no
matter whether XKB is disabled or not.

If my observation is right, could you fix it?

Takuma Murakami ([EMAIL PROTECTED])