mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Vandomelen <chrisv@b0rked.dhs.org>
To: Nerijus Baliunas <nerijus@users.sourceforge.net>
Cc: Guest section DW <dwguest@win.tue.nl>, <linux-kernel@vger.kernel.org>
Subject: Re: Re[4]: cannot copy files larger than 40 MB from CD
Date: Tue, 31 Jul 2001 17:17:17 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.31.0107311708450.10245-100000@linux.local> (raw)
In-Reply-To: <200108010004.CAA1062359@mail.takas.lt>

> On Tue, 31 Jul 2001 16:58:06 -0700 (PDT) Chris Vandomelen <chrisv@b0rked.dhs.org> wrote:
>
> CV> > Tried vfat, ext2 and reiserfs.
> CV> >
> CV> > BTW, kernel is compiled with gcc-2.96-85, glibc-2.2.2-10 (RH 7.1) if
> CV>                                ^^^^^^^^^^^
> CV> > that matters.
> CV>
> CV> Have you tried compiling your kernel using kgcc?
>
> No.
>
> CV> gcc-2.96.* is known to compile code incorrectly AFAIK, and shouldn't be
> CV> used for compiling kernels. (kgcc is egcs-1.1.2, I think.)
>
> As I remember Alan said recent 2.4 kernels should be compiled with gcc 2.95
> or 2.96 (preferably?).

Everything that I've seen recommends egcs-1.1.2. The kernel documentation
(linux/Documentation/Changes) recommends that version of egcs, as do some
list messages around 12/00.

Chris



  reply	other threads:[~2001-08-01  0:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31 22:37 Nerijus Baliunas
     [not found] ` <20010801012719.A11060@win.tue.nl>
2001-07-31 23:44   ` Re[2]: " Nerijus Baliunas
2001-07-31 23:58     ` Chris Vandomelen
2001-08-01  0:03       ` Re[4]: " Nerijus Baliunas
2001-08-01  0:17         ` Chris Vandomelen [this message]
2001-08-01  0:25           ` Re[6]: " Nerijus Baliunas
2001-08-01  8:55             ` bvermeul
2001-08-01  4:19         ` Re[4]: " Bill Pringlemeir
2001-08-02 15:14       ` Re[2]: " Alan Cox
2001-08-02 15:19         ` David Weinehall
2001-08-02 16:05         ` Hugh Dickins
2001-08-03  8:15         ` bvermeul

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=Pine.LNX.4.31.0107311708450.10245-100000@linux.local \
    --to=chrisv@b0rked.dhs.org \
    --cc=dwguest@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nerijus@users.sourceforge.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

all inboxes | Powered by JetHome®