Bug#1073045: elfutils: test failures are ignored

2024-06-12 Thread Emanuele Rocca
Source: elfutils Version: 0.191-1 Severity: important All test failures during make check are ignored, see the following line in debian/rules: -LC_CTYPE=C $(MAKE) check $(USE_JOBS) || { cat tests/test-suite.log; exit 1; } Please drop the initial hyphen to ensure that the build fails in case of

Bug#1057635: marked as done (Fix gcc-13 test failures during package build)

2023-12-14 Thread Debian Bug Tracking System
Your message dated Thu, 14 Dec 2023 19:21:39 + with message-id and subject line Bug#1057635: fixed in gcc-13 13.2.0-9 has caused the Debian Bug report #1057635, regarding Fix gcc-13 test failures during package build to be marked as done. This means that you claim that the problem has been

Bug#1057635: Fix gcc-13 test failures during package build

2023-12-08 Thread Gwenole Beauchesne
t;norepro", "default" }. Also made standalone tests for the has_deb_build_options() function. Regards, Gwenole. Le jeu. 7 déc. 2023 à 10:45, Matthias Klose a écrit : > > On 06.12.23 10:30, Gwenole Beauchesne wrote: > > Package: gcc-13 > > Version: 13.2.0-7 >

Bug#1057635: Fix gcc-13 test failures during package build

2023-12-07 Thread Matthias Klose
On 06.12.23 10:30, Gwenole Beauchesne wrote: Package: gcc-13 Version: 13.2.0-7 The gcc-ice-dump.diff patch causes the GCC driver to test for the DEB_BUILD_OPTIONS environment variable and generate extra debug output when an ICE occurs, for instance. This is an interesting feature, while

Bug#1057635: Fix gcc-13 test failures during package build

2023-12-06 Thread Gwenole Beauchesne
Package: gcc-13 Version: 13.2.0-7 The gcc-ice-dump.diff patch causes the GCC driver to test for the DEB_BUILD_OPTIONS environment variable and generate extra debug output when an ICE occurs, for instance. This is an interesting feature, while building other packages, but not while building GCC

Processed (with 1 error): Re: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2023-11-21 Thread Debian Bug Tracking System
alter fixed versions of bug #1055750 to the same values previously set > forwarded 1055228 https://sourceforge.net/p/plplot/bugs/206/ Bug #1055228 [plplot] plplot: FTBFS on armhf (test segfault) Ignoring request to change the forwarded-to-address of bug#1055228 to the same value > merge -1

Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2023-11-21 Thread Rafael Laboissière
Control: reassign -1 plplot Control: forwarded 1055228 https://sourceforge.net/p/plplot/bugs/206/ Control: merge -1 1055228 * Emanuele Rocca [2023-11-16 09:30]: To be honest I think it's safe to close 1055750 (gfortran) and mark 1055228 (plplot) as forwarded upstream though, I don't think we h

Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2023-11-16 Thread Emanuele Rocca
Hi Rafael, On 2023-11-16 08:42, Rafael Laboissière wrote: > Control: forwarded -1 https://sourceforge.net/p/plplot/bugs/206/ > > * Rafael Laboissière [2023-11-16 07:51]: > > > My guess is that the bug is in PLplot and not in gfortran, but this is > > just a guess. I will eventually inform the P

Processed: Re: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2023-11-15 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://sourceforge.net/p/plplot/bugs/206/ Bug #1055750 [gfortran] gfortran: [armhf] Yield SIGBUS when compiling with -fstack-clash-protection Set Bug forwarded-to-address to 'https://sourceforge.net/p/plplot/bugs/206/'. -- 1055750: https://bugs.debia

Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2023-11-15 Thread Rafael Laboissière
Control: forwarded -1 https://sourceforge.net/p/plplot/bugs/206/ * Rafael Laboissière [2023-11-16 07:51]: My guess is that the bug is in PLplot and not in gfortran, but this is just a guess. I will eventually inform the PLplot upstream authors about the issue. Done ! R.

Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2023-11-15 Thread Rafael Laboissière
* Emanuele Rocca [2023-11-15 20:11]: On 2023-11-15 06:47, Rafael Laboissière wrote: Does this mean that the origin of the bug is upstream or that it still may be a bug in gfortran? At this point we know for sure that the issue is not armhf-specific, and also that it is not caused by stack-c

Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2023-11-15 Thread Emanuele Rocca
Hello Rafael! On 2023-11-15 06:47, Rafael Laboissière wrote: > Does this mean that the origin of the bug is upstream or that it still may > be a bug in gfortran? At this point we know for sure that the issue is not armhf-specific, and also that it is not caused by stack-clash-protection. On the c

Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2023-11-15 Thread Rafael Laboissière
Hi Emanuele, Our messages crossed. * Emanuele Rocca [2023-11-15 18:20]: On 2023-11-09 05:11, Rafael Laboissière wrote: The Fortran example x09f.f90, which is exercised during the building of plplot, now fails on armhf, due to the use of the compiler option -fstack-clash-protection. The pro

