public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/8971: [Tru64 4.0] virtual memory exhausted: Not enough space
Date: Sat, 17 May 2003 09:16:00 -0000 [thread overview]
Message-ID: <20030517091600.31166.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/8971; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: bootstrap/8971: [Tru64 4.0] virtual memory exhausted: Not enough space
Date: Sat, 17 May 2003 02:06:20 -0700 (PDT)
--- Ingolf Knopf <iknopf@csc-dd.de> wrote:
> From: Ingolf Knopf <iknopf@csc-dd.de>
> To: Dara Hazeghi <dhazeghi@yahoo.com>
> Subject: Re: bootstrap/8971: [Tru64 4.0] virtual
> memory exhausted: Not enough space
> Date: Thu, 15 May 2003 08:20:27 +0200
>
> Am Mittwoch, 14. Mai 2003 19:13 schrieben Sie:
> > > I've found in a FAQ-list, which kernel parameter
> I
> > > should change to compile
> > > gcc. Now I have a running gcc-3.2.2.
> > > The changed kernel-parameter (from
> > > /etc/sysconfigtab):
> >
> > Glad you succeeded. Does that mean we can close
> this
> > bug report then (ie all the necessary information
> was
> > in the documentation)? Thanks,
> >
> > Dara
> >
> > __________________________________
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo.
> > http://search.yahoo.com
>
> yes, you can.
> Ingolf.
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
next reply other threads:[~2003-05-17 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 9:16 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 10:49 giovannibajo
2003-05-14 10:06 Dara Hazeghi
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=20030517091600.31166.qmail@sources.redhat.com \
--to=dhazeghi@yahoo.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).