Bug#803039: [PATCH] libffi: enable autoreconf

[Frederic Bonnard]

Source: libffi
Source-Version: 3.2.1-3
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el

--

Hi,
here is a patch to enable autoreconf for libffi as it was not figuring out the
good linker on ppc64el :
---
checking whether the powerpc64le-linux-gnu-gcc linker 
(/usr/powerpc64le-linux-gnu/bin/ld -m elf64ppc) supports shared libraries... no 
---
and it should be ld only.
This was particularly problematic when cross compiling and rebootstrap was 
impacted :
https://jenkins.debian.net/view/All/job/rebootstrap_ppc64el_gcc5/44/console

Thanks,
Fred
diff -Nru libffi-3.2.1/debian/control libffi-3.2.1/debian/control
--- libffi-3.2.1/debian/control	2014-11-18 16:58:51.0 +0100
+++ libffi-3.2.1/debian/control	2015-10-22 10:21:33.0 +0200
@@ -5,7 +5,8 @@
 Build-Depends: debhelper (>= 5),
   g++-multilib [amd64 i386 mips mipsel powerpc ppc64 s390 sparc kfreebsd-amd64],
   dejagnu, lsb-release, texinfo,
-  dpkg-dev (>= 1.16.0~ubuntu4)
+  dpkg-dev (>= 1.16.0~ubuntu4),
+  dh-autoreconf, libltdl-dev
 Standards-Version: 3.9.6
 Section: libs
 
diff -Nru libffi-3.2.1/debian/rules libffi-3.2.1/debian/rules
--- libffi-3.2.1/debian/rules	2014-06-04 15:28:42.0 +0200
+++ libffi-3.2.1/debian/rules	2015-10-26 10:29:11.0 +0100
@@ -39,6 +39,7 @@
 	dh_testdir
 	rm -rf build
 	mkdir -p build
+	dh_autoreconf
 	cd build && ../configure \
 		--host=$(DEB_HOST_GNU_TYPE) \
 		--build=$(DEB_BUILD_GNU_TYPE) \
@@ -75,6 +76,7 @@
 	rm -f stamp-*
 	rm -rf build*
 	rm -f doc/libffi.info
+	dh_autoreconf_clean
 	dh_clean 
 
 install: build

Bug#802838: ada: gnatgcc-5 and gnatmake symlinks

[Ludovic Brenta]

Matthias Klose  writes:
> I've never understood why this link moved to the versioned gnat
> package and didn't stay in the unversioned gnat package. So maybe we
> changed that when preparing the ada cross compiler?
>
> The cross compiler builds shouldn't ship such unversioned links at
> all. I very much would prefer to have these links in the unversioned
> gnat package again.

My first reaction is to agree wholeheartedly but one of Nicolas'
greatest qualities is that he discusses and documents such changes
beforehand:

https://lists.debian.org/debian-ada/2014/04/msg0.html

I think the problem he wanted to solve was to be able to build gnat-x.y
with itself even during the transition period when gnat pointed to an
earlier, or later, on nonexistent, gnat-x'.y'.

Now I'm not sure how such a situation could arise, or how it could
prevent building gnat-x.y.

> Not sure about gnatmake and others. I'm not an gnat developer.  If it
> is possible that the versioned tools can be used on its own, then
> again I would prefer to ship these in the gnat package.

No, the "versioned" tools cannot be used on their own.  We don't want to
require users to type gnatmake-x.y instead of gnatmake; and there is a
whole bunch of user-facing programs that call each other, too, like
gnatls, gprbuild, etc.

--
Ludovic Brenta.

Bug#803109: gcc-5: If compiled with gcc-5, GnuPG classic cannot import certain public keys

[Christian Pietsch]

Package: gcc-5
Version: 5.2.1-22
Severity: normal
Tags: upstream

Dear Maintainer,

I noticed that on Debian testing, I cannot import a certain public key into
gnupg-1.4.19 that I can import on Debian stable. This is how the bug is
triggered:

