public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David <david@kalifornia.com>
To: Frank de Lange <frank@unternet.org>
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: Sat, 17 Feb 2001 18:18:46 -0800	[thread overview]
Message-ID: <3A8F3106.6020107@kalifornia.com> (raw)
In-Reply-To: <1217040000.982455419@tiny> <3A8F29C5.7000302@kalifornia.com> <20010218030727.C13823@unternet.org>

> 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


Yes I was running reiserfs before 2.2.1 and I switched to 2.2.1 a couple 
months ago.  Since then I've been dealing with issues.  I've had to 
recompile half a dozen things similar to sendmail, apache etc.  They 
segfaulted.  It wasn't as purely backward compatible as expected.

I typically compile everything on one machine and distribute it.  Thus 
far everything has been ok save a few issues I haven't been able to pin 
down.  One of these issues is the inability to compile mozilla.  Also 
related, I can't recompile gcc 2.95.2.

All of these things I was able to do just fine before the changeover.  
To note, I used to cvs up mozilla and recompile it every few days.  I 
suppose I'll build an ext2 system and try things out.

Oh btw, I don't run That distribution either.

-d


  reply	other threads:[~2001-02-18  2:20 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
2001-02-18  2:18       ` David [this message]
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=3A8F3106.6020107@kalifornia.com \
    --to=david@kalifornia.com \
    --cc=frank@unternet.org \
    --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