Re: perl 5.8.0 and spamassasin

Ajay Simha wrote: > > Hi, > > With Perl 5.8.0 and SpamAssassin-2.55 I get: > > BEGIN failed--compilation aborted at > /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin.pm line 62. > Compilation failed in require at /bin/spamassassin line 69. > procmail: Program failure (70) of "spamassassin" > p

[ANNOUNCEMENT] Testversion uploaded: bash-2.05b-10

David Rothenberger writes: > Corinna Vinschen writes: > > Please give it a try, especially if you're using textmode mounts. If > > nobody complains about problems which result from that patch within, > > say, two or three weeks, I'll make this the standard

1.5.0: rxvt copy/paste problems

I'm seeing some weird, new behavior with rxvt under cygwin-1.5.0-1 related to copy/paste and its interaction with the Windows clipboard. All of the weirdness described below goes away when I revert to 1.3.22. I'm running under Win2k Pro SP4. It seems that if I startup rxvt directly from Windows

Re: 1.5.0: rxvt copy/paste problems

u use "tty" in your CYGWIN variable? If not, can you try it? If so, would you mind posting your cygcheck output, or emailing it to me privately, so I can investigate further? -Dave Rolf Campbell writes: > I am unable to reproduce using 1.5.0/Win2000ProSp4 > > David Rothenberge

Anyone trying 1.5.0 for anything other than managed mode?

Christopher Faylor writes: > Can I take the silence on bug reports for anything other than managed > mode as a good sign. I'm still experiencing the problems with copy/paste interaction with the Windows clipboard mentioned in . -Dave

Re: 1.5.0: rxvt copy/paste problems

Christopher Faylor writes: > On Sat, Jul 19, 2003 at 10:57:54AM -0400, Rolf Campbell wrote: > >When I have CYGWIN=tty, I was able to reproduce the same exact problem. > > Sounds like an extremely simple fix then. There is no need to use > CYGWIN=tty if you are using rxvt. Thanks for the wor

Re: cut and paste problem with xemacs Was Re: [ANNOUNCEMENT] Available for test: cygwin-1.5.0-1

Antoine Levy-Lambert writes: > Hi Christopher, Corinna, > > My xemacs is XEmacs 21.4.1.0 "Military Intelligence (Windows)" configured > for `i686-pc.cywin` > > With cygwin 1.3, cut and paste between other applications and Xemacs works. > With cygwin 1.5.0-1, cut and paste between other app

Re: cut and paste problem with xemacs Was Re: [ANNOUNCEMENT] Available for test: cygwin-1.5.0-1

Antoine, Please keep your replies on the list. I set the Reply-To: header; please make sure your mailer honors it. > I have tried your workaround ... and it works for me, much to my surprise > because my XEmacs is a Windows/Cygwin build, not an XWindows/Cygwin build, > and so I do not understand

Questions about building from CVS (was Re: documentation on building the cygwin dll)

Gerrit P. Haase writes: > Try this: > > #!/bin/bash Gerrit, Thanks for the script! I just started building the cygwin DLL from sources last week and this script sure does make it easier. I do have two questions for those that have done it successfully. First, how do you do the update from

1.5.0: Problem with fseeko() after fdopen()

I'm running 1.5.0 with all the latest test packages installed. I recently noticed a problem with the test release of patch and its ability to read from stdin. I started to investigate and have extracted the problematic code from patch into a test program. The program (and patch) use open() to cr

Re: cut and paste problem with xemacs Was Re: [ANNOUNCEMENT] Available for test: cygwin-1.5.0-1

Antoine Levy-Lambert wrote: > > Does anyone have any idea about how this issue (cut and paste between xemacs > running under cygwin 1-5.0-1 and Windows applications). Or even a suggestion on where to start looking? I still think this is related to the rxvt problems. I've done some investigati

Re: cut and paste problem with xemacs Was Re: [ANNOUNCEMENT] Available for test: cygwin-1.5.0-1

Antoine Levy-Lambert wrote: > > > One work-around I've discovered is to start XEmacs from an rxvt > > window instead of directly from bash. That fixes the problem for > > me. I use the following shortcut for starting XEmacs: > > > > start /min c:\cygwin\bin\rxvt -T "start XEmacs" -e > /bin/bas

