public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drnj at redherring dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/27675] Compiler crash building PHP component
Date: Mon, 21 Aug 2006 09:28:00 -0000	[thread overview]
Message-ID: <20060821092843.24161.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27675-12709@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from drnj at redherring dot co dot uk  2006-08-21 09:28 -------
Subject: Re:  Compiler crash building PHP component

Swap space problem in NSLU2 linux based system - not a compiler bug. 
Appologies for not feeding that back sooner



On 21 Aug 2006 05:31:59 -0000, "pinskia at gcc dot gnu dot org" <gcc-
bugzilla@gcc.gnu.org> wrote :

> 
> 
> ------- Comment #3 from pinskia at gcc dot gnu dot org  2006-08-21 
05:31 -------
> No feedback in 3 months.
> 
> 
> -- 
> 
> pinskia at gcc dot gnu dot org changed:
> 
>            What    |Removed                     |Added
> -------------------------------------------------------------------------
---
>              Status|WAITING                     |RESOLVED
>          Resolution|                            |INVALID
> 
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27675
> 
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
> 
> 
> 


-- 


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


      parent reply	other threads:[~2006-08-21  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  5:33 [Bug c/27675] New: " drnj at redherring dot co dot uk
2006-05-19  5:40 ` [Bug c/27675] " pinskia at gcc dot gnu dot org
2006-05-19  5:40 ` pinskia at gcc dot gnu dot org
2006-08-21  5:32 ` pinskia at gcc dot gnu dot org
2006-08-21  9:28 ` drnj at redherring dot co dot uk [this message]

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=20060821092843.24161.qmail@sourceware.org \
    --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).