From: Dan Kegel <dkegel@ixiacom.com>
To: linux-kernel@vger.kernel.org
Subject: Status of compiling 2.4 with gcc3.1?
Date: Mon, 20 May 2002 13:46:52 -0700 [thread overview]
Message-ID: <3CE960BC.5858E63@ixiacom.com> (raw)
How far from wise is it to compile the 2.4.19-prex
kernel with gcc3.1? Is there a list of known issues?
Only report of trouble I've seen so far is
http://groups.google.com/groups?selm=linux.kernel.5.1.0.14.2.20020515015506.02749780%40pop.cus.cam.ac.uk
and that's just a compile-time fatal error building ntfs.
- Dan
next reply other threads:[~2002-05-20 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 20:46 Dan Kegel [this message]
2002-05-21 2:31 ` Status of compiling 2.4 with gcc3.1? Kurt Wall
2002-05-21 2:39 ` John Weber
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=3CE960BC.5858E63@ixiacom.com \
--to=dkegel@ixiacom.com \
--cc=linux-kernel@vger.kernel.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