Re: 1.5.0: Problem with fseeko() after fdopen() (gold star alert)

Christopher Faylor wrote: > [snip] > I've submitted a patch request to fix this to the newlib mailing list > which I expect to fix the problem. It does cause patch to operate > correctly when linked with a new cygwin dll. I'm glad you posted. I was just about to try writing fdopen64 myself. I j

Re: cut and paste problem with xemacs Was Re: [ANNOUNCEMENT] Available for test: cygwin-1.5.0-1

Antoine Levy-Lambert wrote: > > David Rothenberger wrote : > >Any suggestions would be appreciated, even if its just "try looking at > >somefile.c". I don't mind investigation and can go with limited info; > >I'm just out of ideas now. > One ide

Re: Cygwin DLL configuration

Doru Carastan wrote: [snip] > I would like to ask the list how to configure the cygwin DLL to have > 'make install' create a tree similar to the one stored in the binary > distribution tar file: [snip] Gerrit recently posted a script that I've been using for building from CVS. The produces a tree

Re: snap, crackle, popshot (was Re: cut and paste problem with xemacs/rxvt)

Christopher Faylor wrote: > > I'm building a cygwin1-20030726.dll.bz2 snapshot now. It may fix the > cut and paste problem. It (well, cvs HEAD) does for me. > It also may allow console windows running the bash shell to exit > automatically when you logout. Ditto. > It also exports fdopen64

1.5.1: unzip problems with binary files in archive

I'm getting a strange error from unzip when trying to extract an archive that contains binary files. Everything works fine if the archive contains just text files. This problem occurs with the 1.5.1 DLL and the latest test packages for zip and unzip. Everything works fine with 1.3.22. It also w

Re: 1.5.1: unzip problems with binary files in archive

Christopher Faylor wrote: > > On Mon, Jul 28, 2003 at 01:14:53PM -0700, David Rothenberger wrote: > Content-Description: message body text > >I'm getting a strange error from unzip when trying to extract an > >archive that contains binary files. Everything works fine

1.5.1: lseek64 woes (was Re: 1.5.1: unzip problems with binary files in archive)

Charles Wilson writes: > Christopher Faylor wrote: > > I'm getting a strange error from unzip when trying to extract an > archive that contains binary files. Everything works fine if the > archive contains just text files. > >>> > >>>Can't duplicate it. Sorry. > >> > I --can

Re: 1.5.1: lseek64 woes (was Re: 1.5.1: unzip problems with binary files in archive)

Darn it! I forgot to change the disposition on those attachments. Sorry about that, guys. Getting late for me. Dave -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ:

Re: Limit to size of pipe

chris writes: > Hello! > > Further to an earlier message I sent, I now attach an example. This > tries to send a message of a fixed sized down a pipe. Under windows I > can't seem to send much more than 25k down in one go, although I can > send more if I chop it up into sections. Under li

Re: 1.5.1: lseek64 woes (was Re: 1.5.1: unzip problems with binary files in archive)

Christopher Faylor wrote: > > On Mon, Jul 28, 2003 at 11:41:43PM -0700, David Rothenberger wrote: > Content-Description: message body text > >Charles Wilson writes: > > > Christopher Faylor wrote: > > > > > > >>>>I'm getting a strange e

Re: 1.5.1-1 unzip broken

bob sandefur wrote: > > Hi-- > > I went to the exp 1.5.1-1 release because ls -lt was confused on size and > tar didn't work on big files; ls +tar worked fine but unzip was broken; went > back to current and unzip is fine. > Sorry If i shouldn't have reported this to you This was already report

Re: What is the minimum needed to run gtar?

Christopher Faylor writes: > On Fri, Aug 08, 2003 at 09:12:45AM -0700, David Rothenberger wrote: > >David Rothenberger wrote: > >> > >> David Rothenberger writes: > >> > "Biederman, Steve" wrote: > >> > > > >> >

Re: What is the minimum needed to run gtar?

David Rothenberger writes: > "Biederman, Steve" wrote: > > > > I want to allow the users I support to be able to run Cygwin tar on their Windows > > machines. > > These machines have not had any Cygwin installed; they're just bare Windows > &

