Re: Cygwin pathconf() query filesystem kernel data? Re: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Tue, Aug 22, 2023 at 12:07 AM Brian Inglis wrote: > > On 2023-08-21 06:03, Martin Wege via Cygwin wrote: > > On Sat, Aug 19, 2023 at 7:50 PM Brian Inglis wrote: > >> > >> On 2023-08-18 07:09, Martin Wege via Cygwin wrote: > >>> On Fri, Aug 18, 2023 at 10:44 AM Corinna Vinschen via Cygwin > >>>

Re: Cygwin pathconf() query filesystem kernel data? Re: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On 2023-08-21 06:03, Martin Wege via Cygwin wrote: On Sat, Aug 19, 2023 at 7:50 PM Brian Inglis wrote: On 2023-08-18 07:09, Martin Wege via Cygwin wrote: On Fri, Aug 18, 2023 at 10:44 AM Corinna Vinschen via Cygwin wrote: On Aug 17 20:49, Martin Wege via Cygwin wrote: On Mon, Aug 14, 2023

Re: Cygwin pathconf() query filesystem kernel data? Re: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Sat, Aug 19, 2023 at 7:50 PM Brian Inglis wrote: > > On 2023-08-18 07:09, Martin Wege via Cygwin wrote: > > On Fri, Aug 18, 2023 at 10:44 AM Corinna Vinschen via Cygwin > > wrote: > >> > >> On Aug 17 20:49, Martin Wege via Cygwin wrote: > >>> On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen v

Re: Cygwin pathconf() query filesystem kernel data? Re: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On 2023-08-18 07:09, Martin Wege via Cygwin wrote: On Fri, Aug 18, 2023 at 10:44 AM Corinna Vinschen via Cygwin wrote: On Aug 17 20:49, Martin Wege via Cygwin wrote: On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen via Cygwin wrote: and the result is the same. Note that Cygwin supports MS

Cygwin pathconf() query filesystem kernel data? Re: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Fri, Aug 18, 2023 at 10:44 AM Corinna Vinschen via Cygwin wrote: > > On Aug 17 20:49, Martin Wege via Cygwin wrote: > > On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen via Cygwin > > wrote: > > > and the result is the same. Note that Cygwin supports MSFT NFSv3 but > > > not CITI NFSv4.1 int

Re: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Aug 17 20:49, Martin Wege via Cygwin wrote: > On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen via Cygwin > wrote: > > and the result is the same. Note that Cygwin supports MSFT NFSv3 but > > not CITI NFSv4.1 internally. No gurantee that Cygwin always does what > > is necessary for that othe

How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen via Cygwin wrote: > and the result is the same. Note that Cygwin supports MSFT NFSv3 but > not CITI NFSv4.1 internally. No gurantee that Cygwin always does what > is necessary for that other NFS. 1. How does Cygwin detect whether something is a

Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Aug 14 21:42, Martin Wege via Cygwin wrote: > Maybe MinGW compat is broken in 3.5.0-0.388.g1a646ad7970a? There's no Mingw compatibility stuff in Cygwin. Mingw are just non-Cygwin binaries, just like any other native Windows tool. Corinna -- Problem reports: https://cygwin.com/problems

Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Aug 14 19:29, Roland Mainz via Cygwin wrote: > On Mon, Aug 14, 2023 at 6:25 PM Roland Mainz wrote: > > On Mon, Aug 14, 2023 at 12:21 PM Corinna Vinschen via Cygwin > > wrote: > > > On Aug 11 13:36, Mainz, Roland via Cygwin wrote: > [snip] > > > > In our case we have a project with both custom

Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Mon, Aug 14, 2023 at 7:30 PM Roland Mainz via Cygwin wrote: > > On Mon, Aug 14, 2023 at 6:25 PM Roland Mainz wrote: > > On Mon, Aug 14, 2023 at 12:21 PM Corinna Vinschen via Cygwin > > wrote: > > > On Aug 11 13:36, Mainz, Roland via Cygwin wrote: > [snip] > > > > In our case we have a project

Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Mon, Aug 14, 2023 at 6:25 PM Roland Mainz wrote: > On Mon, Aug 14, 2023 at 12:21 PM Corinna Vinschen via Cygwin > wrote: > > On Aug 11 13:36, Mainz, Roland via Cygwin wrote: [snip] > > > In our case we have a project with both custom binaries and sources > > > both hosted on the filesystem as

Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Mon, Aug 14, 2023 at 12:21 PM Corinna Vinschen via Cygwin wrote: > > On Aug 11 13:36, Mainz, Roland via Cygwin wrote: > > Hi! > > > > > > > > Cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 has some weird > > path problems with network filesystems on Windows 10. Previous stable > > ve

Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Aug 11 13:36, Mainz, Roland via Cygwin wrote: > Hi! > > > > Cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 has some weird > path problems with network filesystems on Windows 10. Previous stable > version of Cygwin (4.7.x ?) worked fine. 3.4.7 > In our case we have a project with b

Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