Bug#1023756: gcc-12: Miscompilation of attached test files, gcc-11 ok

2023-01-08 Thread Matthias Klose
Please could you prepare a self-contained test case, either adding the required included files, or providing the preprocessed source? Also, please with the recent GCC 11, 12 versions in unstable, and the GCC 13 snapshot in experimental.

Bug#1023756: gcc-12: Miscompilation of attached test files, gcc-11 ok

2022-11-09 Thread Camm Maguire
Subject: gcc-12: Miscompilation of attached test files, gcc-11 ok Package: gcc-12 X-Debbugs-Cc: c...@debian.org Version: 12.2.0-9 Severity: important This prevents GCL using gcc-12. = File: t.c

keep the issue open until the package can be built in a follow-up test rebuild.

2022-07-28 Thread Geert Stappers
for the other package (or clone), and add a block in this |package. Please keep the issue open until the package can be built in |a follow-up test rebuild. | |The package fails to build in a test rebuild on at least amd64 with |gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The |severity

Bug#999845: marked as done (debugedit test failures on hppa)

2021-11-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 08:39:46 + with message-id and subject line Bug#999845: fixed in debugedit 1:5.0-2 has caused the Debian Bug report #999845, regarding debugedit test failures on hppa to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#999845: debugedit test failures on hppa

2021-11-17 Thread Matthias Klose
Package: src:debugedit Version: 1:5.0-1 Severity: important Tags: sid bookworm X-Debbugs-CC: debian-h...@lists.debian.org Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=28598 debugedit shows some test failures on hppa: https://buildd.debian.org/status/fetch.php?pkg=debugedit&

Bug#999847: debugedit test failures on mips64el

2021-11-17 Thread Matthias Klose
Package: src:debugedit Version: 1:5.0-1 Severity: important Tags: sid bookworm X-Debbugs-CC: debian-m...@lists.debian.org Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=28599 debugedit shows some test failures on mips64el: https://buildd.debian.org/status/fetch.php?pkg=debugedit&

Bug#998330: cvise FTBFS: test failure

2021-11-02 Thread Adrian Bunk
7;/<>/obj-x86_64-linux-gnu/tests/../cvise.py blocksort-part.c -c "gcc -c blocksort-part.c && grep nextHi blocksort-part.c"' returned non-zero exit status 1. /usr/lib/python3.9/subprocess.py:528: CalledProcessError - Captured stderr call

Bug#988313: libgccjit-8-dev: Smoke test of libgccjit fails

2021-05-10 Thread Holger Schurig
: Installed libgccjit has failed passing the smoke test. You can verify it yourself compiling: <https://gcc.gnu.org/onlinedocs/jit/intro/tutorial01.html>. Please report the issue to your distribution if libgccjit was installed through that. Here instructions on how to compile and install lib

Bug#972820: confirmation, test case

2020-12-04 Thread Ryan Pavlik
of course inferior to having them > actually provided by the relevant source package. > https://salsa.debian.org/rpavlik/gcc-10-compat (I only mocked up/built > the packages required to test on x86_64/i386, but I'd expect the same > problem and solution on the other platforms that have a

Bug#972820: confirmation, test case

2020-12-04 Thread Ryan Pavlik
by the relevant source package. https://salsa.debian.org/rpavlik/gcc-10-compat (I only mocked up/built the packages required to test on x86_64/i386, but I'd expect the same problem and solution on the other platforms that have additional libgcc packages.) I have a reproducible test case: I did

Bug#946709: Patch for one more successful libgo test: syscall

2019-12-23 Thread Svante Signell
Hello again, The attached patch libgo_go_syscall_export_unix_test.go.diff fixes one failing test of libgo: syscall. Maybe it could be added to the patch already submitted patch in this bug report. Thanks! --- a/src/libgo/go/syscall/export_unix_test.go 2017-05-10 19:26:09.0 +0200 +++ b

Bug#836944: marked as done (gcc: autoconf test failing on amd64 with -pie -static combination)

2019-02-06 Thread Debian Bug Tracking System
Your message dated Thu, 07 Feb 2019 03:13:19 + with message-id and subject line Bug#920171: Removed package(s) from unstable has caused the Debian Bug report #836944, regarding gcc: autoconf test failing on amd64 with -pie -static combination to be marked as done. This means that you claim

Bug#819429: marked as done (libstdc++-5-dev: Kodi test crashes in STL on armel and armhf)

2019-01-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Jan 2019 10:00:21 + with message-id and subject line Bug#920166: Removed package(s) from unstable has caused the Debian Bug report #819429, regarding libstdc++-5-dev: Kodi test crashes in STL on armel and armhf to be marked as done. This means that you claim that

Bug#888911: marked as done (giac test failures with mpfr 4.0.0 on several architectures)

2018-02-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Feb 2018 18:20:19 + with message-id and subject line Bug#888422: fixed in mpfr4 4.0.1-1 has caused the Debian Bug report #888422, regarding giac test failures with mpfr 4.0.0 on several architectures to be marked as done. This means that you claim that the problem