Re: Help with Cygwin SSH

The command below is forwarding only the command channel for ftp. The fact that you were able to login indicates that the tunnel is operating correctly. Successfully tunnelling normal FTP is difficult and normally requires that you can configure either your client or your server so that you can

Re: Problem with rsh

Check your /etc/passwd file and make sure there is no entry in the password field (the second field). You want something like this: someuser::11150:... and not something like this: someuser:unused_by_nt/2000/xp:11150:... An easy way to check if this is the culprit is to try doing an rlogin. F

Re: Problem with rsh

permissions set to 644. "Pierre A. Humblet" wrote: > > On Fri, Oct 25, 2002 at 03:23:11PM -0700, Andrew DeFaria wrote: > > David Rothenberger wrote: > > > > >Check your /etc/passwd file and make sure there is no entry in the > > >password field (th

Re: Native Xemacs

The XEmacs installer from www.xemacs.org includes a cygwin version and a native Windows version. I think you installed the cygwin version (which is good). Unfortunately, that binary is not compiled with X support. You can recompile XEmacs with X support and native Windows windowing support. It

Re: [Performance Regression] cygwin 1.3.15-2 -> 1.3.16-1

I noticed the same problem while running the SETI@Home client. It only occurred when running bash from the DOS box, not when using rxvt. Also, if I remove tty from the CYGWIN setting (setting back to just ntsec), the DOS box performs fine. Dave Ljubomir Josifovski wrote: > > On Sun, Nov 24, 20

Re: [Performance Regression] cygwin 1.3.15-2 -> 1.3.16-1

Christopher Faylor wrote: > > This should be fixed in the latest snapshot. I'll make a new 1.3.17 > release if I get a consensus that it really is fixed. The new snapshot fixes the problem for me, too. Thanks Chris! Dave -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug r

1.3.18: slow pipe performance when cpu busy

I've noticed slow pipe performance when my CPU is busy running low-priority programs (e.g., SETI@home). For example, if I run: % grep keychain .profile the command completes very fast. However, when I run % cat .profile | grep keychain the command takes 6-7 seconds to complete. However, if

Re: please try the latest snapshot

The latest 1-17 snapshot fixes the pipe problem for me. No other problems detected so far. Thanks! Christopher Faylor wrote: > > The latest snapshot should fix some /etc handling problems (thanks to > ideas and code from Pierre Humblet), like the dreaded BSOD. It may also > solve the "pipes ar

Re: please try the latest snapshot

structions for collecting the information is provided. Dave David Rothenberger wrote: > > The latest 1-17 snapshot fixes the pipe problem for me. No other > problems detected so far. Thanks! > > Christopher Faylor wrote: > > > > The latest snapshot should fix s

Re: Suppress newline under cygwin bash

Randall R Schulz wrote: > > This is csh / tcsh's way of suppressing the terminal newline usually > supplied by the "echo" command. It also documented in the man page to > work with the separate echo executable, "/bin/echo.exe", but it does > not do so for me (for whatever reason). The man page i

Re: regtool freezes on XP (Was: Re: [ANNOUNCEMENT] Updated: cygwin-1.5.6-1)

I think the problem is bash, not regtool. The following script also displays the problem: ---begin script--- #!/bin/sh ls ---end script--- Running the script through /bin/sh makes the problem go away. (I.e., execute "sh -c scriptname.sh" from the Run menu.) Dave Rolf Campbell wrote: When I r

Re: cygwin-1.5.6-1 Vim now broken

Christopher Faylor wrote: On Mon, Jan 19, 2004 at 09:39:19PM -0500, [EMAIL PROTECTED] wrote: I installed the new 1.5.6-1 and rebooted. I then went to edit a file with vim. I changed one line of code and went to save the file. This is what happened: - vi FA_lib.pm 'Vim: Caught deadly signal SEGV Vi

Re: regtool freezes on XP (Was: Re: [ANNOUNCEMENT] Updated: cygwin-1.5.6-1)

Christopher Faylor wrote: On Mon, Jan 19, 2004 at 01:48:52PM -0800, David Rothenberger wrote: I think the problem is bash, not regtool. The following script also displays the problem: ---begin script--- #!/bin/sh ls ---end script--- Does the latest snapshot fix this problem? Yes. Thank you

Re: cygwin-1.5.6-1 Vim now broken

Corinna Vinschen wrote: On Jan 20 07:11, David Rothenberger wrote: Christopher Faylor wrote: Editing files works fine, AFAICT. Vim seems to be dying on exit. I don't know if this will help with this problem, but I had the same issue under Windows XP Pro. The problem occurred with fil

Re: CVS instructions

Frédéric L. W. Meunier wrote: "Once you have the latest sources, "cvs update" will get any changes since your last update." A cvs update from src/ also downloads many other modules (I guess all from http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/?cvsroot=src), not just the changes from a winsup

bash, dircolors, setsid and a stackdump

I've just encountered a very strange problem involving setsid, rxvt, bash and dircolors. I'm using CVS from Thu Jan 22 07:18:16 PST 2004. I have a simple script script.sh: ---begin script--- #!/bin/sh echo foo sleep 10 ---end script--- I have uncommented the dircolors line in the default /etc/p

Re: bash, dircolors, setsid and a stackdump

Rafael Kitover wrote: I would dearly love to know how you get those lovely line numbers in the stackdump :) I used the unstripped DLL from my CVS build and then used addr2line on each function address in the stacktrace, specifying the DLL as the executable. I.e., addr2line -e /bin/cygwin1.dll

