From: Jochen Striepe <jochen@tolot.escape.de>
To: Jeff Chua <jeffchua@silk.corp.fedex.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: gcc-2.95.3
Date: Fri, 6 Apr 2001 09:30:18 +0200 [thread overview]
Message-ID: <20010406093018.B18157@tolot.escape.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0104060847200.965-100000@boston.corp.fedex.com>
In-Reply-To: <Pine.LNX.4.33.0104060847200.965-100000@boston.corp.fedex.com>; from jeffchua@silk.corp.fedex.com on Fri, Apr 06, 2001 at 08:49:51AM +0800
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
Hi,
On 06 Apr 2001, Jeff Chua <jeffchua@silk.corp.fedex.com> wrote:
>
> Does anybody have bad experience with gcc-2.95.3?
>
> I'm using gcc-2.95.2 with linux 2.4.3 and have no problem with it.
I'm using gcc-2.95.3 for kernel compilation on latest 2.4.x since it's
out. Never had any Problem.
Linux tolot 2.4.3 #1 Fri Mar 30 09:35:17 CEST 2001 i586 unknown
Gnu C 2.95.3
Gnu make 3.79.1
binutils 2.11.90.0.4
util-linux 2.11b
modutils 2.4.5
e2fsprogs 1.19
pcmcia-cs 3.0.14
PPP 2.4.0
isdn4k-utils 3.1pre1
Linux C Library 2.1.3
ldd: version 1.9.9
Procps 2.0.7
Net-tools 1.59
Kbd 0.99
Sh-utils 2.0.11
Modules Loaded nls_utf8 nls_iso8859-15 nls_iso8859-2
nls_iso8859-1 nls_cp852 nls_cp850 nls_cp437 floppy sr_mod sg isofs
ne2k-pci 8390 ide-cd cdrom adlib_card opl3 sb sb_lib uart401 sound
soundcore lp parport serial
Hth,
Jochen.
--
"I was gratified to be able to answer promptly, and I did. I said I
didn't know." -- Mark Twain
[-- Attachment #2: Type: application/pgp-signature, Size: 524 bytes --]
next prev parent reply other threads:[~2001-04-06 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 0:49 gcc-2.95.3 Jeff Chua
2001-04-06 1:08 ` gcc-2.95.3 Shawn Starr
2001-04-06 2:00 ` gcc-2.95.3 Mike Castle
2001-04-06 7:30 ` Jochen Striepe [this message]
2001-04-18 22:23 ` gcc-2.95.3 Dr. Kelsey Hudson
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=20010406093018.B18157@tolot.escape.de \
--to=jochen@tolot.escape.de \
--cc=jeffchua@silk.corp.fedex.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
all inboxes | Powered by JetHome®