Re: [ANNOUNCEMENT] Updated: emacs-24.3.93-1 [TEST]

2014-08-20 Thread Peter Hull
On Thu, Aug 21, 2014 at 6:08 AM, Achim Gratz wrote: > Ken Brown writes: >> This is another pretest of the upcoming emacs-24.4, replacing the >> current pretest (24.3.91-1). It includes a workaround for the bug >> reported in It seems to have fixed my original problem with vc integration though I

Re: [ANNOUNCEMENT] Updated: emacs-24.3.93-1 [TEST]

2014-08-20 Thread Achim Gratz
Ken Brown writes: > This is another pretest of the upcoming emacs-24.4, replacing the > current pretest (24.3.91-1). It includes a workaround for the bug > reported in > > https://cygwin.com/ml/cygwin/2014-07/msg00387.html I've ran the new test version for a while now, mostly emacs-w32, but als

Re: Python missing dependency on libuuid-devel?

2014-08-20 Thread Yaakov Selkowitz
On 2014-08-20 19:20, David Rothenberger wrote: Yaakov Selkowitz wrote: I have added libuuid-devel to both python and python3 requires. I think binutils is also required. An strace shows a use of dlltool and python will segfault if it's not installed. Right, of course. Fixed on sourceware.

Re: Python missing dependency on libuuid-devel?

2014-08-20 Thread David Rothenberger
Yaakov Selkowitz wrote: > On 2014-08-20 15:13, David Rothenberger wrote: >> Doing an "import uuid" in python causes a segmentation fault unless >> libuuid-devel is installed. It appears from the strace that something is >> trying to find libuuid.dll.a. Installing libuuid-devel fixes the problem. >

gdb 7.8 consistently fails to run executable - error is "dll path too long"

2014-08-20 Thread DGStevens
I'm unable to use gdb on any c/c++ executables. When I try, gdb issues the message "dll path too long" and fails to start the target executable. I know that I must be doing something stupid, but it's escaping me. The only forum discussion that I could find suggested using mintty, which I am. I

Re: possible problem with "find . -name blah -o -name blah2"

2014-08-20 Thread Andrey Repin
Greetings, ml...@bogusville.us! > using CYGWIN_NT-6.1, bash 4.1.11(2) and find 4.5.12, the following returns > immediately >find . -name \*.cs -o -name \*.h -o -name \*.cpp -exec ls {} \; > pick your favorite for 'ls' $ uname -a CYGWIN_NT-5.1 daemon2 1.7.32s(0.274/5/3) 20140807 16:26:58 i68

Re: Python missing dependency on libuuid-devel?

2014-08-20 Thread Yaakov Selkowitz
On 2014-08-20 15:13, David Rothenberger wrote: Doing an "import uuid" in python causes a segmentation fault unless libuuid-devel is installed. It appears from the strace that something is trying to find libuuid.dll.a. Installing libuuid-devel fixes the problem. You are indeed correct. The stdl

Re: possible problem with "find . -name blah -o -name blah2"

2014-08-20 Thread Georg Nikodym
On Aug 20, 2014, at 16:58 , ml...@bogusville.us wrote: > using CYGWIN_NT-6.1, bash 4.1.11(2) and find 4.5.12, the following returns > immediately > > find . -name \*.cs -o -name \*.h -o -name \*.cpp -exec ls {} \; Not a Cygwin problem. Try: find . \( -name \*.cs -o -name \*.h -o -na

possible problem with "find . -name blah -o -name blah2"

2014-08-20 Thread mlist
using CYGWIN_NT-6.1, bash 4.1.11(2) and find 4.5.12, the following returns immediately find . -name \*.cs -o -name \*.h -o -name \*.cpp -exec ls {} \; pick your favorite for 'ls' this works as expected find . -name \*.cs -o -name \*.h -o -name \*.cpp it's probably not a horrible problem

Python missing dependency on libuuid-devel?

2014-08-20 Thread David Rothenberger
Doing an "import uuid" in python causes a segmentation fault unless libuuid-devel is installed. It appears from the strace that something is trying to find libuuid.dll.a. Installing libuuid-devel fixes the problem. This only happens when x64_64. It works fine with the i686 distribution. -- David