You'll probably mark this bug as invalid, as it's not my bug and being on x86, I really can't provide any info. http://bugs.gentoo.org/show_bug.cgi?id=293899 http://bugs.freedesktop.org/show_bug.cgi?id=25103 As you may see there, a trivial autoconf test was failing with -maltivec, but even before upstream made a change to do that test with g++, instead of gcc, it was working on x86. That's why I suspect it may be a compiler problem, that poppler upstream simply masked.
Subject: Re: New: A problem with -maltivec Can you attach the preprocessed source for the configure test that is failing? It looks like the context sensitive keywords is causing the header to fail to compile. Sent from my iPhone On Nov 27, 2009, at 11:00 AM, "galtgendo at o2 dot pl" <gcc-bugzilla@gcc.gnu.org > wrote: > You'll probably mark this bug as invalid, > as it's not my bug and being on x86, I really can't > provide any info. > > http://bugs.gentoo.org/show_bug.cgi?id=293899 > http://bugs.freedesktop.org/show_bug.cgi?id=25103 > > As you may see there, a trivial autoconf test was failing > with -maltivec, but even before upstream made a change > to do that test with g++, instead of gcc, it was working on x86. > > That's why I suspect it may be a compiler problem, > that poppler upstream simply masked. > > > -- > Summary: A problem with -maltivec > Product: gcc > Version: 4.4.2 > Status: UNCONFIRMED > Severity: normal > Priority: P3 > Component: c > AssignedTo: unassigned at gcc dot gnu dot org > ReportedBy: galtgendo at o2 dot pl > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42199 >
Created attachment 19452 [details] preprocessed sources Finally I've got a response in the Gentoo bug. Info: Using built-in specs. Target: powerpc-unknown-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.4.2/work/gcc-4.4.2/configure --prefix=/usr --bindir=/usr/powerpc-unknown-linux-gnu/gcc-bin/4.4.2 --includedir=/usr/lib/gcc/powerpc-unknown-linux-gnu/4.4.2/include --datadir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/4.4.2 --mandir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/4.4.2/man --infodir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/4.4.2/info --with-gxx-include-dir=/usr/lib/gcc/powerpc-unknown-linux-gnu/4.4.2/include/g++-v4 --host=powerpc-unknown-linux-gnu --build=powerpc-unknown-linux-gnu --enable-altivec --disable-fixed-point --with-ppl --with-cloog --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-multilib --enable-libmudflap --disable-libssp --enable-libgomp --enable-cld --with-python-dir=/share/gcc-data/powerpc-unknown-linux-gnu/4.4.2/python --disable-libgcj --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.4.2 p1.0' Thread model: posix gcc version 4.4.2 (Gentoo 4.4.2 p1.0) Command line: powerpc-unknown-linux-gnu-gcc \ -std=gnu99 -E -Os -mcpu=G4 -mtune=G4 -maltivec -mabi=altivec -Wall \ conftest.c -o conftest.i
There's new input in a different Gentoo bug: http://bugs.gentoo.org/show_bug.cgi?id=305333 Apparently in certain conditions on ppc, bool is both defined and undefined. Unless you'll see that as bad code on openjpeg side.
(In reply to Rafał Mużyło from comment #3) > There's new input in a different Gentoo bug: > http://bugs.gentoo.org/show_bug.cgi?id=305333 > > Apparently in certain conditions on ppc, > bool is both defined and undefined. > > Unless you'll see that as bad code on openjpeg side. Yeah, bad code on the openjpeg side. Plus it's possible to trigger errors even without -maltivec, so -maltivec is not the problem. Closing.