bzr problem

2013-07-10 Thread Katsumi Yamaoka
Hi, Recently /usr/bin/bzr doesn't work well. For the Emacs trunk, those two commands achieve the purpose even if issuing a warning: $ bzr update $ bzr commit -m "Bla bla" Usually a warning is like: 0 [main] python2.7 1264 child_info_fork::abort: address space needed by 'math.dll' (0x80) is

Re: svn_load_dirs not in subversion-tools-1.8.0-1

2013-07-10 Thread David Rothenberger
David Stacey wrote: > I've just noticed that the perl script 'svn_load_dirs' is not in > subversion-tools-1.8.0 [1]. It is still in the 'contrib' section of the > svn-1.8.0 tag [2]. I used this script quite a bit with svn-1.7.x - > please could you reinstate 'svn_load_dirs' if at all possible. >

svn_load_dirs not in subversion-tools-1.8.0-1

2013-07-10 Thread David Stacey
I've just noticed that the perl script 'svn_load_dirs' is not in subversion-tools-1.8.0 [1]. It is still in the 'contrib' section of the svn-1.8.0 tag [2]. I used this script quite a bit with svn-1.7.x - please could you reinstate 'svn_load_dirs' if at all possible. Many thanks in advance, D

Re: emacs problem

2013-07-10 Thread Christopher Faylor
On Wed, Jul 10, 2013 at 05:54:55PM -0400, Ken Brown wrote: >On 7/10/2013 5:10 PM, Christopher Faylor wrote: >> On Wed, Jul 10, 2013 at 04:55:38PM -0400, Christopher Faylor wrote: >>> On Wed, Jul 10, 2013 at 02:54:59PM -0400, Ken Brown wrote: On 7/10/2013 2:07 PM, J. David Boyd wrote: > >>>

Re: i686-w64-mingw32-gcc 4.7.3: ignores __attribute__((packed)), regression?

2013-07-10 Thread JonY
On 7/11/2013 06:28, JonY wrote: > On 7/11/2013 06:12, Christian Franke wrote: >> >> If #pragma pack(1) is used instead, it works as expected also with >> i686-w64-mingw32-gcc 4.7.3. >> >> (Upstream?) bug ? >> > > Likely, there are no cygwin specific patches applied for it, please > check with gcc-

Re: i686-w64-mingw32-gcc 4.7.3: ignores __attribute__((packed)), regression?

2013-07-10 Thread JonY
On 7/11/2013 06:12, Christian Franke wrote: > > If #pragma pack(1) is used instead, it works as expected also with > i686-w64-mingw32-gcc 4.7.3. > > (Upstream?) bug ? > Likely, there are no cygwin specific patches applied for it, please check with gcc-help. Thanks. signature.asc Descripti

i686-w64-mingw32-gcc 4.7.3: ignores __attribute__((packed)), regression?

2013-07-10 Thread Christian Franke
The new MinGW-w64 4.7.3 gcc apparently ignores __attribute__((packed)). Cygwin's gcc 4.7.3 and older MinGW-w64 4.5.3 work as expected. Testcase: $ cat packed.c struct packed { char a; short b; } __attribute__((packed)); int size = sizeof(struct packed); $ i686-w64-mingw32-gcc --version i686-

Re: emacs problem

2013-07-10 Thread Ken Brown
On 7/10/2013 5:10 PM, Christopher Faylor wrote: On Wed, Jul 10, 2013 at 04:55:38PM -0400, Christopher Faylor wrote: On Wed, Jul 10, 2013 at 02:54:59PM -0400, Ken Brown wrote: On 7/10/2013 2:07 PM, J. David Boyd wrote: I'm starting to see this error quite a bit in the terminal window I started

Re: emacs problem

2013-07-10 Thread Christopher Faylor
On Wed, Jul 10, 2013 at 04:55:38PM -0400, Christopher Faylor wrote: >On Wed, Jul 10, 2013 at 02:54:59PM -0400, Ken Brown wrote: >>On 7/10/2013 2:07 PM, J. David Boyd wrote: >>> >>> I'm starting to see this error quite a bit in the terminal window I started >>> emacs from: >>> >>> 0 [main] emacs-X11

Re: test-driver: line 95: Segmentation fault

2013-07-10 Thread Christopher Faylor
On Wed, Jul 10, 2013 at 09:14:39PM +0200, Vasiliy wrote: >Help needed: whenever I run 'make check' I'm experiencing the same >kind or error: >copying 'test-driver' from... to... upon (auto)configure phase, then, >when checking: >test-driver: line 95: Segmentation fault > >It's likely due to some m

