Processing commands for cont...@bugs.debian.org:
> affects 856274 + gcc-mingw-w64
Bug #856274 [gnat-5,gnat-6,gnat-7] gnat-BV: gnatchop fails to execute
(ARCH-)?gcc-BV-BV
Added indication that 856274 affects gcc-mingw-w64
> thanks
Stopping processing here.
Please contact me if you need
LAST_UPDATED: Tue Jul 17 12:08:55 UTC 2018 (revision 262818)
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is s390x-ibm-linux-gnu
=== g++ tests ===
Running
LAST_UPDATED: Tue Jul 17 12:08:55 UTC 2018 (revision 262818)
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is powerpc64le-unknown-linux-gnu
=== g++ tests ===
LAST_UPDATED: Tue Jul 17 12:08:55 UTC 2018 (revision 262818)
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is i686-pc-linux-gnu
=== brig tests ===
Running
LAST_UPDATED: Tue Jul 17 12:08:55 UTC 2018 (revision 262818)
Native configuration is arm-unknown-linux-gnueabi
=== libatomic tests ===
Running target unix
=== libatomic Summary ===
# of expected passes44
# of unsupported tests 5
LAST_UPDATED: Tue Jul 17 12:08:55 UTC 2018 (revision 262818)
=== acats tests ===
FAIL: c960001
=== acats Summary ===
# of expected passes2319
# of unexpected failures1
Native configuration is x86_64-pc-linux-gnu
=== brig
Please consider the attached changes.
* apply the attached ada-verbose.diff
I fail to understand why anyone ever silents errors or command lines
nowadays.
* append the attached howto-test-path-with-cross-build to the README
of gcc-*-cross, or more experienced advices for beginners like me.
Dixi quod…
> but, at that point, 06-check-stamp was already written.
>
> Then, it hangs again.
Incidentally, killing it starts my cowbuilder hook which opens
up a shell in that chroot; at that point, build-arch was fully
done, which allowed a manual call to binary-arch to succeed (I
am going to
On Wed, 18 Jul 2018, Thorsten Glaser wrote:
> A system state inspection at the fail point shows an idle system
> and a hang here:
>
> tglase@tglase:~ $ ps axwww -O ppid | fgrep 18365
> 17623 18365 Z pts/600:00:00 [sh]
> 18365 18342 S pts/600:00:00 expect -- /usr/share/dejagnu/runtest.exp
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 18 Jul 2018 12:44:57 +0200
Source: gcc-7-cross-ports
Binary: gcc-7-cross-base-ports gcc-7-alpha-linux-gnu-base
libgcc-7-dev-alpha-cross gcc-7-alpha-linux-gnu gcc-7-plugin-dev-alpha-linux-gnu
gcc-7-cross-ports_20_source.changes uploaded successfully to localhost
along with the files:
gcc-7-cross-ports_20.dsc
gcc-7-cross-ports_20.tar.xz
gcc-7-cross-ports_20_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 18 Jul 2018 08:18:09 +0200
Source: gcc-7-cross
Binary: gcc-7-cross-base gcc-7-x86-64-linux-gnu-base libgcc-7-dev-amd64-cross
lib32gcc-7-dev-amd64-cross libx32gcc-7-dev-amd64-cross gcc-7-x86-64-linux-gnu
On 15.07.2018 17:12, Nicolas Boulenguez wrote:
> Hello.
>
> The attached reproducer_installed demonstrates that
> * 903694 is a bug in gcc-7, not in the source for gcc-snapshot.
> * 856274 is fixed in gcc-7.
>
> I have tried to rebuild gcc-7 with itself, replacing the former
>
gcc-7-cross_24_source.changes uploaded successfully to localhost
along with the files:
gcc-7-cross_24.dsc
gcc-7-cross_24.tar.xz
gcc-7-cross_24_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
14 matches
Mail list logo
