Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined

2019-10-17 Thread Olly Betts
On Fri, Oct 18, 2019 at 07:47:01AM +1300, Olly Betts wrote: > That helped, but qhull_a.h is also included elsewhere without this > workaround which caused my upload to FTBFS on ppc64el. I've extended > the patch to cover that case too and uploaded again. My second upload built successfully on

Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined

2019-10-17 Thread Olly Betts
On Thu, Oct 17, 2019 at 04:52:58PM +1300, Olly Betts wrote: > Aha! wxWidgets "helpfully" defines __POWERPC__ for us on ppc64el, but > to an empty value. Then 3depict has a workaround to define it to 1 if > it is defined, because that empty value breaks Qhull. > > This bug has been open 7 days

Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined

2019-10-16 Thread Olly Betts
On Wed, Oct 16, 2019 at 11:30:47AM +0200, Thierry fa...@linux.ibm.com wrote: > I've personally always used __powerpc__ . > Here is my reference, very useful for all arch related defines : > https://wiki.debian.org/ArchitectureSpecificsMemo That page documents what's defined by GCC on Debian, but

Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined

2019-10-16 Thread Olly Betts
Control: tags -1 + pending On Thu, Oct 17, 2019 at 04:12:35PM +1300, Olly Betts wrote: > And why does this only cause an error on one architecture? I downloaded > and compared the headers in the amd64 and ppc64el libqhull-dev packages > and they're identical. If neither __MWERKS__ nor

Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined

2019-10-16 Thread Thierry fa...@linux.ibm.com
Hello I've personally always used __powerpc__ . Here is my reference, very useful for all arch related defines : https://wiki.debian.org/ArchitectureSpecificsMemo Cheers Thierry I've Cc:-ed tille as his was the most recent upload. Let me know if you'd like me to NMU with a

Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined

2019-10-12 Thread Olly Betts
Control: tag -1 + ftbfs Control: severity -1 serious Raising severity because this is a FTBFS on a release architecture where the package has previously built. On Fri, Oct 11, 2019 at 01:01:13PM +0200, Thierry fa...@linux.ibm.com wrote: > Changing on file side is not enough as there a couple of

Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined

2019-10-11 Thread Thierry fa...@linux.ibm.com
Changing on file side is not enough as there a couple of file impacted > g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/freetype2 -I/usr/include/libpng16 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security --std=gnu++11

Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined

2019-10-10 Thread Thierry fa...@linux.ibm.com
Package: 3depict Version 0.0.22-1 Severity: normal The error when compiling on ppc64el: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/freetype2 -I/usr/include/libpng16 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security