Re: pack bitmap woes on Windows

2014-02-13 Thread Johannes Sixt
Am 2/12/2014 17:48, schrieb Jeff King: > On Wed, Feb 12, 2014 at 03:49:24PM +0100, Erik Faye-Lund wrote: > >> It seems the author of a201c20b41a2f0725977bcb89a2a66135d776ba2 >> assumes __BYTE_ORDER was guaranteed to always be defined, probably >> fooled by the following check: >> >> #if !defined(_

Re: pack bitmap woes on Windows

2014-02-12 Thread Jeff King
On Wed, Feb 12, 2014 at 03:49:24PM +0100, Erik Faye-Lund wrote: > It seems the author of a201c20b41a2f0725977bcb89a2a66135d776ba2 > assumes __BYTE_ORDER was guaranteed to always be defined, probably > fooled by the following check: > > #if !defined(__BYTE_ORDER) > # error "Cannot determine endian

Re: pack bitmap woes on Windows

2014-02-12 Thread Erik Faye-Lund
On Wed, Feb 12, 2014 at 3:22 PM, Erik Faye-Lund wrote: > On Wed, Feb 12, 2014 at 3:09 PM, Duy Nguyen wrote: >> On Wed, Feb 12, 2014 at 8:23 PM, David Kastrup wrote: >>> Johannes Sixt writes: >>> Am 2/12/2014 13:55, schrieb David Kastrup: > Johannes Sixt writes: > >> Running te

Re: pack bitmap woes on Windows

2014-02-12 Thread Erik Faye-Lund
On Wed, Feb 12, 2014 at 3:09 PM, Duy Nguyen wrote: > On Wed, Feb 12, 2014 at 8:23 PM, David Kastrup wrote: >> Johannes Sixt writes: >> >>> Am 2/12/2014 13:55, schrieb David Kastrup: Johannes Sixt writes: > Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with >>

Re: pack bitmap woes on Windows

2014-02-12 Thread Duy Nguyen
On Wed, Feb 12, 2014 at 8:23 PM, David Kastrup wrote: > Johannes Sixt writes: > >> Am 2/12/2014 13:55, schrieb David Kastrup: >>> Johannes Sixt writes: >>> Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with the following symptoms. I haven't followed the topic. Hav

Re: pack bitmap woes on Windows

2014-02-12 Thread David Kastrup
Johannes Sixt writes: > Am 2/12/2014 13:55, schrieb David Kastrup: >> Johannes Sixt writes: >> >>> Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with >>> the following symptoms. I haven't followed the topic. Have there been >>> patches floating that addressed the problem i

Re: pack bitmap woes on Windows

2014-02-12 Thread Johannes Sixt
Am 2/12/2014 13:55, schrieb David Kastrup: > Johannes Sixt writes: > >> Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with >> the following symptoms. I haven't followed the topic. Have there been >> patches floating that addressed the problem in one way or another? >> >> (gd

Re: pack bitmap woes on Windows

2014-02-12 Thread David Kastrup
Johannes Sixt writes: > Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with > the following symptoms. I haven't followed the topic. Have there been > patches floating that addressed the problem in one way or another? > > (gdb) run > Starting program: D:\Src\mingw-git\t\trash

Re: pack bitmap woes on Windows

2014-02-12 Thread Johannes Sixt
Am 2/12/2014 12:56, schrieb Erik Faye-Lund: > On Wed, Feb 12, 2014 at 8:27 AM, Johannes Sixt wrote: >> Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with >> the following symptoms. I haven't followed the topic. Have there been >> patches floating that addressed the problem in

Re: pack bitmap woes on Windows

2014-02-12 Thread Erik Faye-Lund
On Wed, Feb 12, 2014 at 8:27 AM, Johannes Sixt wrote: > Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with > the following symptoms. I haven't followed the topic. Have there been > patches floating that addressed the problem in one way or another? > > (gdb) run > Starting pro

pack bitmap woes on Windows

2014-02-11 Thread Johannes Sixt
Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with the following symptoms. I haven't followed the topic. Have there been patches floating that addressed the problem in one way or another? (gdb) run Starting program: D:\Src\mingw-git\t\trash directory.t5310-pack-bitmaps/..\..