Hi! Cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 has some weird path problems with network filesystems on Windows 10. Previous stable version of Cygwin (4.7.x ?) worked fine. In our case we have a project with both custom binaries and sources both hosted on the filesystem as /hom

Re: Problems with cygwin in Windows 10

On 7/22/2015 4:03 AM, Corinna Vinschen wrote: On Jul 21 23:13, Robert McBroom wrote: Having problems with the X interface in Windows 10 (currently build 10240). /bin/startxwin fails with the symptoms in the attached file xwin.txt. The output from cygcheck -cv is also attached. What am I missing?

Re: Problems with cygwin in Windows 10

On Jul 21 23:13, Robert McBroom wrote: > > Having problems with the X interface in Windows 10 (currently build 10240). > /bin/startxwin fails with the symptoms in the attached file xwin.txt. The > output from cygcheck -cv is also attached. What am I missing? > [...] > granp@WIN-xx / > $ ls -la > t

Re: Problems with cygwin in Windows 10

Hi, (This is the same reply I sent when Robert emailed cygwin-xfree rather than cygwin.) On Tue, Jul 21, 2015 at 11:13 PM, Robert McBroom wrote: > > Having problems with the X interface in Windows 10 (currently build 10240). > /bin/startxwin fails with the symptoms in the attached file xwin.txt.

Problems with cygwin in Windows 10

Having problems with the X interface in Windows 10 (currently build 10240). /bin/startxwin fails with the symptoms in the attached file xwin.txt. The output from cygcheck -cv is also attached. What am I missing? $ startxwin Could not load crashreporter dll Welcome to the XWin X Server Vendor

Re: Problems with Cygwin symlinks on a TrueCrypt volume

On Dec 19 15:53, Dr Rainer Woitok wrote: > Corinna, > > On Wed, 11 Dec 2013 14:53:33 +0100 you wrote: > > > ... > > Apart from that, there's a chance that this is a problem not related > > to Cygwin's usage of a transaction on a TrueCrypt volume in the first > > place. Can you try the workaround

Re: Problems with Cygwin symlinks on a TrueCrypt volume

Corinna, On Wed, 11 Dec 2013 14:53:33 +0100 you wrote: > ... > Apart from that, there's a chance that this is a problem not related > to Cygwin's usage of a transaction on a TrueCrypt volume in the first > place. Can you try the workaround from > http://support.microsoft.com/kb/948252 and see if

Re: Problems with Cygwin symlinks on a TrueCrypt volume

On Dec 16 10:33, Dr Rainer Woitok wrote: > Corinna, > > On Fri, 13 Dec 2013 14:06:26 +0100 you wrote: > > > ... > > You just have to put the released Cygwin 1.7.27 DLL back in place, > > that's all. I assume you copied it somewhere else for the time being? > > Just copy it back into place and, i

Re: Problems with Cygwin symlinks on a TrueCrypt volume

Corinna, On Fri, 13 Dec 2013 14:06:26 +0100 you wrote: > ... > You just have to put the released Cygwin 1.7.27 DLL back in place, > that's all. I assume you copied it somewhere else for the time being? > Just copy it back into place and, if that was not the solution, copy the > snapshot DLL over

Re: Problems with Cygwin symlinks on a TrueCrypt volume

On Dec 13 13:47, Dr Rainer Woitok wrote: > Corinna, > > On Wed, 11 Dec 2013 14:53:33 +0100 you wrote: > > > ... > > I created a new snapshot with this patch. Please give the latest > > snapshot from http://cygwin.com/snapshots/ a try and report back. > > First time ever I installed a Cygwin