$ gpg --recv-key 67F41449
gpg: requesting key 67F41449 from hkp server keys.gnupg.net
gpg: DBG: armor-keys-failed (KEY 0x67F41449 BEGIN
) ->0
gpg: DBG: armor-keys-failed (KEY 0x67F41449 END
) ->0
gpg: assuming bad signature from key 67F41449 due to an unknown critical bit
gpg: assuming bad signature from key 67F41449 due to an unknown critical bit
gpg: key 67F41449: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg:   w/o user IDs: 1
$ gpg --list-key 67F41449
gpg: error reading key: public key not found

When I compiled vanilla versions of recent GnuPG classic releases, noting 
changed.
Only after I did `./configure CC=gcc-4.9`, the key could be imported:

$ gpg --recv-key 67F41449
gpg: requesting key 67F41449 from hkp server keys.gnupg.net
gpg: DBG: armor-keys-failed (KEY 0x67F41449 BEGIN
) ->0
gpg: DBG: armor-keys-failed (KEY 0x67F41449 END
) ->0
gpg: key 67F41449: public key "Xxx Yyy " imported
gpg: Total number processed: 1
gpg:   imported: 1  (RSA: 1)
$ gpg --list-key 67F41449 >/dev/null && echo works
works

GnuPG's test suite currently does not catch this bug, i.e. `make check`
succeeds in any case.

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcc-5 depends on:
ii  binutils  2.25.1-7
ii  cpp-5 5.2.1-22
ii  gcc-5-base5.2.1-22
ii  libc6 2.19-22
ii  libcc1-0  5.2.1-22
ii  libgcc-5-dev  5.2.1-22
ii  libgcc1   1:5.2.1-22
ii  libgmp10  2:6.0.0+dfsg-7
ii  libisl13  0.14-2
ii  libmpc3   1.0.3-1
ii  libmpfr4  3.1.3-1
ii  libstdc++65.2.1-22
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages gcc-5 recommends:
ii  libc6-dev  2.19-22

Versions of packages gcc-5 suggests:
pn  gcc-5-doc 
pn  gcc-5-locales 
pn  gcc-5-multilib
pn  libasan2-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx0-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information

Bug#803055: gcj-5-jre-headless: update-alternatives priority is too low: 105 instead of 1050

[Vincent Lefevre]

Package: gcj-5-jre-headless
Version: 5.2.1-22
Severity: normal

One has the following update-alternatives priorities:

xvii:~> update-alternatives --display java
[...]
/usr/bin/gij-4.6 - priority 1046
/usr/bin/gij-4.7 - priority 1047
/usr/bin/gij-4.8 - priority 1048
/usr/bin/gij-4.9 - priority 1049
/usr/bin/gij-5 - priority 105
[...]

105 for the latest version is too low. I suppose that it should be
1050 and the problem is due to out-of-date code in debian/rules.defs,
which assumes that BASE_VERSION has 2 components:

  java_priority = 10$(subst .,,$(BASE_VERSION))

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gcj-5-jre-headless depends on:
ii  gcc-5-base 5.2.1-22
ii  gcj-5-jre-lib  5.2.1-22
ii  libc6  2.19-22
ii  libgcc11:5.2.1-22
ii  libgcj16   5.2.1-22
ii  zlib1g 1:1.2.8.dfsg-2+b1

gcj-5-jre-headless recommends no packages.

Versions of packages gcj-5-jre-headless suggests:
ii  fastjar   2:0.98-6
pn  gcj-5-jdk 
ii  libgcj16-awt  5.2.1-22

-- no debconf information

Results for 4.9.3 (Debian 4.9.3-5) testsuite on i586-pc-gnu

[Matthias Klose]

LAST_UPDATED: Thu Oct 15 13:58:24 UTC 2015 (revision 228843)

Target: i586-gnu
gcc version 4.9.3 (Debian 4.9.3-5) 
Native configuration is i586-pc-gnu

=== g++ tests ===


