From: Brian Gerst <bgerst@didntduck.org>
To: Rob <rob@hereintown.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compilation problems
Date: Tue, 27 Feb 2001 15:35:18 -0500 [thread overview]
Message-ID: <3A9C0F86.BA7D5723@didntduck.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0102271529380.967-100000@robsdigs.hereintown.net>
Rob wrote:
>
> gcc --version gives me pgcc-2.91.66
>
> I have a bootable 2.2.4 kernel I just can no longer recompile it for some
> reason.
IIRC, pgcc is known to be broken. Use standard gcc 2.91.66 or later.
--
Brian Gerst
next parent reply other threads:[~2001-02-27 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.30.0102271529380.967-100000@robsdigs.hereintown.net>
2001-02-27 20:35 ` Brian Gerst [this message]
2003-04-16 14:50 Compilation problems Ferry van Steen
-- strict thread matches above, loose matches on Subject: below --
2002-01-27 15:38 Tomasz Wegrzanowski
2002-01-27 16:09 ` Dave Jones
2001-02-27 20:06 Rob
2001-02-27 20:21 ` Brian Gerst
2001-02-27 20:24 ` Richard B. Johnson
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=3A9C0F86.BA7D5723@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@hereintown.net \
/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