Your message dated Mon, 19 Jun 2017 13:31:31 +0200
with message-id
<cabnmvq4oeadu-muzppcr3t1c42ftsxxpiafv9lfwejg9z0y...@mail.gmail.com>
and subject line Re: apertium: FTBFS on powerpcspe
has caused the Debian Bug report #696095,
regarding apertium: FTBFS on powerpcspe
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
696095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apertium
Version: 3.1.0-2
Severity: wishlist
Tags: patch sid upstream
User: debian-powerpc...@breakpoint.cc
Usertags: powerpcspe
Hi,
apertium FTBFS on powerpcspe[1] like this:
[...]
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking Compilation architecture: PPC, i686, x86_64, Other... PowerPC
checking for powerpc-linux-gnuspe-g++... powerpc-linux-gnuspe-g++
checking whether the C++ compiler works... no
configure: error: in `/«PKGBUILDDIR»':
configure: error: C++ compiler cannot create executables
See `config.log' for more details
make: *** [config.status] Error 77
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[...]
Attaching a patch that fixes this by adding -maltivec only on powerpc, but not
on powerpcspe.
Thanks,
Roland
[1] http://wiki.debian.org/PowerPCSPEPort
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.5.0 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Index: apertium-3.1.0/configure.ac
===================================================================
--- apertium-3.1.0.orig/configure.ac 2008-11-05 15:42:48.000000000 +0100
+++ apertium-3.1.0/configure.ac 2012-12-16 19:04:54.421203953 +0100
@@ -61,8 +61,21 @@
if test x$ARCH = xppc
then
AC_MSG_RESULT([PowerPC])
- CFLAGS="$CFLAGS -Wall -ansi -mpowerpc -maltivec -fno-pic -fomit-frame-pointer"
- CXXFLAGS="$CXXFLAGS -Wall -ansi -mpowerpc -maltivec -fno-pic -fomit-frame-pointer"
+ CFLAGS="$CFLAGS -Wall -ansi -mpowerpc -fno-pic -fomit-frame-pointer"
+ CXXFLAGS="$CXXFLAGS -Wall -ansi -mpowerpc -fno-pic -fomit-frame-pointer"
+ AC_COMPILE_IFELSE([
+#if defined(__GNUC__) && (__GNUC__ < 3 || (__GNUC__ == 3 && __GNUC_MINOR__ < 4))
+#error "Need GCC >= 3.4 for sane altivec support"
+#endif
+#include <altivec.h>
+int main () {
+ vector unsigned int v = vec_splat_u32 (1);
+ v = vec_sub (v, v);
+ return 0;
+}], [
+ CFLAGS="$CFLAGS -maltivec"
+ CXXFLAGS="$CXXFLAGS -maltivec"
+],)
else
if test x$ARCH = xi686
then
--- End Message ---
--- Begin Message ---
Package: apertium
Version: 3.3.0
This hasn't been an issue for many years; I suspect since we started using
raw unconfigured sources.
The powerpcspe build passes:
https://buildd.debian.org/status/package.php?p=apertium
-- Tino Didriksen
--- End Message ---
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
