begin Steve Lord quotation:
> On Thu, 2002-01-03 at 10:30, Steve Lord wrote:
>> On Thu, 2002-01-03 at 09:56, Sean Neakums wrote:
>> > begin Steve Lord quotation:
>> > > Following up to myself, dropping the system memory to 128M seems to
>> > > have triggered the problem here, so yes there does seem to be an
>> > > XFS bug here.
>> > Excellent. I was beginning to think that it was something
>> > specific to my setup.
>> It gets even better, the other difference was that emacs was
>> already installed on the box were it worked, if I remove emacs it
>> fails to find it and fails in the same manner. So scratch memory
>> size as being the trigger here.
The box I was building on had emacs installed, showed consistent build
failure on XFS and consistent build success on ext2. However...
> However, a build of emacs on a box running ext3 filesystems and no
> emacs installed fails with exactly the same error. So it would
> appear to not be XFS related at all, and more of an emacs build
> Can you check out a build on another fs on a box which does not have
> emacs installed already? You could just rename your emacs binary
> rather than deinstall.
...I am building now on an ext2 volume, emacs removed.
(The build just passed the dump stage; src/emacs-21.1 is there and
src/temacs is not, as the make output indicates should be the case.)
Is there any chance that the mmap issue that Colin mentioned could be
cropping up on XFS, too? Since the emacs21 build has worked for me on
2.4.14-pre7 on an XFS volume, perhaps there were changes introduced or
a fix accidentally reversed during a merge with the Linus tree tha
might trigger this.
///////////////// | | The spark of a pin
<sneakums@xxxxxxxx> | (require 'gnu) | dropping, falling feather-like.
\\\\\\\\\\\\\\\\\ | | There is too much noise.