public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank de Lange <frank@unternet.org>
To: David <david@kalifornia.com>
Cc: Chris Mason <mason@suse.com>,
	linux-kernel@vger.kernel.org, reiser@namesys.com
Subject: Re: reiserfs on 2.4.1,2.4.2-pre (with null bytes patch) breaks mozilla compile
Date: Sun, 18 Feb 2001 03:07:27 +0100	[thread overview]
Message-ID: <20010218030727.C13823@unternet.org> (raw)
In-Reply-To: <1217040000.982455419@tiny> <3A8F29C5.7000302@kalifornia.com>
In-Reply-To: <3A8F29C5.7000302@kalifornia.com>; from david@kalifornia.com on Sat, Feb 17, 2001 at 05:47:49PM -0800

On Sat, Feb 17, 2001 at 05:47:49PM -0800, David wrote:
> I can say "me too" for this.  I thought it was perhaps glibc or binutils 
> tho.  I only have reiserfs systems now so I don't have a basis for 
> comparison.
> 
> However I -can- say that I didn't experience this until I put glibc 
> 2.2.1 on my systems.  I do use an "approved" gcc, stock 2.95.2.
> 
> I wouldn't be so quick to pin it on reiserfs.

Well, I run glibc-2.2.1 as well, so that might be one of the factors
contributing to this. Then again, glibc-2.2.1 with ext2 does not cause any
problems whatsoever with mozilla. So it could be that reiserfs + glibc-2.2.1 is
a bad combination, question remains which of these two is the culprit (if not
both). Since glibc-2.2.2 is out, I will give that a try as well. Not tonight
though...

And no, I'm not running RedHat 7.x for those who might think so (and
automatically blame everything on it).

When did you switch to glibc-2.2.1? Were you running reiserfs before that?

Cheers//Frank

-- 
  WWWWW      _______________________
 ## o o\    /     Frank de Lange     \
 }#   \|   /                          \
  ##---# _/     <Hacker for Hire>      \
   ####   \      +31-320-252965        /
           \    frank@unternet.org    /
            -------------------------
 [ "Omnis enim res, quae dando non deficit, dum habetur
    et non datur, nondum habetur, quomodo habenda est."  ]

  reply	other threads:[~2001-02-18  2:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-17 16:21 reiserfs on 2.4.1,2.4.2-pre (with null bytes patch) breaks mozilla compile Frank de Lange
2001-02-18  0:16 ` Chris Mason
2001-02-18  1:47   ` David
2001-02-18  2:07     ` Frank de Lange [this message]
2001-02-18  2:18       ` David
2001-02-19 17:40         ` Frank de Lange
2001-02-18 17:10       ` Chris Mason
  -- strict thread matches above, loose matches on Subject: below --
2001-02-18  0:57 Frank de Lange
2001-02-18  1:10 ` Frank de Lange
2001-02-18 16:42   ` Chris Mason
2001-02-18  1:15 ` Frank de Lange
2001-02-18 17:47 Frank de Lange

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=20010218030727.C13823@unternet.org \
    --to=frank@unternet.org \
    --cc=david@kalifornia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=reiser@namesys.com \
    /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