Running target unix
FAIL: g++.dg/cdce3.C -std=gnu++98 execution test
FAIL: g++.dg/cdce3.C -std=gnu++11 execution test
FAIL: g++.dg/cdce3.C -std=gnu++1y execution test
FAIL: g++.dg/eh/sighandle.C -std=gnu++98 execution test
FAIL: g++.dg/eh/sighandle.C -std=gnu++11 execution test
FAIL: g++.dg/eh/sighandle.C -std=gnu++1y execution test
FAIL: g++.dg/ext/cleanup-10.C -std=gnu++98 execution test
FAIL: g++.dg/ext/cleanup-10.C -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-10.C -std=gnu++1y execution test
FAIL: g++.dg/ext/cleanup-11.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++1y execution test
FAIL: g++.dg/ext/cleanup-8.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++1y execution test
FAIL: g++.dg/ext/cleanup-9.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++1y execution test
FAIL: g++.dg/ext/sync-4.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++1y 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++1y execution test
FAIL: g++.dg/tls/thread_local3.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local3.C -std=gnu++1y execution test
FAIL: g++.dg/tls/thread_local3g.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local3g.C -std=gnu++1y execution test
FAIL: g++.dg/tls/thread_local4.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local4.C -std=gnu++1y execution test
FAIL: g++.dg/tls/thread_local4g.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local4g.C -std=gnu++1y execution test
FAIL: g++.dg/tls/thread_local5.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local5.C -std=gnu++1y execution test
FAIL: g++.dg/tls/thread_local5g.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local5g.C -std=gnu++1y execution test
FAIL: g++.old-deja/g++.law/profile1.C -std=gnu++98 (test for excess errors)
UNRESOLVED: g++.old-deja/g++.law/profile1.C -std=gnu++98 compilation failed to 
produce executable
FAIL: g++.old-deja/g++.law/profile1.C -std=gnu++11 (test for excess errors)
UNRESOLVED: g++.old-deja/g++.law/profile1.C -std=gnu++11 compilation failed to 
produce executable
FAIL: g++.old-deja/g++.law/profile1.C -std=gnu++1y (test for excess errors)
UNRESOLVED: g++.old-deja/g++.law/profile1.C -std=gnu++1y compilation failed to 
produce executable

=== g++ Summary for unix ===

# of expected passes81570
# of unexpected failures36
# of unexpected successes   2
# of expected failures  446
# of unresolved testcases   3
# of unsupported tests  2690

Running target unix/-fstack-protector
FAIL: g++.dg/cdce3.C -std=gnu++98 execution test
FAIL: g++.dg/cdce3.C -std=gnu++11 execution test
FAIL: g++.dg/cdce3.C -std=gnu++1y execution test
FAIL: g++.dg/eh/sighandle.C -std=gnu++98 execution test
FAIL: g++.dg/eh/sighandle.C -std=gnu++11 execution test
FAIL: g++.dg/eh/sighandle.C -std=gnu++1y execution test
FAIL: g++.dg/ext/cleanup-10.C -std=gnu++98 execution test
FAIL: g++.dg/ext/cleanup-10.C -std=gnu++11 execution test
FAIL: g++.dg/ext/cleanup-10.C -std=gnu++1y execution test
FAIL: g++.dg/ext/cleanup-11.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++1y execution test
FAIL: g++.dg/ext/cleanup-8.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++1y execution test
FAIL: g++.dg/ext/cleanup-9.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++1y execution test
FAIL: g++.dg/ext/sync-4.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++1y 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++1y execution test
FAIL: g++.dg/tls/thread_local3.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local3.C -std=gnu++1y execution test
FAIL: g++.dg/tls/thread_local3g.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local3g.C -std=gnu++1y execution test
FAIL: g++.dg/tls/thread_local4.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local4.C -std=gnu++1y execution test
FAIL: g++.dg/tls/thread_local4g.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local4g.C -std=gnu++1y execution test
FAIL: g++.dg/tls/thread_local5.C -std=gnu++11 execution test
FAIL: g++.dg/tls/thread_local5.C -std=gnu++1y execution test
FAIL: