mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chris Vandomelen <chrisv@b0rked.dhs.org>,
	Nerijus Baliunas <nerijus@users.sourceforge.net>,
	Guest section DW <dwguest@win.tue.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: Re[2]: cannot copy files larger than 40 MB from CD
Date: Thu, 2 Aug 2001 17:19:02 +0200	[thread overview]
Message-ID: <20010802171902.H6387@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.LNX.4.31.0107311656420.10245-100000@linux.local> <E15SKBL-0000qt-00@the-village.bc.nu>
In-Reply-To: <E15SKBL-0000qt-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Aug 02, 2001 at 04:14:39PM +0100

On Thu, Aug 02, 2001 at 04:14:39PM +0100, Alan Cox wrote:
> > > Tried vfat, ext2 and reiserfs.
> > >
> > > BTW, kernel is compiled with gcc-2.96-85, glibc-2.2.2-10 (RH 7.1) if
> >                                ^^^^^^^^^^^
> > > that matters.
> > 
> > Have you tried compiling your kernel using kgcc?
> > 
> > gcc-2.96.* is known to compile code incorrectly AFAIK, and shouldn't be
> > used for compiling kernels. (kgcc is egcs-1.1.2, I think.)
> 
> [x86 hat on]
> 
> egcs-1.1.2 aka kgcc wont build 2.4.7 it seems. gcc 2.96 >= 2.96.75 or so is
> just fine, gcc 2.95-2/3 is fine, gcc 3.0 seems to be doing the right thing

gcc 2.95.4 seem to be working too.


/David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2001-08-02 15:20 UTC|newest]

Thread overview: 13+ 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
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 [this message]
2001-08-02 16:05         ` Hugh Dickins
2001-08-03  8:15         ` bvermeul
     [not found] <Pine.LNX.4.10.10108010028220.18588-100000@coffee.psychology.mcmaster.ca>
2001-08-01  0:35 ` Nerijus Baliunas

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=20010802171902.H6387@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=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®