ash signal problems with latest CVS

I'm having a problem with signals with the latest CVS DLL and ash. I have a script tst.sh: #!/bin/sh while true; do date sleep 20 done >From a cmd.exe prompt, if I do "bash tst.sh" and then press Ctrl-C, the script terminates. If I do the same with "

Re: ash signal problems with latest CVS

Brian Ford wrote: Are you sure this is the latest CVS? It looks like the same problem fixed here to me: http://www.cygwin.com/ml/cygwin/2004-01/msg01140.html Yes, I'm sure it is the latest CVS. The problem above is fixed in my build, but not the problem I reported. It looks the same, but the sh

Re: ash signal problems with latest CVS

Brian Ford wrote: Incidentally, is there a way to reliably compare two CVS built DLLs from the cygcheck or uname -a output? I don't think so, since both just include the date the DLL was built. FWIW, this problem appears to be fixed by: http://www.cygwin.com/ml/cygwin/2004-01/msg01160.html Concu

Re: Problems with Emacs

Charles Plager wrote: Most of the time I try to start the program (using X) , it launches o.k. But sometimes, the window pops up and it freezes taking all of the cpu (it says "loading ed mode"). Does anybody have any ideas? Has anybody else seen this? Try the latest snapshot. If that do

Re: XEmacs and Windows Fonts

Paul Stodghill wrote: I don't know if it is a 21.4.14 problem or a configuration problem. I believe it is a configuration problem of some sort. I am running a 21.4.14 that I built myself from CVS and did not encounter the problem with fonts. I'm also not seeing it with a 21.4.15 built from CVS.

2004-Feb-17 snapshot change ssh option parsing behavior

Prior to using the 2004-Feb-17 snapshot, the command % ssh somehost /bin/bash --login -c date worked correctly. Now, ssh gives "Unknown cipher type 'date'." The command % ssh somehost -- /bin/bash --login -c date works, but % ssh somehost -- /bin/bash -login -c date fails. The comman

Re: 2004-Feb-17 snapshot change ssh option parsing behavior

Corinna Vinschen wrote: On Feb 17 12:58, David Rothenberger wrote: We're using the latest plain BSD getopt() now. It's permuting the options by default. This was switched off by default in Cygwin so far. Typically you should quote the command you send to the remote host: ssh some

Re: 2004-Feb-17 snapshot change ssh option parsing behavior

Robert Collins wrote: you may find that ssh somehost -- bin/bash --login -c date also works. In fact, I did, and mentioned that in my first email. Unfortunately, I use this with some old Solaris boxes, which require "-login" instead of "--login", and ssh somehost -- /bin/bash -login -c date

Re: 2004-Feb-17 snapshot change ssh option parsing behavior

