Your message dated Sat, 11 Feb 2017 22:12:59 +0100
with message-id <[email protected]>
and subject line Bug#706475: sparc buildd sompek seems to have hardware issues
has caused the Debian Bug report #706475,
regarding sparc buildd sompek seems to have hardware issues
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
706475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706475
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: buildd.debian.org
sompek seems to have some kind of hardware issues, seen at least twice building
openjdk-7:
https://buildd.debian.org/status/logs.php?pkg=openjdk-7&arch=sparc
g++-4.7 ...
../generated/jvmtifiles/jvmtiEnter.cpp: In function 'jvmtiError
jvmti_ForceEarlyReturnLong(jvmtiEnv*, jthread, jlong)':
../generated/jvmtifiles/jvmtiEnter.cpp:1662:1: internal compiler error:
Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
--- End Message ---
--- Begin Message ---
On 2013-04-30 18:16, Matthias Klose wrote:
> Package: buildd.debian.org
>
> sompek seems to have some kind of hardware issues, seen at least twice
> building
> openjdk-7:
>
> https://buildd.debian.org/status/logs.php?pkg=openjdk-7&arch=sparc
>
> g++-4.7 ...
>
> ../generated/jvmtifiles/jvmtiEnter.cpp: In function 'jvmtiError
> jvmti_ForceEarlyReturnLong(jvmtiEnv*, jthread, jlong)':
> ../generated/jvmtifiles/jvmtiEnter.cpp:1662:1: internal compiler error:
> Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
> The bug is not reproducible, so it is likely a hardware or OS problem.
The machine doesn't exist anymore. Closing the bug.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
[email protected] http://www.aurel32.net
--- End Message ---
