Re: Bug#806208: src:gegl: FTBFS on sparc64, tools/introspect segfaults

2016-06-04 Thread John Paul Adrian Glaubitz
On 06/04/2016 05:53 PM, Patrick Baggett wrote: > Yeah, the memcpy with a word will probably be wrong due to endian issues when > it is stored because dst[3] would be written in the first byte, but they are > assuming that dst[3] is the last byte, given that they do OR with 0xff << 24, > i.e.

Re: Bug#806208: src:gegl: FTBFS on sparc64, tools/introspect segfaults

2016-06-04 Thread Patrick Baggett
On Saturday, June 4, 2016, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> wrote: > On 06/03/2016 11:49 PM, John Paul Adrian Glaubitz wrote: > > So, maybe we're lucky and just the above patch will be enough :). > > > > Will build gegl now to verify this. > > And, indeed, gegl now builds

Re: Bug#806208: src:gegl: FTBFS on sparc64, tools/introspect segfaults

2016-06-04 Thread John Paul Adrian Glaubitz
On 06/03/2016 11:49 PM, John Paul Adrian Glaubitz wrote: > So, maybe we're lucky and just the above patch will be enough :). > > Will build gegl now to verify this. And, indeed, gegl now builds fine on sparc64 [1]. Note the comments in the upstream bug tracker though [2] where it is suggested to