Your message dated Sat, 18 May 2002 14:12:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Build server was short on memory
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 17 May 2002 02:38:13 +0000
>From [EMAIL PROTECTED] Thu May 16 21:38:13 2002
Return-path: <[EMAIL PROTECTED]>
Received: from dsl-65-184-214-9.telocity.com (sonny.eddelbuettel.com) 
[65.184.214.9] (mail)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 178XdE-0000UC-00; Thu, 16 May 2002 21:38:12 -0500
Received: from edd by sonny.eddelbuettel.com with local (Exim 3.35 #1 (Debian))
        id 178XdG-0008Of-00
        for <[EMAIL PROTECTED]>; Thu, 16 May 2002 21:38:14 -0500
To: Debian Bug Tracking System <[EMAIL PROTECTED]> 
Subject: g++: internal compiler error on s390 
X-Debbugs-CC: Dirk Eddelbuettel <[EMAIL PROTECTED]>
From: Dirk Eddelbuettel <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Date: Thu, 16 May 2002 21:38:14 -0500
Delivered-To: [EMAIL PROTECTED]

Package: g++
Version: 2:2.95.4-14  (or what s390 used, see below)
Severity: normal

My QuantLib package doesn't build on s390. Buildd shows the following towards
the end of the log:


make[3]: Entering directory `/build/buildd/quantlib-0.3.0/Examples/Swap'
source='swapvaluation.cpp' object='swapvaluation.o' libtool=no \
depfile='.deps/swapvaluation.Po' tmpdepfile='.deps/swapvaluation.TPo' \
depmode=gcc /bin/sh ../../config/depcomp \
g++ -DHAVE_CONFIG_H -I. -I. -I../../ql -I../.. -I../..    -O2 -D_REENTRANT -c 
-o swapvaluation.o `test -f swapvaluation.cpp || echo './'`swapvaluation.cpp
g++: Internal compiler error: program cc1plus got fatal signal 9
make[3]: *** [swapvaluation.o] Error 1
make[3]: Leaving directory `/build/buildd/quantlib-0.3.0/Examples/Swap'


This is pretty much the most ram-consuming c++ code I have seen, it might
simply have been short of further memory resources.

Let me know if I can help with further infos.

Dirk


-- System Information
Debian Release: 3.0
Kernel Version: Linux sonny 2.2.20ext3 #1 Sat Dec 8 23:52:06 CST 2001 i586 
unknown

Versions of the packages g++ depends on:
ii  cpp            2.95.4-14      The GNU C preprocessor.
ii  g++-2.95       2.95.4-7       The GNU C++ compiler.
ii  gcc-2.95       2.95.4-7       The GNU C compiler.


-- 
Good judgement comes from experience; experience comes from bad judgement. 
                                                            -- Fred Brooks

---------------------------------------
Received: (at 147241-done) by bugs.debian.org; 18 May 2002 13:08:37 +0000
>From [EMAIL PROTECTED] Sat May 18 08:08:37 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mgw00.swol.de [195.238.142.133] 
        by master.debian.org with smtp (Exim 3.12 1 (Debian))
        id 1793wr-0000hN-00; Sat, 18 May 2002 08:08:37 -0500
Received: (qmail 3471 invoked by uid 1001); 18 May 2002 14:07:14 -0000
Received: from p508a807a.dip0.t-ipconnect.de (HELO tau) (80.138.128.122)
  by mgw00.swol.de with SMTP; 18 May 2002 14:07:14 -0000
From: Gerhard Tonn <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Build server was short on memory
Date: Sat, 18 May 2002 14:12:44 +0200
X-Mailer: KMail [version 1.1.99]
Content-Type: text/plain;
  charset="iso-8859-1"
MIME-Version: 1.0
Message-Id: <[EMAIL PROTECTED]>
Content-Transfer-Encoding: 8bit
Delivered-To: [EMAIL PROTECTED]

Hi,
a short on memory condition has caused the compiler abort. I have added some 
memory and it is working now.

Regards,
Gerhard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Reply via email to