xfs
[Top] [All Lists]

Re: file corruption during emacs build on XFS logical volume

To: Linux XFS <linux-xfs@xxxxxxxxxxx>
Subject: Re: file corruption during emacs build on XFS logical volume
From: Sean Neakums <sneakums@xxxxxxxx>
Date: Thu, 03 Jan 2002 23:45:47 +0000
In-reply-to: <6usn9nm3om.fsf@zork.zork.net> (Sean Neakums's message of "Thu, 03 Jan 2002 23:10:17 +0000")
Mail-followup-to: Linux XFS <linux-xfs@xxxxxxxxxxx>
References: <6u4rm4r53e.fsf@zork.zork.net> <1010013019.1281.6.camel@jen.americas.sgi.com> <6upu4spccv.fsf@zork.zork.net> <1010013997.1315.11.camel@jen.americas.sgi.com> <6ulmfgpau5.fsf@zork.zork.net> <6uheq4p9ny.fsf@zork.zork.net> <3C33AF81.AC235AD0@idcomm.com> <6ubsgbq013.fsf@zork.zork.net> <1010069377.23328.15.camel@jen.americas.sgi.com> <1010072382.23328.38.camel@jen.americas.sgi.com> <6u3d1npgx9.fsf@zork.zork.net> <1010075404.12080.79.camel@jen.americas.sgi.com> <1010076426.12080.86.camel@jen.americas.sgi.com> <6uu1u3nt3h.fsf@zork.zork.net> <1010087177.12080.104.camel@jen.americas.sgi.com> <6upu4rnquf.fsf@zork.zork.net> <1010088984.23328.115.camel@jen.americas.sgi.com> <1010097091.23328.117.camel@jen.americas.sgi.com> <6u3d1nnjsc.fsf@zork.zork.net> <6uwuyzm4du.fsf@zork.zork.net> <6usn9nm3om.fsf@zork.zork.net>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i386-debian-linux-gnu)
begin  Sean Neakums quotation:

> begin  Sean Neakums quotation:
>> begin  Sean Neakums quotation:
>>> begin  Steve Lord quotation:
>>>> OK, I was chasing different things, but emacs 21 is building OK for
>>>> me on xfs and ext3.
>>> This is very weird.  I find it hard to believe that there's
>>> something about Debian's packaging that causes the build to fail on
>>> XFS *only*.
>> Taking a cue from Sherlock Holmes, I've just kicked off a build of
>> the vanilla upstream source, to see if this is being triggered by
>> something in the way Debian's package does its build.
>
> The upstream build went perfectly, with the same configure options
> as the Debian package uses.  I'm composing a message to the
> maintainer, to see if he can tell me what's failing in the package
> build and why, and what is different about the way the build is
> handled in the package.

Aargh.  In the process of trying to create a log of the failed build
to send to the maintainer, instead of getting the errors I've quoted
before, I've gotten the error I orignally found: strip failing with a
`Memory exhausted' error.  I've run strings on the dumped binary, and
it's full of chunks of source, and cores immediately on startup.

Maybe I should just keep an ext2 partition around for building emacs
packages.

-- 
 /////////////////  |                  | The spark of a pin
<sneakums@xxxxxxxx> |  (require 'gnu)  | dropping, falling feather-like.
 \\\\\\\\\\\\\\\\\  |                  | There is too much noise.


<Prev in Thread] Current Thread [Next in Thread>