On Thu, 2002-01-03 at 13:16, Sean Neakums wrote:
> 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...
For me it was consistent success with emacs installed, consistent
failure with emacs removed. This was independent of filesystem type,
ext3 failed in exactly the same manner as xfs.
The failure looked like this:
cd lisp && make EMACS="emacs"
make: Entering directory `/usr/src/redhat/BUILD/emacs-20.7/gnus-5.8.8/lisp'
rm -f *.elc
W3DIR=no lispdir=/var/tmp/emacs-20.7-root/usr/share/emacs/site-lisp srcdir=.
emacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-compile
/bin/sh: emacs: command not found
make: *** [all] Error 127
make: Leaving directory `/usr/src/redhat/BUILD/emacs-20.7/gnus-5.8.8/lisp'
make: *** [lick] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.26560 (%install)
And this is on a machine which build emacs correctly when an emacs
package was installed.
> > 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
> > issue.
> > 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.
If you look at the failure output, are you getting a message saying the
command emacs was not found? A few lines up in the output it is setting
this is the path on my machine, the first of those directories has an
emacs binary in it. I do not know why it does not find it though, and as
I said, for me, it does not matter which fs type I am using, if I have
emacs packages installed it finds the binary and works.
> ///////////////// | | The spark of a pin
> <sneakums@xxxxxxxx> | (require 'gnu) | dropping, falling feather-like.
> \\\\\\\\\\\\\\\\\ | | There is too much noise.
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx