public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjoerd-gcc at linuxonly dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29948]  New: G++ OOM's when compiling kmail
Date: Wed, 22 Nov 2006 22:20:00 -0000	[thread overview]
Message-ID: <bug-29948-13607@http.gcc.gnu.org/bugzilla/> (raw)

When compiling kmail with Debian's dpkg-buildpackage, cc1plus is killed by the
kernel due to memory shortage. This shows when using either g++ 4.0 or 4.1.

Files (including .ii files) are on the following URL:
http://errors.linuxonly.nl/gcc/

G++ version: 
g++-4.0 (GCC) 4.0.4 20060904 (prerelease) (Debian 4.0.3-7)
g++ (GCC) 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)
System type: Linux sjord 2.6.15-1-amd64-k8 #2 Wed Jan 4 06:25:54 CET 2006
x86_64 GNU/Linux
Compiling file: libkmailprivate_la.all_cpp.cpp


-- 
           Summary: G++ OOM's when compiling kmail
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sjoerd-gcc at linuxonly dot nl
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29948


             reply	other threads:[~2006-11-22 22:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 22:20 sjoerd-gcc at linuxonly dot nl [this message]
2006-11-22 22:24 ` [Bug c++/29948] " pinskia at gcc dot gnu dot org
2006-11-22 22:27 ` sjoerd-gcc at linuxonly dot nl
2007-01-29 21:59 ` n dot escuder at intra-links dot com
2007-02-05 21:12 ` sliedes at cc dot hut dot fi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29948-13607@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).