Re: Cygwin: texi2dvi stumbles over texinfo.tex

2006-05-24 Thread Ralf Wildenhues
Hi Karl, * Karl Berry wrote on Wed, May 24, 2006 at 10:03:39PM CEST: > > Ralf, what is the output if you run > tex \\end > etex \\end > pdfetex \\end See typescript, attached. > This shows that texi2dvi is invoking etex. > This shows that mktexfmt is invoking pdfetex to build etex.fmt. >

Re: Cygwin, gdb and SEH [was RE: 1.5.19: changes have broken Qt3]

2006-05-24 Thread clayne
On Wed, May 24, 2006 at 07:06:32PM +0100, Dave Korn wrote: > YES, THERE IS A WAY! > > WHAT IS MORE YOU HAVE ALREADY HAD IT EXPLAINED TO YOU A DOZEN TIMES IN THIS > THREAD! > > THE WAY IS TO USE AN UP-TO-DATE GDB! BTW: Myself, I had just updated to CVS gdb. Currently it looks like SIGINT

cvs emacs

2006-05-24 Thread djh
Has anyone out there been successfull in finding out how to build the latest cvs emacs with the cygwin 5.19.4? I was building emacs with cygwin's x-windows with the following configuration: ./configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --exec-prefix= --with-jp

Re: slow share = slow scripts?

2006-05-24 Thread Larry Hall (Cygwin)
mwoehlke wrote: I'm trying to run some scripts off of a slow network share, and it takes *forever* in Cygwin (it's OK in Interix). Looking at an strace (attached) via 'sort -n' shows a LOT of time being spent in read(), apparently just after (caused by?) an fstat(), which means this feels lik

RE: slow share = slow scripts?

2006-05-24 Thread Gary R. Van Sickle
> From: mwoehlke > > I'm trying to run some scripts off of a slow network share, > and it takes > *forever* in Cygwin (it's OK in Interix). > > Looking at an strace (attached) via 'sort -n' shows a LOT of > time being spent in read(), apparently just after (caused > by?) an fstat(), which mean

RE: No postnews or other Usenet news utilities?

2006-05-24 Thread Bruce Wehr
Let me begin by saying - WOW - this is the LAST type of response I expected. Let me continue by addressing each of your points. > LIAR. You cannot claim that every single usenet reader in > the entire world is interested in Pokemon. You are just > projecting your own personal selfish intere

RE: 1.5.19: Problem with ssh

2006-05-24 Thread Harig, Mark
> -Original Message- > From: Eric Surjawinata [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 24, 2006 4:33 PM > To: Harig, Mark > Subject: Re: 1.5.19: Problem with ssh > > Actually, you are correct. When I typed exit, I am back in the > original session. I guess the login process was s

RE: 1.5.19: Problem with ssh

2006-05-24 Thread Harig, Mark
> -Original Message- > From: Eric Surjawinata [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 24, 2006 4:19 PM > To: Harig, Mark > Cc: cygwin@cygwin.com > Subject: Re: 1.5.19: Problem with ssh > > Hi, > sorry for the implicitness of the message: > 1. Yes, I redirected all output to th

Re: 1.5.19: Problem with ssh

2006-05-24 Thread Eric Surjawinata
Hi, sorry for the implicitness of the message: 1. Yes, I redirected all output to the approp passwd and group file 2. The end of the verbose session throws me back to the bash prompt. no error message that I can detect On 5/24/06, Harig, Mark <[EMAIL PROTECTED]> wrote: > -Original Message---

Re: python: update soon?

2006-05-24 Thread Yaakov S (Cygwin Ports)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jason Tishler wrote: > AFAICT, Cygwin Python uses the normal Python layout. > > On Cygwin, we have: > > $ ls /usr/lib/python2.4/config > Makefile Setup.config config.c install-sh makesetup > Setup Setup.local confi

RE: 1.5.19: Problem with ssh

2006-05-24 Thread Harig, Mark
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Eric Surjawinata > Sent: Wednesday, May 24, 2006 3:50 PM > To: cygwin@cygwin.com > Subject: 1.5.19: Problem with ssh > > Hi, > > I have problems ssh-ing to a cygwin installed on Windows xp. I know > t

RE: Cygwin: texi2dvi stumbles over texinfo.tex (was: failed checks for automake 1.9.6)

2006-05-24 Thread Karl Berry
Ok, you got me curious. How does TeX know what application wrote the file if it's not "to do with" the contents of that file? Sorry, I was referring to the one-line source file \input texinfo @bye As for the .fmt file, yes, it surely records whether tex, etex, pdfetex, etc., was used t

1.5.19: Problem with ssh

2006-05-24 Thread Eric Surjawinata
Hi, I have problems ssh-ing to a cygwin installed on Windows xp. I know this is an old issue, however I scoured all the past issues with this and have not found a solution that worked for me (short of finding an older cygwin release and re-installing). Basically I installed Cygwin 1.5.19 and don

Re: Cygwin: texi2dvi stumbles over texinfo.tex

2006-05-24 Thread Ralf Wildenhues
Hi Dave, * Dave Korn wrote on Tue, May 23, 2006 at 03:41:51PM CEST: > On 23 May 2006 13:13, Ralf Wildenhues wrote: > > [ As per cygwin-L tradition, I am replying only to the lists; Ralf, if you see > this and Karl does not, please feel free to forward it. ] I'm sure Karl reads bug-texinfo; he ma

Cygwin, gdb and SEH [was RE: 1.5.19: changes have broken Qt3]

2006-05-24 Thread Dave Korn
On 24 May 2006 17:13, Ralf Habacker wrote: > Brian Dessent schrieb: >> Ralf Habacker wrote: >> >> And yes, it used to be that gdb was too dumb to recognise that these >> faults in IsBadReadPtr were not actual faults, and it would print them >> as spurious SIGSEGVs, just as it currently does for "

RE: No postnews or other Usenet news utilities?

2006-05-24 Thread Dave Korn
On 24 May 2006 18:38, Bruce Wehr wrote: > First, a little background. I am currently selling some rare Pokemon cards > on eBay ... this is an item that has universal appeal. LIAR. You cannot claim that every single usenet reader in the entire world is interested in Pokemon. You are just pr

No postnews or other Usenet news utilities?

2006-05-24 Thread Bruce Wehr
Hello, Though I am an experienced Unix user (and former admin), I am a relatively new Cygwin user, so this may be a newbie question. I swear I did my due diligence, and am surprised this issue has not been raised in the mailing list archives. (At least, not that I could find.) First, a little

Problems with cygwin, "expect" and ssh

2006-05-24 Thread Stepp, Charles
I have found some interesting behavior regarding the cygwin expect/ssh problem. I used the little expect script That Corinna created. It seemed to not see the prompt for the password from the spawned ssh, so it just timed out. But, when I redirect the stderr to /dev/null, it behaves correctly. Perh

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread Ralf Habacker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Dessent schrieb: > Ralf Habacker wrote: > > And yes, it used to be that gdb was too dumb to recognise that these > faults in IsBadReadPtr were not actual faults, and it would print them > as spurious SIGSEGVs, just as it currently does for "myfa

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread Ralf Habacker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf Habacker schrieb: > Hi all, > > If this would be my project I would add such unit test cases as far as > possible. Because pthread-win32 is also hosted on sources.redhat.com it > may be possible to relicense the test application to cygwin easier

Re: rsh with command hangs, rlogin works

2006-05-24 Thread Lars Björnfot
Andrew DeFaria wrote: > You created? By hand. Or did you use ssh-host-config. Perhaps the sshd user you created was for privilege separation? I used ssh-host-config. You're right about sshd too. > If Local System account is toggle then you are using SYSTEM. Checked, it's SYSTEM. >Local:grep -e

RE: ld terminated with signal 11 [seg fault]

2006-05-24 Thread Dave Korn
On 23 May 2006 23:22, Michael Williamson wrote: > The linker crashes when I try to compile the > camera software LinuxDevKit.tar for SBIG cameras: > > g++ -I . -L . -Wall -o testapp testmain.cpp > csbigcam.cpp > -csbingimg.cpp -lsbigudrv > collect2: ld terminated with signal 11 [Seg

RE: export arrays from cygwin ksh

2006-05-24 Thread Dave Korn
On 24 May 2006 09:24, Thorsten Kampe wrote: > * mwoehlke (2006-05-23 16:37 +) >> It does seem like this doesn't work - at least, not how I would expect >> it to - on bash (either on Cygwin or on Linux). Maybe you should try ksh >> on Cygwin. > > He said he did. Read the subject of this thread

Re: 1.15.19 dlopen() dies with no dlerror()

2006-05-24 Thread Larry Hall (Cygwin)
Jim Kleckner wrote: Larry Hall (Cygwin) wrote: Jim Kleckner wrote: Larry Hall (Cygwin) wrote: Jim Kleckner wrote: Jim Kleckner wrote: Michael McKerns wrote: Yes, yes... I've not given you enough information... ... See: http://cygwin.com/cygwin-ug-net/dll.html http://cygwin.com/faq.html

Re: export arrays from cygwin ksh

2006-05-24 Thread mwoehlke
Thorsten Kampe wrote: * mwoehlke (2006-05-23 16:37 +) It does seem like this doesn't work - at least, not how I would expect it to - on bash (either on Cygwin or on Linux). Maybe you should try ksh on Cygwin. He said he did. Read the subject of this thread. Sorry, my apologies... (Maybe

Re: Visibility of Samba shares after ssh login

2006-05-24 Thread mwoehlke
, also TOFU reformatted... Guenter wrote: mwoehlke wrote: Guenter Bachler wrote: I started the ssh-server on the windows client in order to log-on to a Linux maschine and vice verse. On the Windows client several SAMBA shares have been mapped and correctly displayed with the 'mount' command i

Re: incorrect time stamps (ls)?

2006-05-24 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Lester Ingber on 5/23/2006 11:01 PM: > Sorry, the attachment wasn't in the last email. > > I am seeing date stamps at future dates: > 21:48:21 @lester:/cygdrive/d/Diagoran% ls -l > total 1676 > dr-x-- 8 ingber None 0 Apr 22 200

RE: 1.5.19: changes have broken Qt3

2006-05-24 Thread Dave Korn
On 24 May 2006 13:19, Ralf Habacker wrote: > This breakpoint is never reached (at least in released gdb) and makes it > hard to debug cygwin's threading stuff, probably impossible in this area. How many times do you have to be told? The last released gdb is known to not cope with this. IT IS

RE: 1.5.19: changes have broken Qt3

2006-05-24 Thread Dave Korn
On 24 May 2006 13:07, [EMAIL PROTECTED] wrote: > On Wed, May 24, 2006 at 11:40:58AM +0100, Dave Korn wrote: >>> Actually, is this really a fault in gdb? Cygwin is throwing a SIGSEGV >>> signal, correct? GDB does what it's told, stops on SIGSEGV by default. >>> >>> -cl >> >> But it doesn't inte

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread Ralf Habacker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Dessent schrieb: > Ralf Habacker wrote: > >> There is no segfault, but it does not work as expected e.g. >> pthread_mutexattr_init() does not fill the pthread_mutexattr_t struct >> given as parameter. > > How does it not work? The testcase run

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread Brian Dessent
[EMAIL PROTECTED] wrote: > Actually, is this really a fault in gdb? Cygwin is throwing a SIGSEGV signal, > correct? GDB does what it's told, stops on SIGSEGV by default. Not really. In cases where it is checking parameters or otherwise expects to dereference an invalid pointer, Cygwin installs a

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread clayne
On Wed, May 24, 2006 at 11:40:58AM +0100, Dave Korn wrote: > > Actually, is this really a fault in gdb? Cygwin is throwing a SIGSEGV > > signal, correct? GDB does what it's told, stops on SIGSEGV by default. > > > > -cl > > But it doesn't interact properly with cygwin's exception handling -> si

Re: Re: Java program under cygwin?

2006-05-24 Thread Peter Mueller
Hi Charli and Jim, thanks a lot for your advice! > An X-server provides a means for client programs (the Java app in > question) to "draw" on the display. I use the CygWin/X server all the > time to do just what you are wanting to do. Look at the second link > down on the cygwin home page ( ht

RE: 1.5.19: changes have broken Qt3

2006-05-24 Thread Dave Korn
On 24 May 2006 11:05, [EMAIL PROTECTED] wrote: > On Wed, May 24, 2006 at 01:49:53AM -0700, Brian Dessent wrote: >> Sigh. We've been through this ad nauseum in the archives. This is how >> it's supposed to work, there's nothing wrong here. Gdb doesn't know any >> better though, and reports it as

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread clayne
On Wed, May 24, 2006 at 01:49:53AM -0700, Brian Dessent wrote: > Sigh. We've been through this ad nauseum in the archives. This is how > it's supposed to work, there's nothing wrong here. Gdb doesn't know any > better though, and reports it as a SIGSEGV, when it is not. Did you not > notice tha

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread Brian Dessent
Ralf Habacker wrote: > There is no segfault, but it does not work as expected e.g. > pthread_mutexattr_init() does not fill the pthread_mutexattr_t struct > given as parameter. How does it not work? The testcase runs fine for me with no assertion failures, neither from a prompt nor in (CVS) gdb.

Re: Handling special characters (\/:*?"<>|) gracefully

2006-05-24 Thread Brian Dessent
mwoehlke wrote: > (Speaking of case sensitivity, is it a Windows limitation that Cygwin > can't do this? I'm pretty sure it isn't an NTFS limitation, as Interix > has true case-sensitivity.) As I understand it, the win32 API preserves case but is not case sensitive. The native API is both, so in

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread Ralf Habacker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Dessent schrieb: > Ralf Habacker wrote: > >> Running this testcase results in an internal exception in >> pthread_mutexattr_init() >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x610b1005 in pthread_mutexattr_init (attr=0x404040)

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread Ralf Habacker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christopher Faylor schrieb: > On Tue, May 23, 2006 at 09:20:28PM +0200, Ralf Habacker wrote: >> your right, hope the above mentioned stuff help for this. > > Ralf, > You have the test case. You have the source code. You've already > provided a patch

Re: 1.5.19: changes have broken Qt3

2006-05-24 Thread Brian Dessent
Ralf Habacker wrote: > Running this testcase results in an internal exception in > pthread_mutexattr_init() > > Program received signal SIGSEGV, Segmentation fault. > 0x610b1005 in pthread_mutexattr_init (attr=0x404040) at > ../../../../src/winsup/cygwin/thread.cc:129 > 129 if ((*object)->m

Re: export arrays from cygwin ksh

2006-05-24 Thread Thorsten Kampe
* mwoehlke (2006-05-23 16:37 +) > It does seem like this doesn't work - at least, not how I would expect > it to - on bash (either on Cygwin or on Linux). Maybe you should try ksh > on Cygwin. He said he did. Read the subject of this thread. -- Unsubscribe info: http://cygwin.com/ml/#