Bug#778376: pkgconfig libgcj.pc link points to non existent file

2015-02-14 Thread Victor Seva
Package: gcj-jdk
Severity: normal
Tags: patch

# dpkg -L gcj-jdk | grep libgcj.pc
/usr/lib/pkgconfig/x86_64-linux-gnu/libgcj.pc
# ls -la /usr/lib/pkgconfig/x86_64-linux-gnu/libgcj.pc
lrwxrwxrwx 1 root root 11 Oct 18 09:03 
/usr/lib/pkgconfig/x86_64-linux-gnu/libgcj.pc -> libgcj15.pc
# ls -la /usr/lib/pkgconfig/x86_64-linux-gnu/libgcj15.pc
ls: cannot access /usr/lib/pkgconfig/x86_64-linux-gnu/libgcj15.pc: No such file 
or directory
# ls -la /usr/lib/x86_64-linux-gnu/pkgconfig/libgcj15.pc
lrwxrwxrwx 1 root root 13 Oct 24 16:49 
/usr/lib/x86_64-linux-gnu/pkgconfig/libgcj15.pc -> libgcj-4.9.pc


Switching from /usr/lib/pkgconfig/x86_64-linux-gnu/ to 
/usr/lib/x86_64-linux-gnu/pkgconfig/
will solve the problem.

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- debian/rules.orig	2015-02-14 10:44:11.0 +0100
+++ debian/rules	2015-02-14 10:43:37.0 +0100
@@ -700,8 +700,8 @@
 	  /usr/share/java/libgcj-$(PV_GCJ).jar /usr/share/java/libgcj.jar
 ifeq ($(with_multiarch_lib),yes)
 	dh_link -pgcj-jdk \
-	  /usr/lib/pkgconfig/$(DEB_HOST_MULTIARCH)/$(LIBGCJ_PC) \
-	  /usr/lib/pkgconfig/$(DEB_HOST_MULTIARCH)/libgcj.pc
+	  /usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/$(LIBGCJ_PC) \
+	  /usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/libgcj.pc
 else
 	dh_link -pgcj-jdk \
 	  /usr/lib/pkgconfig/$(LIBGCJ_PC) /usr/lib/pkgconfig/libgcj.pc


Results for 5.0.0 20150211 (experimental) [trunk revision 220605] (Debian 20150211-1) testsuite on x86_64-pc-kfreebsd-gnu

2015-02-14 Thread Matthias Klose
LAST_UPDATED: Wed Feb 11 02:31:39 UTC 2015 (revision 220605)

Target: x86_64-kfreebsd-gnu
gcc version 5.0.0 20150211 (experimental) [trunk revision 220605] (Debian 
20150211-1) 
Native configuration is x86_64-pc-kfreebsd-gnu

=== g++ tests ===


Running target unix
FAIL: g++.dg/ext/cleanup-10.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-10.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-10.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/cleanup-10.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/cleanup-10.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/cleanup-10.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/cleanup-11.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-11.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-11.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/cleanup-11.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/cleanup-11.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/cleanup-11.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/cleanup-8.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-8.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-8.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/cleanup-8.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/cleanup-8.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/cleanup-8.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/cleanup-9.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-9.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-9.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/cleanup-9.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/cleanup-9.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/cleanup-9.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/sync-4.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/sync-4.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/sync-4.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/sync-4.C  -std=gnu++14 execution test
FAIL: g++.dg/ext/sync-4.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/sync-4.C  -std=gnu++98 execution test
FAIL: g++.dg/guality/pr55665.C   -O2  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O2  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O3 -fomit-frame-pointer  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O3 -fomit-frame-pointer  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O3 -g  line 23 p == 40
FAIL: g++.dg/guality/pr55665.C   -O3 -g  line 23 p == 40
XPASS: g++.dg/tls/thread_local-order2.C  -std=c++11 execution test
XPASS: g++.dg/tls/thread_local-order2.C  -std=c++11 execution test
XPASS: g++.dg/tls/thread_local-order2.C  -std=c++14 execution test
XPASS: g++.dg/tls/thread_local-order2.C  -std=c++14 execution test

=== g++ Summary ===