Processed: Re: ngircd test suite failure on mips64el

2017-08-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 871514 + ngircd Bug #871514 [gcc-7] clamav: FTBFS on mips64el Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks that 1 > 1) Added indication that 871514 affects ngircd Added indication that 871538 affects ngircd

Debian/Ubuntu test rebuilds using GCC 7 (r243559)

2016-12-16 Thread Matthias Klose
Here are the results of a first test rebuild of the Debian (amd64) and Ubuntu (all architectures) archives. The test was started with a GCC trunk around 20161202, and then build failures were retried later with r243559. I filed around 10-15 issues for ICEs, the most of them already fixed on the

[Bug libgcj/1373] recursion stress test causes segmentation fault

2016-09-30 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373 Andrew Pinski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

Bug#785249: marked as done (gcc-4.9: test suite errors when memory overcommitting is turned off)

2016-09-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Sep 2016 22:15:11 + with message-id and subject line Bug#838316: Removed package(s) from unstable has caused the Debian Bug report #785249, regarding gcc-4.9: test suite errors when memory overcommitting is turned off to be marked as done. This means that you claim

Bug#836944: gcc: autoconf test failing on amd64 with -pie -static combination

2016-09-07 Thread Frederic Bonnard
Package: gcc-6 Version: 6.2.0-3 -- Hi, I've got an issue close to this one : https://sourceware.org/bugzilla/show_bug.cgi?id=16428 (unstable)debian@vm81:~$ cat conftest.c int main() { return 0; } (unstable)debian@vm81:~$ gcc -fPIE -pie -static conftest1.c /usr/bin/ld: /usr/lib/gcc/x86_64-linux-g

Bug#833430: marked as done (creduce doesn't pass the files to reduce to the test script)

2016-08-07 Thread Debian Bug Tracking System
Your message dated Sun, 7 Aug 2016 12:58:56 +0200 with message-id and subject line Re: Bug#833430: creduce doesn't pass the files to reduce to the test script has caused the Debian Bug report #833430, regarding creduce doesn't pass the files to reduce to the test script to be mark

Bug#833430: creduce doesn't pass the files to reduce to the test script

2016-08-05 Thread Niko Tyni
On Thu, Aug 04, 2016 at 11:26:58AM +0200, Matthias Klose wrote: > Package: creduce > Version: 2.5.0-1 > Severity: serious > Tags: sid stretch > > creduce doesn't pass the files to reduce to the test script. This used to > work ... > > $ creduce --debug ./cr2.sh

Bug#833430: creduce doesn't pass the files to reduce to the test script

2016-08-04 Thread Matthias Klose
Package: creduce Version: 2.5.0-1 Severity: serious Tags: sid stretch creduce doesn't pass the files to reduce to the test script. This used to work ... $ creduce --debug ./cr2.sh foo.c successfully checked prereqs for pass_include_includes successfully checked prereqs for pass_inc

Processed: Re: Bug#811707: FTBFS with GCC 6: compiler failed the ACC conformance test

2016-04-06 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:ucl Bug #811707 [gcc-6] gcc-6 fails to compile a valid code Bug reassigned from package 'gcc-6' to 'src:ucl'. No longer marked as found in versions gcc-6/6-20160228-1. Ignoring request to alter fixed versions of bug #811707 to the same values previou

Bug#811707: FTBFS with GCC 6: compiler failed the ACC conformance test

2016-04-06 Thread Matthias Klose
Control: reassign -1 src:ucl both gcc-5 and gcc-6 show the same error message: $ gcc-6 -c test.c test.c:1:12: error: size of array '__acc_cta' is negative extern int __acc_cta[1-2*!((1l << (8*4 -1)) < 0)]; ^

Bug#819429: libstdc++-5-dev: Kodi test crashes in STL on armel and armhf

2016-03-28 Thread Balint Reczey
Package: libstdc++-5-dev Version: 5.3.1-13 Control: affects -1 kodi Dear Maintainer, Kodi fails to build on armel and armhf due to a crashing test: https://buildd.debian.org/status/fetch.php?pkg=kodi&arch=armhf&ver=16.0%2Bdfsg1-2&stamp=1458793597 ... [--] 1 test from TestScra

Processed: libstdc++-5-dev: Kodi test crashes in STL on armel and armhf

2016-03-28 Thread Debian Bug Tracking System
Processing control commands: > affects -1 kodi Bug #819429 [libstdc++-5-dev] libstdc++-5-dev: Kodi test crashes in STL on armel and armhf Added indication that 819429 affects kodi -- 819429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819429 Debian Bug Tracking System Contact

Processed: Re: Bug#811707: FTBFS with GCC 6: compiler failed the ACC conformance test

2016-03-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 811707 gcc-6 6-20160228-1 Bug #811707 [ucl] FTBFS with GCC 6: compiler failed the ACC conformance test Bug reassigned from package 'ucl' to 'gcc-6'. No longer marked as found in versions 1.03+repack-3. Ignoring

Re: Bug#811707: FTBFS with GCC 6: compiler failed the ACC conformance test

2016-03-06 Thread Robert Luberda
RCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > checking whether your compiler passes the ACC conformance test... FAILED > configure: > configure: Your compiler failed the ACC conformance test - for details see > configure: `config.log'. Please check that log file and consider send

Bug#812287: marked as done (test suites segfault / constexpr leaves reference member var uninitialized)

2016-02-06 Thread Debian Bug Tracking System
Your message dated Sun, 07 Feb 2016 00:08:46 + with message-id and subject line Bug#812287: fixed in gcc-6 6-20160205-1 has caused the Debian Bug report #812287, regarding test suites segfault / constexpr leaves reference member var uninitialized to be marked as done. This means that you

Re: Bug#812287: libetonyek: FTBFS with GCC 6: test suite segfaults

2016-01-22 Thread Martin Michlmayr
reopen 812287 reassign 812287 gcc-6 6-20160117-1 retitle 812287 test suites segfault / constexpr leaves reference member var uninitialized forwarded 812287 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69327 thanks * Rene Engelhard [2016-01-22 13:01]: > That reminds me of >

Processed: Re: Bug#812287: libetonyek: FTBFS with GCC 6: test suite segfaults

2016-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 812287 Bug #812287 {Done: Rene Engelhard } [libetonyek] libetonyek: FTBFS with GCC 6: test suite segfaults Bug reopened Ignoring request to alter fixed versions of bug #812287 to the same values previously set > reassign 812287 g

Re: Bug#812287: libetonyek: FTBFS with GCC 6: test suite segfaults

2016-01-22 Thread Rene Engelhard
. See below. > possible I reported a non-issue, although I tried to avoid that. It probably is. See below. > I apologize in advance if this is the case. No problem. > If you have some time to look into this issue, that'd be great. If > not, I can re-test the package with GCC 6 in

Bug#806769: FTBS: failed test on mipsel architecture: random Bus error emitted from GOMP

2015-11-30 Thread Jerome Benoit
reads: --8><-- [...] Starting program: /home/calculus/normaliz/normaliz-00/normaliz/_build/normaliz -h test-h/cut.in [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/

Bug#635214: marked as done (gcc-4.6: [sparc] miscompile PARI/GP 2.5.0 [test-case provided])

2015-08-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Aug 2015 13:43:08 + with message-id and subject line Bug#796274: Removed package(s) from unstable has caused the Debian Bug report #635214, regarding gcc-4.6: [sparc] miscompile PARI/GP 2.5.0 [test-case provided] to be marked as done. This means that you claim that

Bug#671368: marked as done (100% acats test failures on armel)

2015-08-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Aug 2015 12:09:36 + with message-id and subject line Bug#796148: Removed package(s) from unstable has caused the Debian Bug report #671368, regarding 100% acats test failures on armel to be marked as done. This means that you claim that the problem has been dealt

Bug#794605: marked as done (gcc-5-plugin-dev: A simpel test to see if gcc-5-plugin-dev works yields as result:)

2015-08-05 Thread Debian Bug Tracking System
Your message dated Wed, 05 Aug 2015 12:25:04 +0200 with message-id <55c1e480.1020...@debian.org> and subject line Re: Bug#794605: gcc-5-plugin-dev: A simpel test to see if gcc-5-plugin-dev works yields as result: has caused the Debian Bug report #794605, regarding gcc-5-plugin-dev: A simpe

Bug#794605: gcc-5-plugin-dev: A simpel test to see if gcc-5-plugin-dev works yields as result:

2015-08-04 Thread Huub Reuver
, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) The test used can be used from the CLI: gcc -E -shared - -o /dev/null -I`gcc -print-file-name=plugin`/include 2>&1 <:1: /usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/hash-table.h:201:15: f

Bug#593324: marked as done ([armel] g++-4.4 -O1 makes ppl test suite fail)

2015-07-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 Jul 2015 16:18:22 + with message-id and subject line Bug#707276: Removed package(s) from unstable has caused the Debian Bug report #593324, regarding [armel] g++-4.4 -O1 makes ppl test suite fail to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#785249: gcc-4.9: test suite errors when memory overcommitting is turned off

2015-05-15 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://gcc.gnu.org/PR66154 Bug #785249 [gcc-4.9] gcc-4.9: test suite errors when memory overcommitting is turned off Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR66154'. > tags -1 + upstream Bug #785249 [gcc-4.9] gcc-4.9: t

Bug#785249: gcc-4.9: test suite errors when memory overcommitting is turned off

2015-05-15 Thread Matthias Klose
Control: forwarded -1 https://gcc.gnu.org/PR66154 Control: tags -1 + upstream -- 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/e307.3080...@debian.org

Bug#785249: gcc-4.9: test suite errors when memory overcommitting is turned off

2015-05-13 Thread Frank Heckenbach
Package: gcc-4.9 Version: 4.9.2-10 Severity: normal When I tried building gcc from sources (debuild -us -uc), I got a number of errors like this: FAIL: g++.dg/asan/interception-malloc-test-1.C -O1 output pattern test, is ==25380==ERROR: AddressSanitizer failed to allocate 0xdfff0001000

Bug#735006: marked as done (gcc-4.9: amd64 kernel gives error alg: hash: Chunking test 1 failed for hmac(md5-generic))

2014-09-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Sep 2014 16:33:57 +0200 with message-id <540726d5.4040...@debian.org> and subject line Re: Bug#735006: gcc-4.9: amd64 kernel gives error alg: hash: Chunking test 1 failed for hmac(md5-generic) has caused the Debian Bug report #735006, regarding gcc-4.9: amd64

Bug#756266: marked as done (g++-4.9: test summaries compressed twice (and why install them at all..?))

2014-07-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jul 2014 11:57:22 +0200 with message-id <53d61e82.1030...@debian.org> and subject line Re: Bug#756266: g++-4.9: test summaries compressed twice (and why install them at all..?) has caused the Debian Bug report #756266, regarding g++-4.9: test summaries compressed

Bug#756266: g++-4.9: test summaries compressed twice (and why install them at all..?)

2014-07-28 Thread RjY
Package: g++-4.9 Version: 4.9.1-3 Severity: minor Many of the files in /usr/share/doc/gcc-4.9-base are compressed by xz then by gz. This seems wrong. (Reporting to g++-4.9 since that package owns the files.) % ls -l /usr/share/doc/gcc-4.9-base/test-summaries total 15316 -rw-r--r-- 1 root root

Bug#713323: marked as done (gcc-snapshot: FTBFS: There were fixinclude test FAILURES)

2014-04-05 Thread Debian Bug Tracking System
Your message dated Sat, 05 Apr 2014 11:51:16 +0200 with message-id <533fd214.9060...@debian.org> and subject line closing old bug reports in gcc-snapshot has caused the Debian Bug report #713323, regarding gcc-snapshot: FTBFS: There were fixinclude test FAILURES to be marked as done. This

Re: Debian test rebuild on x86_64-linux-gnu with trunk 20140118

2014-01-24 Thread Jonathan Wakely
On 24 January 2014 10:08, Matthias Klose wrote: > > brainparty, igstk: > error: redeclaration of '...' may not have default arguments [-fpermissive] G++ was fixed to reject this, the code is invalid. > > apron, cadabra: > error: 'ptrdiff_t' does not name a type These should be qualifying the

Re: Debian test rebuild on x86_64-linux-gnu with trunk 20140118

2014-01-24 Thread Jonathan Wakely
On 24 January 2014 10:08, Matthias Klose wrote: > > 0ad, aria2, cupt, dssp, fish, fldigi, iverilog, mednafen, mkvtoolnix, mrs, > nmap, v4l-utils: > error: converting to '...' from initializer list would use explicit > constructor '...' That one was a GCC problem, fixed by http://gcc.gnu.org/view

Debian test rebuild on x86_64-linux-gnu with trunk 20140118

2014-01-24 Thread Matthias Klose
Here are some preliminary results of a test rebuild on x86_64-linux-gnu with trunk 20140118, for all 10755 source packages building architecture dependent binary packages. Compared to the current gcc-4.8 in Debian unstable, there were 103 new build failures. The gcc-4.9 packages used can be found

Processed: Re: Bug#735006: gcc-4.9: amd64 kernel gives error alg: hash: Chunking test 1 failed for hmac(md5-generic)

2014-01-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 wishlist Bug #735006 [gcc-4.9] gcc-4.9: amd64 kernel gives error alg: hash: Chunking test 1 failed for hmac(md5-generic) Severity set to 'wishlist' from 'normal' -- 735006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735

Bug#735006: gcc-4.9: amd64 kernel gives error alg: hash: Chunking test 1 failed for hmac(md5-generic)

2014-01-11 Thread Matthias Klose
Control: severity -1 wishlist Am 11.01.2014 19:26, schrieb Arthur Marsh: > Package: gcc-4.9 > Version: 4.9-20140110-1 > Severity: normal > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > >* What led up to the situation? > > building current git he

Bug#735006: gcc-4.9: amd64 kernel gives error alg: hash: Chunking test 1 failed for hmac(md5-generic)

2014-01-11 Thread Arthur Marsh
Key type cifs.idmap registered [ 55.421943] alg: hash: Chunking test 1 failed for hmac(md5-generic) [ 55.427058] : 53 49 32 30 a0 a8 ec 9f 4d 64 c9 74 62 52 20 d2 [ 55.432172] CIFS VFS: could not allocate crypto hmacmd5 [ 55.437212] CIFS VFS: could not crypto alloc hmacmd5 rc -2 [

Possible transition: Debian realpath -> GNU realpath; please test your packages

2013-12-15 Thread Robert Luberda
on). Could you please check if the above differences are important to your packages? You can try to test your package against experimental `realpath 1.19.coreutils.1' that is built from the coreutils sources. For the transition itself, since the gcc-* packages have versioned build-depend

Bug#713323: gcc-snapshot: FTBFS: There were fixinclude test FAILURES

2013-06-22 Thread Lucas Nussbaum
ts/string2.h > Fixed: bsd/libc.h > Fixed: c_asm.h > Fixed: com_err.h > Fixed: complex.h > Fixed: ctrl-quotes-def-1.h > Fixed: ctype.h > Fixed: curses.h > Fixed: errno.h > Fixed: features.h > Fixed: fixinc-test-limits.h > Fixed: hsfs/hsfs_spec.h > Fixed:

Bug#667341: test builds for template issues in qmf

2012-07-12 Thread Neil Williams
ch gcc-4.6 can pick up as an error or warning in the qmf sources. Reinstalling gcc-4.7 & g++-4.7 and rebuilding with the same flags (and the #include patch) does not indicate any problems with the qmfclient library itself, g++-4.7 just fails to link the test binary. -- Neil Williams

Bug#671368: 100% acats test failures on armel

2012-05-03 Thread Matthias Klose
Package: gnat-4.6 Version: 4.6.3-3 Severity: important seen on the armel build log ... === acats support === Generating support files...sed: -e expression #2, char 165: unterminated `s' command ... and all acats tests fail this fails: target_gnatmake $testdir/support/impbit.adb

Bug#635126: Standalone test case

2011-11-25 Thread Jurij Smakov
Hi, Attached is a standalone test case for this bug, obtained on an up-to-date sid/sparc system. With it I see the following behavior: jurij@debian:~$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/sparc-linux-gnu/4.6/lto-wrapper Target: sparc-linux-gnu Configured

Bug#644338: libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float

2011-10-12 Thread Moffett, Kyle D
oat rework. * Add a new libffi5.symbols.powerpcspe file copied from powerpc. I have performed a native build of this patch on a PowerPC64 system, compiling both the libffi5 and lib64ffi5 versions successfully, with no test-suite failures. Unfortunately I am having issues with my powerpcspe build

Bug#644338: libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float

2011-10-12 Thread Moffett, Kyle D
>> The attached patch resolves both issues. > > and ftbfs on powerpc: > https://buildd.debian.org/status/fetch.php?pkg=libffi&arch=powerpc&ver=3.0.10-2&stamp=1318082452 Ahh, damn, Ok. New patch coming shortly, sorry about that. I'll see if I can use one of the I

Bug#644338: libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float

2011-10-12 Thread Matthias Klose
On 10/05/2011 12:12 AM, Kyle Moffett wrote: > Package: libffi > Severity: normal > Tags: patch upstream > User: debian-powerpc...@breakpoint.cc > Usertags: powerpcspe > > The Debian-Ports "powerpcspe" architecture can't currently build the > libffi package for a couple reasons: > > (1) The pack

Bug#644338: marked as done (libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float)

2011-10-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Oct 2011 13:32:53 + with message-id and subject line Bug#644338: fixed in libffi 3.0.10-2 has caused the Debian Bug report #644338, regarding libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float to be marked as done. This means that you

Bug#644338: marked as done (libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float)

2011-10-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Oct 2011 12:03:02 + with message-id and subject line Bug#644338: fixed in libffi 3.0.11~rc1-4 has caused the Debian Bug report #644338, regarding libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float to be marked as done. This means that

Bug#644338: Fwd: libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float

2011-10-07 Thread Moffett, Kyle D
rom: "Moffett, Kyle D" > Date: October 04, 2011 18:12:27 EDT > To: Debian Bug Tracking System > Subject: libffi: Build errors on PowerPC e500, test-suite failures on PowerPC > soft-float > > Package: libffi > Severity: normal > Tags: patch upstream > User: de

Bug#644338: libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float

2011-10-07 Thread Matthias Klose
please forward this upstream. On 10/05/2011 12:12 AM, Kyle Moffett wrote: > Package: libffi > Severity: normal > Tags: patch upstream > User: debian-powerpc...@breakpoint.cc > Usertags: powerpcspe > > The Debian-Ports "powerpcspe" architecture can't currently build the > libffi package for a coup

Bug#644338: libffi: Build errors on PowerPC e500, test-suite failures on PowerPC soft-float

2011-10-04 Thread Kyle Moffett
f (typenum == FFI_TYPE_DOUBLE) + typenum = FFI_TYPE_UINT64; + if (typenum == FFI_TYPE_LONGDOUBLE) + typenum = FFI_TYPE_UINT128; + } else if (ecif->cif->abi != FFI_LINUX) { +#if FFI_TYPE_LONGDOUBLE != FFI_TYPE_DOUBLE + if (typenum == FFI_TYPE_

Bug#635214: gcc-4.6: [sparc] miscompile PARI/GP 2.5.0 [test-case provided]

2011-07-24 Thread Bill Allombert
Hello GCC maintainers, Please find a smaller test-case. smetana% gcc -O3 -Wall -g test.c -o test smetana% ./test zsh: segmentation fault ./test smetana% gcc -O3 -Wall -g test.c -o test -fno-inline smetana% ./test smetana% Cheers, -- Bill. Imagine a large red swirl here. #include inline

Bug#635214: gcc-4.6: [sparc] miscompile PARI/GP 2.5.0 [test-case provided]

2011-07-23 Thread Bastian Blank
On Sat, Jul 23, 2011 at 11:14:34PM +0200, Bill Allombert wrote: > #include > inline void* > pari_realloc(void *pointer, size_t size) > { > char *tmp; > if (!pointer) > tmp = (char *) malloc(size); > else > tmp = (char *) realloc(pointer,size); Please fix the obvious problems: - Neve

Bug#635214: gcc-4.6: [sparc] miscompile PARI/GP 2.5.0 [test-case provided]

2011-07-23 Thread Bill Allombert
Package: gcc-4.6 Version: 4.6.1-4 Severity: normal Hello Debian GCC Maintainers, gcc-4.6 miscompiles pari 2.5.0 on sparc, see See https://buildd.debian.org/status/fetch.php?pkg=pari&arch=sparc&ver=2.5.0-1&stamp=1311418380 Please find a small test-case attached (test.c) gcc -O2 -

gcc of test was disabled?

2011-06-15 Thread Nobuhiro Iwamatsu
Hi, Debian GCC Maintainers. I noticed that test of gcc was disabled from gcc_4.6-13. This is not written in debian changelog. Could you teach the reason? # It is a change to architecture to make CPU with slow speed a target glad :-) Best regards, Nobuhiro -- Nobuhiro Iwamatsu    iwamatsu at

Re: CPP test program fails for x64 platform

2011-04-01 Thread Dmitry Katsubo
? >> - How to overcome the problem? > > caused by the ld --no-add-needed default? Link libnetpbm.so with -lm. > See http://wiki.debian.org/ToolChain/DSOLinking Matthias, thank you a lot. "-Wl,--as-needed" argument looks to play the essential role! So the original test scrip

Re: CPP test program fails for x64 platform

2011-03-31 Thread Matthias Klose
On 31.03.2011 18:29, Dmitry Katsubo wrote: > Dear developers, > > I hope somebody in this maillist can help me with my (perhaps trivial) > problem. > > I have written autoconf script, which among all other checks performs > the following test: > > AC_LANG([C

CPP test program fails for x64 platform

2011-03-31 Thread Dmitry Katsubo
Dear developers, I hope somebody in this maillist can help me with my (perhaps trivial) problem. I have written autoconf script, which among all other checks performs the following test: AC_LANG([C++]) ... AC_SEARCH_LIBS([pnm_readpnminit], [netpbm pnm]) The resulting configure script works

Bug#593324: [armel] g++-4.4 -O1 makes ppl test suite fail

2010-08-17 Thread Michael Tautschnig
Package: g++-4.4 Version: 4.4.4-8 (Leaving choice of severity to gcc maintainers; at the current stage ppl cannot migrate to testing although it would fix an RC bug.) ppl 0.10.2-7 FTBS on armel [1] (exclusively) with test suite failures; this was extremely surprising as 0.10.2-6 was fine [2] and

Bug#542794: Test case

2010-08-11 Thread Ole Laursen
On Fri, Aug 6, 2010 at 3:31 PM, Arthur Loiret wrote: > Thanks for your test case. Could you please try again with > gcc-4.5/libgomp1 from experimental? Thanks for the interest! I don't have a machine I can butcher with an experimental GCC right now, unfortunately, but VIPS actually w

Bug#542794: Test case

2010-08-06 Thread Arthur Loiret
Hi! Thanks for your test case. Could you please try again with gcc-4.5/libgomp1 from experimental? Thanks! Arthur. 2009/8/21, Ole Laursen : > Hi! > > Forgot to attach a test case. It's really simple. Install > python-vipscc and run the following (and also attached) Python s

Bug#567695: smaller test case enclosed

2010-06-22 Thread Matthias Klose
On 23.02.2010 23:47, Falk Hueffner wrote: On Thu, Feb 04, 2010 at 09:55:42AM -0500, Camm Maguire wrote: This test program will segfault at -O2 on the affected machines: Can you please repost the attachment? It is not retrievable from the BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Bug#582787: marked as done (gcc-4.4: [hppa] Test tstdiomisc fails when multiplication of NAN by -1 results in NAN again.)

2010-06-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Jun 2010 05:19:41 + with message-id and subject line Bug#582787: fixed in gcc-4.5 4.5.0-5 has caused the Debian Bug report #582787, regarding gcc-4.4: [hppa] Test tstdiomisc fails when multiplication of NAN by -1 results in NAN again. to be marked as done. This

Bug#582787: marked as done (gcc-4.4: [hppa] Test tstdiomisc fails when multiplication of NAN by -1 results in NAN again.)

2010-06-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Jun 2010 05:03:30 + with message-id and subject line Bug#582787: fixed in gcc-4.4 4.4.4-4 has caused the Debian Bug report #582787, regarding gcc-4.4: [hppa] Test tstdiomisc fails when multiplication of NAN by -1 results in NAN again. to be marked as done. This

Bug#582787: gcc-4.4: [hppa] Test tstdiomisc fails when multiplication of NAN by -1 results in NAN again.

2010-05-23 Thread Clint Adams
Package: gcc-4.4 Version: 4.4.4-2 - Forwarded message from Carlos O'Donell - Date: Sat, 22 May 2010 22:58:18 -0400 From: Carlos O'Donell To: John David Anglin , Debian HPPA Port List , libc-po...@sourceware.org Subject: Test tstdiomisc fails when multiplicat

Bug#575322: gcc-snapshot: FTBFS on kfreebsd-i386: s=`cat status`; rm -f status; test $s -eq 0

2010-03-25 Thread Arthur Loiret
u/libgfortran' > | make[3]: Leaving directory > `/build/buildd-gcc-snapshot_20100310-1-kfreebsd-i386-c6zRmm/gcc-snapshot-20100310/build' > | make[2]: *** [bootstrap-lean] Error 2 > | make[2]: Leaving directory > `/build/buildd-gcc-snapshot_20100310-1-kfreebsd-i386-c6zRmm/gcc-s

Bug#575322: gcc-snapshot: FTBFS on kfreebsd-i386: s=`cat status`; rm -f status; test $s -eq 0

2010-03-24 Thread Matthias Klose
eebsd-gnu/libgfortran' | make[3]: Leaving directory `/build/buildd-gcc-snapshot_20100310-1-kfreebsd-i386-c6zRmm/gcc-snapshot-20100310/build' | make[2]: *** [bootstrap-lean] Error 2 | make[2]: Leaving directory `/build/buildd-gcc-snapshot_20100310-1-kfreebsd-i386-c6zRmm/gcc-snapshot-201

Bug#575322: gcc-snapshot: FTBFS on kfreebsd-i386: s=`cat status`; rm -f status; test $s -eq 0

2010-03-24 Thread Cyril Brulebois
directory `/build/buildd-gcc-snapshot_20100310-1-kfreebsd-i386-c6zRmm/gcc-snapshot-20100310/build' | s=`cat status`; rm -f status; test $s -eq 0 | make[1]: *** [stamps/05-build-stamp] Error 1 | make[1]: Leaving directory `/build/buildd-gcc-snapshot_20100310-1-kfreebsd-i386-c6zRmm/gcc-sna

Bug#567695: smaller test case enclosed

2010-02-23 Thread Falk Hueffner
On Thu, Feb 04, 2010 at 09:55:42AM -0500, Camm Maguire wrote: > This test program will segfault at -O2 on the affected machines: Can you please repost the attachment? It is not retrievable from the BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567695 ... Falk -- To UNSUBSCR

Bug#567695: smaller test case enclosed

2010-02-04 Thread Camm Maguire
This test program will segfault at -O2 on the affected machines: Take care, -- Camm Maguirec...@maguirefamily.org == "The earth is but one country, and mankind its cit

Re: rebuild test of Debian packages with GCC trunk 20100107

2010-01-13 Thread Julien Cristau
On Thu, Jan 14, 2010 at 01:13:19 +0100, Holger Levsen wrote: > In both cases it would be nice if you'd tag those bugs (FTBFS with > gcc-4.4 and 4.5) with sid+squeeze, so that they dont show up as RC > bugs for stable, for packages which have the same version in lenny. > Except you don't want the

Re: rebuild test of Debian packages with GCC trunk 20100107

2010-01-13 Thread Holger Levsen
Hi, On Mittwoch, 13. Januar 2010, Luk Claes wrote: > >> Please also tag them sid (and squeeze?), so they wont show up affecting > >> stable, if the version in stable is the same as in sid... > > > > I wouldn't worry about that just yet. Unless we're planning > > on switching to gcc-4.5 before the

Re: rebuild test of Debian packages with GCC trunk 20100107

2010-01-13 Thread Kurt Roeckx
On Tue, Jan 12, 2010 at 10:20:38AM +0100, Holger Levsen wrote: > Hi, > > On Dienstag, 12. Januar 2010, Raphael Geissert wrote: > > Please don't forget to usertag the reports. Using the "ftbfs-gcc-4.5" > > usertag should make it easier to track them (which would later make them > > show up on the d

Re: rebuild test of Debian packages with GCC trunk 20100107

2010-01-13 Thread Luk Claes
Kurt Roeckx wrote: > On Tue, Jan 12, 2010 at 10:20:38AM +0100, Holger Levsen wrote: >> Hi, >> >> On Dienstag, 12. Januar 2010, Raphael Geissert wrote: >>> Please don't forget to usertag the reports. Using the "ftbfs-gcc-4.5" >>> usertag should make it easier to track them (which would later make th

  1   2   3   >