Corinna Vinschen wrote: On Feb 17 16:46, David Rothenberger wrote: Robert Collins wrote: you may find that ssh somehost -- bin/bash --login -c date also works. In fact, I did, and mentioned that in my first email. Unfortunately, I use this with some old Solaris boxes, which require "-

Re: Control-c not working in rxvt (for exiting jboss server)

Chuck Irvine wrote: When I start Jboss server from rxvt, I cannot exit, that is, shutdown the server, using Control-c. If I start the server from the normal cygwin bash prompt, that is, cywin.bat, control-c shuts down the server. Control-c from rxvt in other contexts does seem to work, for example,

Re: Control-c not working in rxvt (for exiting jboss server)

Chuck Irvine wrote: I'm a little hesitant to go to the latest snapshot since I rely on cygwin for many things. Do you think it is as safe as the current version? I think it's much safer, actually. I've been using the latest snapshot since it was released and believe it to be the best since before

Re: shortcut to start xemacs in bash cygwin window

Edwin Goei wrote: I would like to be able to have a Windows shortcut that will do the equivalent of the following: 1) run cygwin.bat 2) execute "xemacs &" in the cygwin bash window 3) exit the cygwin bash window 4) leaving xemacs running. I would like to start xemacs in this way so I can have

Re: shortcut to start xemacs in bash cygwin window

Edwin Goei wrote: Thanks. I changed my shortcut and it seems to work, but I noticed that the dos window indicates some number of errors from bash, but then quickly goes away. Is there a way for me to keep the window open so I can see what the errors are? I did not have the shortcut set to s

Re: Questions on cygwin filemode in WindowsXP

Yufeng Xiong wrote: 1. What is the '+' in the file mode? I know it has something to do with file permission, after the editing, my web server/PHP does not have permission to open test.php anymore I believe the "+" indicates that there are some Windows permissions that do not map to the Unix-style

Re: Questions on cygwin filemode in WindowsXP

Yufeng Xiong wrote: I'm using WindowsXP @Home, it does not seem to have anything available for changing file permissions from Windows itself, does anybody know how to do it ? You have to turn off "simple file sharing". It's under the View tab of the Folder Options. Search in WinXP help for "simp

2004-Apr-11 snapshot breaks procps

FWIW, procps does not seem to see any processes with the 2004-Apr-11 snapshot. ps still works, but procps returns nothing. Possibly related: /proc//status is not there anymore with the snapshot. Dave -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: htt

Re: xemacs shell problem

ion-type nil) before starting the shell mode. This will cause the shell mode to use pipes instead of ptys. Lement, you may want to try that and see if it changes anything. Dave -- David Rothenbergerspammer? -> [EMAIL PROTECTED] GPG/PGP: 0x7F67E734, C233 365A 25EF 2C5F C8E1 4

Re: Emacs for Cygwin (was: cygwin-mount.el, Using GDB in NTEMACS)

FWIW, there's a true Cygwin port of XEmacs available now (as well as a Windows-native port). See http://www.xemacs.org Jon Cast wrote: > > You wrote: > > > I think that we need a CygEmacs - an emacs that will be compiled > > with the real Cygwin ported gcc (i.e. without the > > -mno-cygwin). >

Re: What is the minimum needed to run gtar?

"Biederman, Steve" wrote: > > I want to allow the users I support to be able to run Cygwin tar on their Windows > machines. > These machines have not had any Cygwin installed; they're just bare Windows machines. > > I provided them tar.exe and cygwin1.dll and assumed that with these, they could

Re: What is the minimum needed to run gtar?

David Rothenberger wrote: > > David Rothenberger writes: > > "Biederman, Steve" wrote: > > > > > > I want to allow the users I support to be able to run Cygwin tar on their > Windows machines. > > > These machines have not had any Cyg

tar and remote machines (was RE: What is the minimum needed to run gtar?)

Biederman, Steve writes: > > (Resuming an earlier discussion ...) > > In my Cygwin environment, I can invoke tar with Windows-style pathnames, > i.e, "tar -cf C:/temp/foo.tar ." My non-Cygwin users can't; for them, the > "C:" is interpreted as a remote machine name and they get "cannot exe