# of expected passes167058
# of unexpected failures36
# of unexpected successes   4
# of expected failures  530
# of unsupported tests  6700
/build/gcc-snapshot-vSouMS/gcc-snapshot-20150211/build/gcc/testsuite/g++/../../xg++
  version 5.0.0 20150211 (experimental) [trunk revision 220605] (Debian 
20150211-1) 

=== gcc tests ===


Running target unix
FAIL: gcc.dg/cleanup-10.c execution test
FAIL: gcc.dg/cleanup-10.c execution test
FAIL: gcc.dg/cleanup-11.c execution test
FAIL: gcc.dg/cleanup-11.c execution test
FAIL: gcc.dg/cleanup-8.c execution test
FAIL: gcc.dg/cleanup-8.c execution test
FAIL: gcc.dg/cleanup-9.c execution test
FAIL: gcc.dg/cleanup-9.c execution test
FAIL: gcc.dg/graphite/vect-pr43423.c scan-tree-dump-times vect "vectorized 2 
loops" 1
FAIL: gcc.dg/graphite/vect-pr43423.c scan-tree-dump-times vect "vectorized 2 
loops" 1
XPASS: gcc.dg/guality/example.c   -O0  execution test
XPASS: gcc.dg/guality/example.c   -O0  execution test
XPASS: gcc.dg/guality/example.c   -O1  execution test
XPASS: gcc.dg/guality/example.c   -O1  execution test
XPASS: gcc.dg/guality/example.c   -O2  execution test
XPASS: gcc.dg/guality/example.c   -O2  execution test
XPASS: gcc.dg/guality/example.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
XPASS: gcc.dg/guality/example.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
XPASS: gcc.dg/guality/guality.c   -O0  execution test
XPASS: gcc.dg/guality/guality.c   -O0  execution test
XPASS: gcc.dg/guality/guality.c   -O1  execution test
XPASS: gcc.dg/guality/guality.c   -O1  execution test
XPASS: gcc.dg/guality/guality.c   -O2  execution test
XPASS: gcc.dg/guality/guality.c   -O2  execution test
XPASS: gcc.dg/guality/guality.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
XPASS: gcc.dg/guality/guality.c   -O2 -flto -fno-use-linker-plugin 
-flto-partition=none  execution test
XPASS: gcc.dg/guality/guality.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
XPASS: gcc.dg/guality/guality.c   -O2 -flto -fuse-linker-plugin 
-fno-fat-lto-objects  execution test
XPASS: gcc.dg/guality/guality.c   -O3 -fomit-frame-pointer  execution test
XPASS: gcc.dg/guality/guality.c   -O3 -fomit-frame-p

Bug#778436: /usr/share/gcc-5/python/libstdcxx/v6: ImportError: No module named 'printers'

2015-02-14 Thread Jakub Wilk

Package: libstdc++6
Version: 5-20150205-1

$ gdb --batch --quiet --ex 'run >/dev/null' apt-get
Traceback (most recent call last):
 File "/usr/share/gdb/auto-load/usr/lib/i386-linux-gnu/libstdc++.so.6.0.21-gdb.py", 
line 58, in 
   import libstdcxx.v6
 File "/usr/lib/i386-linux-gnu/../../share/gcc-5/python/libstdcxx/v6/__init__.py", 
line 19, in 
   from printers import register_libstdcxx_printers
ImportError: No module named 'printers'
[Inferior 1 (process 6130) exited normally]


This is with gdb_7.8.2-1 (from experimental).


-- System Information:
Debian Release: 8.0
 APT prefers unstable
 APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libstdc++6:i386 depends on:
ii  gcc-5-base 5-20150205-1
ii  libc6  2.19-15
ii  libgcc11:5-20150205-1
ii  multiarch-support  2.19-15

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150214223927.ga1...@jwilk.net



Bug#755295: gcc testsuite on hurd-i386

2015-02-14 Thread Samuel Thibault
Samuel Thibault, le Mon 09 Feb 2015 19:17:14 +0100, a écrit :
> # of unexpected failures124
> 
> To be compared with i386:
> 
> # of unexpected failures94
> 
> The difference is essentially [...] some cleanup-*.c failures

Those and a lot others later in the testsuite seem to be due to
libstdc++ not able to unwind over the signal trampoline on hurd-i386.
Apparently gdb is not either.  That'd be a very good thing to fix :)

Samuel


-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150215011947.gj4...@type.youpi.perso.aquilenet.fr