From: Chris Mason <mason@suse.com>
To: Frank de Lange <frank@unternet.org>, linux-kernel@vger.kernel.org
Cc: 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 11:42:55 -0500 [thread overview]
Message-ID: <1304300000.982514575@tiny> (raw)
In-Reply-To: <20010218021050.A13823@unternet.org>
On Sunday, February 18, 2001 02:10:50 AM +0100 Frank de Lange
<frank@unternet.org> wrote:
>> At least the patch didn't make it worse. Would anyone care to comment on
>> how the elf-dynstr-gc option changes the file access patterns for the
>> compile?
>
> It does not change the file access patterns, it adds an extra step. A
> separate binary (dist/bin/elf-dynstr-gc, a convoluted version of strip)
> is run over the final (linked) library/executable to remove some symbol
> info. The elf-dynstr-gc program is compiled as part of the mozilla build.
> There's nothing wrong with elf-dynstr-gc on the reiserfs filesystem, it
> is identical to the one on the ext2 partition. Running the 'reiserfs'
> version on the ext2 tree works as it should, running the ext2 version on
> the reiserfs tree crashes (seems the program is not very robust, as it
> does not detect garbled input files). As said, running objdump on the
> corrupted (reiserfs compiled) library also produces errors.
Great, that will help narrow things down. Please run the elf-dynstr-gc
program under strace, on top of both the ext2 and reiserfs trees, and send
the results (privately, they'll probably be large) to me.
-chris
next prev parent reply other threads:[~2001-02-18 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 0:57 reiserfs on 2.4.1,2.4.2-pre (with null bytes patch) breaks mozilla compile Frank de Lange
2001-02-18 1:10 ` Frank de Lange
2001-02-18 16:42 ` Chris Mason [this message]
2001-02-18 1:15 ` Frank de Lange
-- strict thread matches above, loose matches on Subject: below --
2001-02-18 17:47 Frank de Lange
2001-02-17 16:21 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
2001-02-19 17:40 ` Frank de Lange
2001-02-18 17:10 ` Chris Mason
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=1304300000.982514575@tiny \
--to=mason@suse.com \
--cc=frank@unternet.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.