Re: emacs problem

2013-07-10 Thread Christopher Faylor
On Wed, Jul 10, 2013 at 02:54:59PM -0400, Ken Brown wrote: >On 7/10/2013 2:07 PM, J. David Boyd wrote: >> >> I'm starting to see this error quite a bit in the terminal window I started >> emacs from: >> >> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error >> in >> forked

Re: emacs problem

2013-07-10 Thread J. David Boyd
Ken Brown writes: > On 7/10/2013 3:07 PM, J. David Boyd wrote: >> Ken Brown writes: >> >>> On 7/10/2013 2:07 PM, J. David Boyd wrote: I'm starting to see this error quite a bit in the terminal window I started emacs from: 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emac

Re: emacs problem

2013-07-10 Thread Ken Brown
On 7/10/2013 3:07 PM, J. David Boyd wrote: Ken Brown writes: On 7/10/2013 2:07 PM, J. David Boyd wrote: I'm starting to see this error quite a bit in the terminal window I started emacs from: 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in forked process - fai

test-driver: line 95: Segmentation fault

2013-07-10 Thread Vasiliy
Help needed: whenever I run 'make check' I'm experiencing the same kind or error: copying 'test-driver' from... to... upon (auto)configure phase, then, when checking: test-driver: line 95: Segmentation fault It's likely due to some mis-compiled binary on my system. How to track it down? -- Probl

Re: emacs problem

2013-07-10 Thread J. David Boyd
Ken Brown writes: > On 7/10/2013 2:07 PM, J. David Boyd wrote: >> >> I'm starting to see this error quite a bit in the terminal window I started >> emacs from: >> >> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error >> in >> forked process - failed to create new win32 s

Re: emacs problem

2013-07-10 Thread Ken Brown
On 7/10/2013 2:07 PM, J. David Boyd wrote: I'm starting to see this error quite a bit in the terminal window I started emacs from: 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in forked process - failed to create new win32 semaphore, Win32 error 87 Have you trie

emacs problem

2013-07-10 Thread J. David Boyd
I'm starting to see this error quite a bit in the terminal window I started emacs from: 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in forked process - failed to create new win32 semaphore, Win32 error 87 It seems to take an indeterminate amount of time before it

mingw64-i686-gcc packages are in a strange state - don't use until all clear

2013-07-10 Thread Christopher Faylor
On Wed, Jul 10, 2013 at 05:52:56PM +0800, JonY wrote: >On 7/10/2013 06:35, Angelo Graziosi wrote: >> Setup.exe has updates (4.5.3 ==> 4.7.3) for mingw64-i686-gcc-core but >> not for other language (fortran, g++ etc.). >> >> Beside this, it wants install mingw64-i686-gcc-debuginfo.. Usually >> *deb

no output from GNUTLS package

2013-07-10 Thread Vasiliy
Hello, I could not get any output from 'gnutls' Cygwin64 package. Could somebody invoke it as follows: gnutls-cli - GnuTLS client or any other example. Compiled from the sources it passes many tests, but still no luck, very strange, indeed. Thank you in advance. Best regards, Vasiliy -- Prob

Re: Something is wrong in setup.ini? [mingw64-i686]

2013-07-10 Thread JonY
On 7/10/2013 17:52, JonY wrote: > On 7/10/2013 06:35, Angelo Graziosi wrote: >> Setup.exe has updates (4.5.3 ==> 4.7.3) for mingw64-i686-gcc-core but >> not for other language (fortran, g++ etc.). >> >> Beside this, it wants install mingw64-i686-gcc-debuginfo.. Usually >> *debuginfo packages are op

TEMP_FAILURE_RETRY macro missing

2013-07-10 Thread Fedin Pavel
Hello! My cross-compiling activity has discovered that TEMP_FAILURE_RETRY() macro is often used, but missing in our includes. GNU code of this macro is below: --- cut --- # define TEMP_FAILURE_RETRY(expression) \ (__extension__ \ ({ long int __result; \ do __result = (long int) (exp

Re: Something is wrong in setup.ini? [mingw64-i686]

2013-07-10 Thread JonY
On 7/10/2013 06:35, Angelo Graziosi wrote: > Setup.exe has updates (4.5.3 ==> 4.7.3) for mingw64-i686-gcc-core but > not for other language (fortran, g++ etc.). > > Beside this, it wants install mingw64-i686-gcc-debuginfo.. Usually > *debuginfo packages are optional not mandatory.. Or not? > It