Hi Andreas, Sounds like my report was missing some info - sorry about that. When we compile it stops with message cannot convert ‘bool’ to ‘__vector?=(4) bool =?UTF-8?Q?int’ in assignment
Searching for that I found a couple of occurences and mainly bug gcc.gnu.org/bugzilla/show_bug.cgi?id=58241 which is named *Bug 58241* <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58241> - [PPC/Altivec] altivec.h inclusion in -std=c++98..11 causes bool to be redefined This bug reports that building with -std=gnu++11 does not fail. So I checked that this is also true with our package. Trying other workaround like #undef bool around #include <altivec.h> doesn't work because it is not implicitely specified in the code, so I haven't find how to do it right.now. However I don't know what changing -std= value implies. Is that better ? Thanks On 21/02/2019 18:03, Andreas Tille wrote: > Control: tags -1 help moreinfo > > Hi Thierry, > > thanks for your bug report. > > On Wed, Feb 20, 2019 at 03:46:51PM +0100, Thierry fa...@linux.ibm.com wrote: >> Package: libhmsbeagle >> Version: 3.1.2+dfsg-3 >> Severity: important >> Tags: sid buster ppc64el >> >> Hello, >> >> Compilation on ppc64el fails with following message >> >> Apparently this is a known issue mentioned in >> https://urldefense.proofpoint.com/v2/url?u=https-3A__gcc.gnu.org_bugzilla_show-5Fbug.cgi-3Fid-3D58241&d=DwIBAg&c=jf_iaSHvJObTbx-siA1ZOg&r=h7r4xiDzcYRFJGiSxqE59fVCroGM6UiP7RqRnP6bOQ0&m=FR0XpCBnzfw_4lfBTNopdxf3_8e_dYP-_liOlNGRIvM&s=vr7mnBtA0Vvjf1xuGZl1cF9ykJ1t1cqe_XVR-3L6Y_U&e= >> >> I have tested that cusing -std=gnu+11 get rid of that problem. > I admit I do not understand what exactly you did. I've seen in > configure.ac > > AM_CXXFLAGS="$AM_CXXFLAGS -std=c++11" > > is set. Do you want to say that this option should be removed for > ppc64el? > > Kind regards > > Andreas. > -- Thierry Fauck @ fr.ibm.com