Re: It's a snapshot

Corinna Vinschen wrote: On Thu, Aug 21, 2003 at 10:13:21PM -0400, Christopher Faylor wrote: Tonight's snapshot is nearly 1.5.3-ready. I'd appreciate it if people would test the snapshot and report failures or successes here. Using this snapshot, sshd still eats up all CPU time when running a re

Re: Need help: cron jobs can't access network drives.

Louis-Luc Le Guerrier wrote: Hello, I have tried Universal Name Convention path as well, and I still can't access the network drives, even with UNC paths inside the script ran by 'cron'. The same script invoked manually accesses net drives of course. I have looked at "www.denicomp.com/faq.htm#Q21"

Re: strange cut and paste between windows and xemacs after upgrade to 1.5.3

Thomas Pfaff wrote: After upgrading my cygwin release box from 1.33.2 to 1.5.3 i see a strange cut and paste probleme between xemacs 21.4.13 and windows. Cut and paste from and to windows works as long as xemacs does not fork a child process. After a fork of a shell, gdb or gnuserv the actual

Re: 1.5.3-1: sshd stopped working after update to 3.6.1p2-2

Robert Diamond wrote: I'm running on win2k, latest patches from MS. The system is behind a SMC7004AWBR router, via DSL (SBC). I had no problems getting in via ssh for the past year, but after today's update, I can't get in through the router. I can get in through localhost, and other systems

Re: strange cut and paste between windows and xemacs after upgrade to 1.5.3

Thomas Pfaff wrote: After upgrading my cygwin release box from 1.33.2 to 1.5.3 i see a strange cut and paste probleme between xemacs 21.4.13 and windows. Cut and paste from and to windows works as long as xemacs does not fork a child process. After a fork of a shell, gdb or gnuserv the actual

Re: Need help: cron jobs can't access network drives.

Louis-Luc Le Guerrier wrote: On Tue, 2 Sep 2003, David Rothenberger wrote: Louis-Luc Le Guerrier wrote: Hello, I have tried Universal Name Convention path as well, and I still can't access the network drives, even with UNC paths inside the script ran by 'cron'. The same

1.5.5s: procps error

FWIW, the latest snapshot and the latest CVS both cause a problem with procps that is not present in 1.5.4. -- $ procps Signal 11 caught by ps (procps version 2.0.7). Please send bug reports to <[EMAIL PROTECTED]> --

Re: 1.5.5s: procps error

David Rothenberger writes: > FWIW, the latest snapshot and the latest CVS both cause a problem > with procps that is not present in 1.5.4. > > -- > $ procps > > > Signal 11 caught by ps (procps v

Re: ^Z does not get back to shell prompt in v1.5.4-1 on WinXP

Igor Pechtchanski wrote: On Wed, 17 Sep 2003, Bill McCormick wrote: ... Searching the recent archives. This was not only reported, but also fixed: . Is it fixed? According to the msg, it *will be* fixed. CFG is working on it. No. It *is* fix

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

Yadin Y. Goldschmidt wrote: It is true that making a xemacs.bat file which contains c:\cygwin\usr\X11R6\bin\run.exe /bin/bash -c "/usr/local/bin/i686-pc-cygwin/xemacs" makes XEmacs run correctly under cygwin 1.5.5. (Actually one needs to add a line 'set cygwin=tty ' before that line if one does no

Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.

Triza UK wrote: I have same experience with Cygwin 1.5.5 I updated my Cygwin to 1.5.5 and XEmacs became unusable. Cygwin 1.3.20 works OK. XEmacs I am using is 21.5.5, but this must be a Cygwin bug because I only ungraded Cygwin. The problem starts when I run a subprocess from XEmacs. Good exa

Re: getsockopt broken in cygwin 1.3.6-1

m. This is the first time I've contributed anything to cygwin. I've read the web pages and I think I've included everything required. Please let me know if I've done this incorrectly. Dave Rothenberger [EMAIL PROTECTED] 2001-12-04 David Rothenberger <[EMAIL PROTECTED]>

Re: No longer can compile w/ -mno-cygwin

I had the same problem and discovered that /usr/include/mingw and /usr/lib/mingw were essentially empty. I corrected the problem by re-installing the mingw and mingw-runtime packages (in the Devel group). HTH, Dave "Weber, Neil" wrote: > > I just upgraded my Cygwin installation and the C++ pro

Re: cygwin 1.3.6-3 and xemacs

I've done a little debugging and here's what I've found out. It appears to be a problem/change to the behavior of cygwin_posix_to_win32_path_list(). When this function is called with a path of the form "/cygdrive/z/something", it returns an empty string unless the drive "z" actually exists. Thi

Re: cygwin 1.3.6-3 and xemacs

gdrive" when following symlinks like the ones you described, but it does. Maybe cgf can fix this behavior, too... Dave "Ryan T. Sammartino" wrote: > > On Thu, Dec 06, 2001 at 11:46:43AM -0800, David Rothenberger wrote: > > I've done a little debugging and here

Re: xemacs users -- please try latest cygwin snapshot...

I'm unable to download any snapshots. It appears that all the files in ftp://sources.redhat.com/pub/cygwin/snapshots are actually symlinks to /www/..., and the /www directory doesn't exist (or is not accessible through anonymous login). Anyone else able to grab the snapshot? Dave -- Unsubscrib

latest snapshot fixes xemacs problems

ted so succinctly by > David Rothenberger. > > Since I didn't have an actual test case for the other problem, I > could only take a stab at what it could be, but it's possible that > problem is fixed, too. > > My availability is, again, rather limited in the next day or so

Re: latest snapshot fixes xemacs problems

I am unable to repeat the problems you've described. I tried with the cygwin-inst-20011206.tar.bz2 and with a DLL I compiled myself from the latest CVS sources. The only real differences I can see are that I'm using textmode mounts and my CYGWIN value is a bit different. [mount -s -c /cygdrive]

1.3.6-5: BUG: stat() returns 0 when errno != 0

I've discovered an inconsistency in the way stat() treats windows-style paths (e.g., "z:/foo") and unix-style paths ("/z/foo"). If the drive doesn't exist, stat() returns 0 with a windows path and -1 with a unix path. errno != 0 in both cases. This behavior exists in the latest 1.3.6 dll but no

Re: path problems when logged in through ssh

I had a similar problem with ssh. In my case, I couldn't even log in through ssh because the spawned child process could not find the cygwin DLL. The problem was that my system PATH value was longer than 512 characters. The sshd daemon is supposed to copy its environment for the child process.

Re: path problems when logged in through ssh

Corinna Vinschen wrote: > > On Mon, Dec 17, 2001 at 12:43:37PM -0800, David Rothenberger wrote: > > I had a similar problem with ssh. In my case, I couldn't even log in > > through ssh because the spawned child process could not find the cygwin > > DLL. The pr

Re: path problems when logged in through ssh

08:49:18AM -0800, David Rothenberger wrote: > > I thought there was a limit because the char[] array for the > > environment value in copyEnvironment() was 512. (This is from > > memory, so I may be a little off here.) > > No, you're not off. I just looked into the

Re: Proper "$HOME" setup? (/home or My Documents)

I would use the mount command to mount "My Documents" at /home/crb (after first running mkdir -p /home/crb). That way, you don't need to move anything. Chris Bailey wrote: > > I checked the FAQ but didn't see anything on this (and did some mailing list > searches, but didn't find it, hopefully

Re: 1.5.18: problem with drag and drop using XEmacs

21.4 with support for Windows and XEmacs under Cygwin for a long time. I've always used --with-dragndrop and have never encountered any problems. You could try to download the 21.4 source package and rebuild with that option. Perhaps it will work for you, too. -- David Rothenberger

Re: Call for testing Cygwin snapshot

alhost The command succeeds but opens a console window while the SSH process is running. The console window doesn't open if I start bash first: c:\cygwin\bash -lc '/bin/rxvt -e /bin/bash -li' % ssh localhost The first command doesn't yield a console window with the 2005111

Re: Call for testing Cygwin snapshot

On 12/12/2005 2:32 AM, Corinna Vinschen wrote: > On Dec 8 16:08, David Rothenberger wrote: >> -- >> Problem 2: >> -- >> This is a

Re: Call for testing Cygwin snapshot

On 12/12/2005 1:00 PM, Corinna Vinschen wrote: > On Dec 12 11:59, David Rothenberger wrote: >> On 12/12/2005 2:32 AM, Corinna Vinschen wrote: >> 3. XEmacs will prompt for a command. The prompt will already have >>"grep -n ". Just add (without quotes) "-i

Re: Call for testing Cygwin snapshot (rsync mem use)

mmand: % rsync -avRP --delete --exclude='*~' /usr /etc /sbin /some/dest twice. The second time, the rsync process will consume hundreds of MB of memory. With the 20051110 snapshot, the rsync process stays under 9 MB. -- David Rothenbergerspammer? -> [EMAIL

Re: Call for testing Cygwin snapshot

On 12/8/2005 4:08 PM, David Rothenberger wrote: -- Problem 2: -- This is also with XEmacs. I normally start XEmacs with the following command from a CMD.EXE

Re: Please try a snapshot - final push for 1.5.19 (ssh/cron console windows)

(I restart the services after a new DLL installation through an rxvt/bash session). -- David Rothenbergerspammer? -> [EMAIL PROTECTED] GPG/PGP: 0x92D68FD8, DB7C 5146 1AB0 483A 9D27 DFBA FBB9 E328 92D6 8FD8 Cygwin Configuration Diagnostics Current System Time: Tue Jan 03 09:24:05

Re: services not starting with 20060104 snapshot

a DLL built 20060104 4:00 GMT. The only changes after that are the change for the beep and for managed mounts. -- David Rothenbergerspammer? -> [EMAIL PROTECTED] GPG/PGP: 0x92D68FD8, DB7C 5146 1AB0 483A 9D27 DFBA FBB9 E328 92D6 8FD8 -- Unsubscribe info: http://cygwi

setup crashes trying to install xorg-x11-fnts

ine and setup crashed there, too. Any ideas how to fix this? Or, is there any way I can manually reinstall xorg-x11-fnts so I have a working X11 installation again? -- David Rothenbergerspammer? -> [EMAIL PROTECTED] GPG/PGP: 0x92D68FD8, DB7C 5146 1AB0 483A 9D27 DFBA FBB9 E328

Re: setup crashes trying to install xorg-x11-fnts

On 1/10/2006 8:28 PM, Igor Peshansky wrote: On Tue, 10 Jan 2006, David Rothenberger wrote: Setup is crashing for me (Windows "unexpected error" window) when I try to reinstall xorg-x11-fnts. Tsk, tsk, tsk. Which setup version? Which OS? Which version of xorg-x11-fnts are you

Re: setup crashes trying to install xorg-x11-fnts

On 1/10/2006 10:00 PM, David Rothenberger wrote: On 1/10/2006 8:28 PM, Igor Peshansky wrote: On Tue, 10 Jan 2006, David Rothenberger wrote: Any ideas how to fix this? It would be best if we found why setup doesn't work for you (whatever it does, it shouldn't crash). It could be tr

Re: setup crashes trying to install xorg-x11-fnts

On 1/11/2006 3:14 AM, Dave Korn wrote: David Rothenberger wrote: On 1/10/2006 10:00 PM, David Rothenberger wrote: On 1/10/2006 8:28 PM, Igor Peshansky wrote: On Tue, 10 Jan 2006, David Rothenberger wrote: Any ideas how to fix this? Here's the backtrace. I haven't had a chance

bash 3.1-1 "exec -l" doesn't start login shell

"exec -l" in bash 3.1-1 doesn't seem to start a login shell. This prevents my chere commands from starting a login shell, too. It works in 3.0-14. I'm using a self-built DLL from 20060109 16:00:41. -- David Rothenbergerspammer? -> [EMAIL PROTECTED] GP

Re: bash 3.1-1 "exec -l" doesn't start login shell

m by adding echo "`date` ~/.profile" >> /tmp/dotfile at the top of ~/.profile. When I start a shell with "bash --login", I see the current date/time added to /tmp/dotfile. If I execute "exec -l /bin/bash", no entry is added to /tmp/dotfile with 3.1-1. An en

  1   2   3   4   5   6   7   8   >