Package: libcc-5-dev Version: 5-20150205-1 Severity: important Tags: patch Hello,
The libgomp testsuite fails on kfreebsd and hurd because the omp_nest_lock_t size announced to application doesn't correspond to the actual size used internally. This happens because ./debian/patches/libgomp-omp_h-multilib.diff actually hardcodes (!) the size of omp_nest_lock_t. I guess this was done in order to be able to use the same omp.h on both i386 and amd64, but I don't think this is still needed now that omp.h is in arch-specific /usr/lib/gcc/x86_64-linux-gnu/5/include/omp.h Could you consider removing this patch? Samuel -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages gcc-5 depends on: ii binutils 2.25-4 ii cpp-5 5-20150205-1 ii gcc-5-base 5-20150205-1 ii libc6 2.19-13 ii libcc1-0 5-20150205-1 ii libgcc-5-dev 5-20150205-1 ii libgmp10 2:6.0.0+dfsg-6 ii libisl10 0.12.2-2 ii libmpc3 1.0.2-1 ii libmpfr4 3.1.2-2 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages gcc-5 recommends: ii libc6-dev 2.19-13 Versions of packages gcc-5 suggests: pn gcc-5-doc <none> pn gcc-5-locales <none> ii gcc-5-multilib 5-20150205-1 pn libasan2-dbg <none> pn libatomic1-dbg <none> pn libcilkrts5-dbg <none> ii libgcc1-dbg 1:5-20150205-1 pn libgomp1-dbg <none> pn libitm1-dbg <none> pn liblsan0-dbg <none> pn libquadmath0-dbg <none> pn libtsan0-dbg <none> pn libubsan0-dbg <none> -- no debconf information -- Samuel Progress (n.): The process through which the Internet has evolved from smart people in front of dumb terminals to dumb people in front of smart terminals. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