Re: Problems with Cygwin symlinks on a TrueCrypt volume

Corinna, On Wed, 11 Dec 2013 14:53:33 +0100 you wrote: > ... > I created a new snapshot with this patch. Please give the latest > snapshot from http://cygwin.com/snapshots/ a try and report back. First time ever I installed a Cygwin snapshot ... but it installed cleanly. More important,

Re: Problems with Cygwin symlinks on a TrueCrypt volume

On Dec 6 17:33, Corinna Vinschen wrote: > On Dec 6 15:18, Dr Rainer Woitok wrote: > > Greetings, > > > > I just happened to stumble over the problem described below. > > > > Additional information: > > > > - Windows Vista, patched this week. > > > > - Cygwin updated this week. > > > >

Re: Problems with Cygwin symlinks on a TrueCrypt volume

On Dec 6 15:18, Dr Rainer Woitok wrote: > Greetings, > > I just happened to stumble over the problem described below. > > Additional information: > > - Windows Vista, patched this week. > > - Cygwin updated this week. > > - TrueCrypt downloaded and installed this week. > [...] > $ cd /g

Problems with Cygwin symlinks on a TrueCrypt volume

Greetings, I just happened to stumble over the problem described below. Additional information: - Windows Vista, patched this week. - Cygwin updated this week. - TrueCrypt downloaded and installed this week. First the normal case using the "C:" partition, where everything runs as expect

Re: I'm having problems with cygwin 1.7 and ACL handling.

On Jul 5 12:02, Mark Lommers wrote: > Hi Corinna, > > Thanks for your tip, it pointed me to the right direction. > > When calling the test now with > > cygdrop -P backup -P restore test.exe > > the test is running fine. > > Is it also possible to drop this privileges by default? No,

Re: I'm having problems with cygwin 1.7 and ACL handling.

don't have to change my scripts which call the test, but can configure it on the system itself. Regards, Mark Re: I'm having problems with cygwin 1.7 and ACL handling. From: Corinna Vinschen To: cygwin at cygwin dot com Date: Mon, 2 Jul 2012 18:04:52 +0200 Subject: Re: I'm havin

Re: I'm having problems with cygwin 1.7 and ACL handling.

, Richard. On Mon, Jul 2, 2012 at 11:56 AM, Mark Lommers wrote: > > Hi, > > I'm having problems with cygwin 1.7 and ACL handling. > > I do some software development and for the software I write I also create > unit tests. Those unit test are run automatically in a c

Re: I'm having problems with cygwin 1.7 and ACL handling.

On Jul 2 17:56, Mark Lommers wrote: > Hi, > > I'm having problems with cygwin 1.7 and ACL handling. > > I do some software development and for the software I write I also create > unit tests. Those unit test are run automatically in a cygwin environment > triggered

I'm having problems with cygwin 1.7 and ACL handling.

Hi, I'm having problems with cygwin 1.7 and ACL handling. I do some software development and for the software I write I also create unit tests. Those unit test are run automatically in a cygwin environment triggered by a build system. Now I'm updating the machines on which the unit

Re: Problems with Cygwin on SSD

On Mar 29 10:28, Roland Schwingel wrote: > Hi... > > Recently I bought an SSD (OCZ Vertex 3 120GB). I hoped to improve > performance together with cygwin. But some strange and unexpected > things happen. > > My Setup: > Dell Optiplex 980. Core i5-760. 4 GB Ram. Windows 7 SP1 64bit. A > 500GB WDC

Problems with Cygwin on SSD

Hi... Recently I bought an SSD (OCZ Vertex 3 120GB). I hoped to improve performance together with cygwin. But some strange and unexpected things happen. My Setup: Dell Optiplex 980. Core i5-760. 4 GB Ram. Windows 7 SP1 64bit. A 500GB WDC WD5000AAKS harddrive and the new SSD. Windows 7 instal

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On 3/8/2011 7:01 AM, Corinna Vinschen wrote: > On Mar 7 20:12, Corinna Vinschen wrote: > I found the problem, or at least I could narrow down the effect. It > occurs only on XP and Server 2003, afaics, on 32 as well as on 64 bit > versions. Hard to explain. For the curious, just have a look int

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

Corinna Vinschen wrote: I applied a patch to CVS and just uploaded a new snapshot to http://cygwin.com/snapshots/ Please give it a try. David, this is for you, too. The problem is fixed for me. Thanks a lot! Ciao, Angelo. -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Mar 7 20:12, Corinna Vinschen wrote: > On Mar 7 18:00, Angelo Graziosi wrote: > > Corinna Vinschen wrote: > > >Ok, I found a simpler testcase. > > > > Thanks for you work and your patience... > > > > >Please do NOT quote raw email addresses. > > > > Usually I remove always that... not this

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On 3/7/2011 2:15 AM, Corinna Vinschen wrote: > On Mar 5 10:08, David Rothenberger wrote: >> On 3/3/2011 9:44 AM, Angelo Graziosi wrote: >>> After I flagged these problems [*], I chose to do a clean reinstall of >>> TeXLive 2010 (TL2010). After installed its packages (> 2000!), TL2010 >>> installat

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Mar 7 18:00, Angelo Graziosi wrote: > Corinna Vinschen wrote: > >Ok, I found a simpler testcase. > > Thanks for you work and your patience... > > >Please do NOT quote raw email addresses. > > Usually I remove always that... not this time. I apologize.. > > ..and, what about David's report (

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

Corinna Vinschen wrote: Ok, I found a simpler testcase. Thanks for you work and your patience... Please do NOT quote raw email addresses. Usually I remove always that... not this time. I apologize.. ..and, what about David's report (*)? I am just curios.. Ciao, Angelo. --- (*) http://cyg

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Mar 7 11:11, Corinna Vinschen wrote: > On Mar 5 15:36, Angelo Graziosi wrote: > > Ken Brown wrote: > > >I'm running Win7 in case that makes a difference. > > > > Here on Win XP SP3, 32 bit. I haven't W7 :( > > > > >Corinna, are there changes in the 20100910 snapshot that could explain > > >

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Mar 5 10:08, David Rothenberger wrote: > On 3/3/2011 9:44 AM, Angelo Graziosi wrote: > > After I flagged these problems [*], I chose to do a clean reinstall of > > TeXLive 2010 (TL2010). After installed its packages (> 2000!), TL2010 > > installation proceeds with its post-install actions, main

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Mar 5 15:36, Angelo Graziosi wrote: > Ken Brown wrote: > >I'm running Win7 in case that makes a difference. > > Here on Win XP SP3, 32 bit. I haven't W7 :( > > >Corinna, are there changes in the 20100910 snapshot that could explain this? > > Anyway it would be a remarkable coincidence that 2

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Mar 5 08:47, Ken Brown wrote: > On 3/5/2011 5:22 AM, Angelo Graziosi wrote: > >Anyway, with a binary testing (only .dll.bz2 of snapshots), I have > >verified that the last snapshot with which the .fmt files get the right > >permissions (-rw-r--r--) is 20100904 snapshot, instead with 20100910 >

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On 3/3/2011 9:44 AM, Angelo Graziosi wrote: > After I flagged these problems [*], I chose to do a clean reinstall of > TeXLive 2010 (TL2010). After installed its packages (> 2000!), TL2010 > installation proceeds with its post-install actions, mainly generating > all format files. The installation

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

Ken Brown wrote: I'm running Win7 in case that makes a difference. Here on Win XP SP3, 32 bit. I haven't W7 :( Corinna, are there changes in the 20100910 snapshot that could explain this? Anyway it would be a remarkable coincidence that 20100910 snapshot ChangeLog says: [...] 2010-09-10

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On 3/5/2011 5:22 AM, Angelo Graziosi wrote: Corinna Vinschen wrote: Since fmtutil-sys is apparently the core of the problem, and given my total lack of knowledge about the Tex/Latex system, is there any simple call to fmtutil-sys with which I can reproduce the problem without having to install t

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

Corinna Vinschen wrote: Since fmtutil-sys is apparently the core of the problem, and given my total lack of knowledge about the Tex/Latex system, is there any simple call to fmtutil-sys with which I can reproduce the problem without having to install texlive? It seems too difficult for me. fmtu

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Fri, Mar 04, 2011 at 07:26:11PM +0100, Angelo Graziosi wrote: >Corinna Vinschen wrote: >> Since fmtutil-sys is apparently the core of the problem, and given >> my total lack of knowledge about the Tex/Latex system, is there any >> simple call to fmtutil-sys with which I can reproduce the problem

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

Corinna Vinschen wrote: Since fmtutil-sys is apparently the core of the problem, and given my total lack of knowledge about the Tex/Latex system, is there any simple call to fmtutil-sys with which I can reproduce the problem without having to install texlive? You are right. I will try... ...no

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Mar 4 17:49, Angelo Graziosi wrote: > Ken Brown wrote: > >I think fmtutil creates the files in a temporary directory (using TMPDIR, > >TEMP, or TMP if they exist) and then mv's them. Could this be your problem? > >What happens if you unset those variables before installing texlive? > > It is

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

Ken Brown wrote: I think fmtutil creates the files in a temporary directory (using TMPDIR, TEMP, or TMP if they exist) and then mv's them. Could this be your problem? What happens if you unset those variables before installing texlive? It is some time that my Cygwin installation does not set

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

Corinna Vinschen wrote: If you see that behaviour as part of a perl script, you should also see that which every other tool, even simple stuff like `echo foo > bar'. Really the perl script, at some time, calls (in a posta install action) 'fmutil-sys --all', which creates the .fmt file with wro

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On 3/3/2011 4:23 PM, Angelo Graziosi wrote: The last steps of installation regard the generation of format file for all users (-rw-r--r-- root root), but with recent snapshots the format file are creted only for root (-rwx-+) (**) : these permissions resemble those created when one installs n

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Mar 3 22:23, Angelo Graziosi wrote: > Corinna Vinschen wrote: > >What about some helpful details which allow to reproduce your problem? > >Like, say, how to get the packages, how you install them, stuff like > >that. You seem to imply that everybody knows how to do that. I don't. > > Sorry,

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

Corinna Vinschen wrote: What about some helpful details which allow to reproduce your problem? Like, say, how to get the packages, how you install them, stuff like that. You seem to imply that everybody knows how to do that. I don't. Sorry, I have omitted details because TL2010 is a full dist

Re: Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

On Mar 3 18:44, Angelo Graziosi wrote: > After I flagged these problems [*], I chose to do a clean reinstall > of TeXLive 2010 (TL2010). After installed its packages (> 2000!), > TL2010 installation proceeds with its post-install actions, mainly > generating all format files. The installation is d

Problems with Cygwin-1.7.8 (or snapshot) and TeXLive 2010

After I flagged these problems [*], I chose to do a clean reinstall of TeXLive 2010 (TL2010). After installed its packages (> 2000!), TL2010 installation proceeds with its post-install actions, mainly generating all format files. The installation is done as 'root' (administrator), but the forma

Re: Unknown problems with cygwin-1.7 install on windows 7 host

On Nov 30 10:57, Rance Hall wrote: > I apologize for the vagueness of this post, but I dont know how to > track this down as the Windows error messages do not help much. > > I have windows 7 professional, and just installed cygwin-1.7 beta. > > As far as I can tell, the installation works and all

Unknown problems with cygwin-1.7 install on windows 7 host

I apologize for the vagueness of this post, but I dont know how to track this down as the Windows error messages do not help much. I have windows 7 professional, and just installed cygwin-1.7 beta. As far as I can tell, the installation works and all is well with the cygwin world. However, the s

Re: tcsh problems with Cygwin on 64-bit Windows Server 2008

On Wed, Jan 07, 2009 at 03:31:32PM +0100, Corinna Vinschen wrote: >This is a problem of the lapack package. Unfortunately the lapack >package is orphaned and nobody volunteered to be the new package >maintainer so far. I've created a new lapack.csh file which should not have this problem and crea

Re: tcsh problems with Cygwin on 64-bit Windows Server 2008

On Jan 5 11:50, Freddy Jensen wrote: > > I just finished setting up my new 64-bit Windows Server 2008 machine. > One of the final things was to install cygwin on the machine so I > could get all the Unix functionality. However, I ran into a problem > when launching the tcsh shell. I got this erro

Re: massive heap problems with cygwin 1.7.0

On Thu, Sep 04, 2008 at 08:14:22AM -0600, Bernd Prager wrote: >Hi, > >I am trying to make use of the UTF wide character support in cygwin 1.7 and >tried to give it a shot. >Until now I am almost unable to do anything because I constantly run into >heap problems, like: > >5 [main] ? (5096) D:\bin\cy

massive heap problems with cygwin 1.7.0

Hi, I am trying to make use of the UTF wide character support in cygwin 1.7 and tried to give it a shot. Until now I am almost unable to do anything because I constantly run into heap problems, like: 5 [main] ? (5096) D:\bin\cygwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 err

Re: Problems with cygwin bash shell under NT Emacs

Will writes > I don't know if there's one specifically for NTEmacs, but gnu.emacs.help > answers NTEmacs questions. Thx for the pointer. Haven't thought about it. -- Rolf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html D

Re: Problems with cygwin bash shell under NT Emacs

Andy writes [snip] > I do run NTemacs with cygwin. I do so becuase for a long time the cyugwin > emaxs was broken and/or horribly slow compared to the NTemacs port, and > requires an X11 server to have a GUI. > > Try running "python -i" to force interactive behaviour - this works for me. Yes,

Re: Problems with cygwin bash shell under NT Emacs

On Mon, 14 Jul 2008 20:18:12 GMT, rolf wrote: > René Berber writes: > > > [snip] >> Just for reference, with XEmacs opening a shell: >> >> sh-3.2$ echo $TERM >> dumb >> sh-3.2$ echo $TERMCAP >> emacs:co#79:tc=unknown: >> sh-3.2$ python >> Python 2.5.1 (r251:54863, May 18 2007, 16:56:43) >> [GCC

Re: Problems with cygwin bash shell under NT Emacs

rolf wrote: > And, it seems I can't find a NTEmacs list alive. Is there one? I don't know if there's one specifically for NTEmacs, but gnu.emacs.help answers NTEmacs questions. -- Will -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/p

Re: Problems with cygwin bash shell under NT Emacs

On Mon, Jul 14, 2008 at 12:38:42PM -0500, Ren? Berber wrote: > But the FAQ seems to endorse NTemacs: > > http://cygwin.com/faq/faq-nochunks.html#faq.using.ntemacs That isn't really endorsing. It is just mentioned because it really is a FAQ. The FAQ entry ends with: Note that all of this ``jus

Re: Problems with cygwin bash shell under NT Emacs

René Berber writes: [snip] > Just for reference, with XEmacs opening a shell: > > sh-3.2$ echo $TERM > dumb > sh-3.2$ echo $TERMCAP > emacs:co#79:tc=unknown: > sh-3.2$ python > Python 2.5.1 (r251:54863, May 18 2007, 16:56:43) > [GCC 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)] on cygwin >

Re: Problems with cygwin bash shell under NT Emacs

rolf wrote: [snip] Couldn't it be, that the Cygwin port of python has something to do with it? The point was that mixing a "native" application with a Cygwin app is probably the problem . Which one has to adapt to the other? You should ask the NTEmacs list, tell them about your TERM and T

Re: Problems with cygwin bash shell under NT Emacs

René wrote: >> I'm running a native win32 version emacs. > [snip] > > Then, why do you ask here? Couldn't it be, that the Cygwin port of python has something to do with it? > You should ask the NTEmacs list, tell them > about your TERM and TERMCAP environment strings, those look like the > real

Re: Problems with cygwin bash shell under NT Emacs

Rolf wrote: I'm running a native win32 version emacs. [snip] Then, why do you ask here? You should ask the NTEmacs list, tell them about your TERM and TERMCAP environment strings, those look like the real cause of the problem. Cygwin has emacs and XEmacs, both work fine. -- René Berber

Re: building perl 5.8.8 (was run-time problems with cygwin-1.5.24-2)

Todd Brunhoff schrieb: * From: Reini Urban * Subject: Re: run-time problems with cygwin-1.5.24-2 Todd Brunhoff schrieb: ...In an effort to see what the problem might be, I focussed on perl (although

Re: building perl 5.8.8 (was run-time problems with cygwin-1.5.24-2)

* From: Reini Urban * Subject: Re: run-time problems with cygwin-1.5.24-2 Todd Brunhoff schrieb: ...In an effort to see what the problem might be, I focussed on perl (although interesting, this info may

Re: run-time problems with cygwin-1.5.24-2

Todd Brunhoff wrote: Problem: after installing cygwin-1.5.24-2, most things work but I've noticed a few things that don't work: perl and subversion (svn). Specifically, the programs do absolutely nothing... Ok, so everyone's view was generally helpful. Cygcheck pointed at two missing dlls, cygc

Re: run-time problems with cygwin-1.5.24-2

* Todd Brunhoff (Sun, 02 Sep 2007 11:48:09 -0700) > Problem: after installing cygwin-1.5.24-2, most things work but I've > noticed a few things that don't work: perl and subversion (svn). > Specifically, the programs do absolutely nothing... command line > arguments are ignored, there is no outp

Re: run-time problems with cygwin-1.5.24-2

Todd Brunhoff schrieb: Problem: after installing cygwin-1.5.24-2, most things work but I've noticed a few things that don't work: perl and subversion (svn). Specifically, the programs do absolutely nothing... command line arguments are ignored, there is no output, and the commands appear to do

RE: run-time problems with cygwin-1.5.24-2

On 02 September 2007 19:48, Todd Brunhoff wrote: > Problem: after installing cygwin-1.5.24-2, most things work but I've > noticed a few things that don't work: perl and subversion (svn). > Specifically, the programs do absolutely nothing... command line > arguments are ignored, there is no output,

run-time problems with cygwin-1.5.24-2

Problem: after installing cygwin-1.5.24-2, most things work but I've noticed a few things that don't work: perl and subversion (svn). Specifically, the programs do absolutely nothing... command line arguments are ignored, there is no output, and the commands appear to do nothing. There are no e

Re: 1.5.22-1: Problems with cygwin binaries execution on Windows 2003

Arseny Klimovsky wrote: Hello! I installed cygwin on my MS Windows 2003 and can't cope with problems during execution any exe file except cygcheck. After every execution I have something like this. Faulting application yes.exe, version 0.0.0.0, faulting module cygwin1.dll, version 1005.22.0

1.5.22-1: Problems with cygwin binaries execution on Windows 2003

Hello! I installed cygwin on my MS Windows 2003 and can't cope with problems during execution any exe file except cygcheck. After every execution I have something like this. Faulting application yes.exe, version 0.0.0.0, faulting module cygwin1.dll, version 1005.22.0.0, fault address 0x3

Problems with cygwin, "expect" and ssh

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: Problems with cygwin cvs over ssh.

On Mar 24 04:03, Charles Wilson wrote: > Eric Blake wrote: > >My experience with cvs-1.11.21-1 is that it loses track of conflicts. In > >other words, in cvs-1.11.17, if I do: > > > >$ cvs up > >C foo > >$ cvs up > >C foo > > > >but in cvs-1.11.21, I get: > >$ cvs up > >C foo > >$ cvs up > >M foo

Re: Problems with cygwin cvs over ssh.

Eric Blake wrote: My experience with cvs-1.11.21-1 is that it loses track of conflicts. In other words, in cvs-1.11.17, if I do: $ cvs up C foo $ cvs up C foo but in cvs-1.11.21, I get: $ cvs up C foo $ cvs up M foo I would much rather see conflicts every time I update, so I haven't done muc

Re: Problems with cygwin cvs over ssh.

> The funny thing is that the > directory in the message *is* created before the commands are even read, > and yet cvs still complains that it can't create it because of ENOENT. I think, that ENOENT is wrong! It should be EEXIST. Perhaps cvs would ignore EEXIST, but now complains about ENOENT. I

Re: Problems with cygwin cvs over ssh.

>> Right. I missed the "." in the original message. The change that >> prompted this behavior seems to be >> . I'm assuming the >> motivation for this patch was to duplicate Linux's behavior (which doesn't >> allow trailing "." in a path pas

Re: Problems with cygwin cvs over ssh.

> > So I guess it's now up to the cvs maintainer to try tracking this down (or > reporting this as a bug upstream). FWIW, I've looked at the sources of > 1.11.17 and didn't see where that "." was added. Did anyone try this with > a test cvs-1.11.21-1? My experience with cvs-1.11.21-1 is that it

Re: Problems with cygwin cvs over ssh.

On Sat, 28 Jan 2006, Corinna Vinschen wrote: > On Jan 27 17:01, Igor Peshansky wrote: > > Ugh, top-posting... Reformatted. > > > > On Fri, 27 Jan 2006, Frank-Michael Moser wrote: > > > > > Igor Peshansky wrote: > > > > > > > The problem is with the CVS server running on Cygwin. CVS in client >

Re: Problems with cygwin cvs over ssh.

On Jan 27 17:01, Igor Peshansky wrote: > Ugh, top-posting... Reformatted. > > On Fri, 27 Jan 2006, Frank-Michael Moser wrote: > > > Igor Peshansky wrote: > > > > > The problem is with the CVS server running on Cygwin. CVS in client > > > mode works just fine. > > > > I have encountered the sam

Re: Problems with cygwin cvs over ssh.

Ugh, top-posting... Reformatted. On Fri, 27 Jan 2006, Frank-Michael Moser wrote: > Igor Peshansky wrote: > > > The problem is with the CVS server running on Cygwin. CVS in client > > mode works just fine. > > I have encountered the same problem, have investigated it a bit and came > out with t

Re: Problems with cygwin cvs over ssh.

I have encountered the same problem, have investigated it a bit and came out with two interesting facts: A) Without changing anything else than replacing cygwin1.dll, using the snaphot cygwin1-20050928.dll works fine while using cygwin1-20050929.dll produces the problem. B) Also without changing

Re: Problems with cygwin cvs over ssh.

On 26/01/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: > > > > Remote CVS server is Solaris, local ssh and Cygwin dll versions are > > latest released. > > Then you have misunderstood the original problem. The problem is with the > CVS server running on Cygwin. CVS in client mode works just fine.

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, René Berber wrote: > Igor Peshansky wrote: > [snip] > > FWIW, I could reproduce the original problem, either with or without > > ":ext:". > > The combination cvs/ssh has no problem : > > $ echo $CVS_RSH > ssh > $ echo $CVSROOT > :ext:[EMAIL PROTECTED]:/export/home0/cvsrep > $

Re: Problems with cygwin cvs over ssh.

Igor Peshansky wrote: [snip] > FWIW, I could reproduce the original problem, either with or without > ":ext:". The combination cvs/ssh has no problem : $ echo $CVS_RSH ssh $ echo $CVSROOT :ext:[EMAIL PROTECTED]:/export/home0/cvsrep $ cvs co junit-test cvs server: Updating junit-test U junit-test/

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, René Berber wrote: > Igor Peshansky wrote: > [snip] > >>From the manual: > >> > >>"If the access method is omitted, then if the repository starts with > >>'/', then :local: is assumed." > >> > >>Try: cvs -d :ext:[EMAIL PROTECTED]:/test-repository co test1 > > > > FWICS, "[EMA

Re: Problems with cygwin cvs over ssh.

Igor Peshansky wrote: [snip] >>From the manual: >> >>"If the access method is omitted, then if the repository starts with >>'/', then :local: is assumed." >> >>Try: cvs -d :ext:[EMAIL PROTECTED]:/test-repository co test1 > > > FWICS, "[EMAIL PROTECTED]" doesn't start with a '/'. "fred" is not i

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, René Berber wrote: > James Courtier-Dutton wrote: > > > CVS_RSH=/bin/ssh > > CVS -d [EMAIL PROTECTED]:/test-repository co test1 > --^^^ > Is this correct? or it was really _cvs_. Both should work unless you use check_case:strict or a shell that does case-sensitive hashing. >

Re: Problems with cygwin cvs over ssh.

James Courtier-Dutton wrote: > CVS_RSH=/bin/ssh > CVS -d [EMAIL PROTECTED]:/test-repository co test1 --^^^ Is this correct? or it was really _cvs_. > ...password > cannot mkdir /tmp/cvs-server1396/. > No such file or directory. > > I am running OpenSSH on a cygwin windows server. > The CVS

Re: Problems with cygwin cvs over ssh.

On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > On 25/01/06, Igor Peshansky xxx wrote: > > On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > > > > > On 25/01/06, Karl-Heinz Wirth <[EMAIL PROTECTED]> wrote: > > > > . Thanks. > > Does anyone

  1   2   3   >