xfs
[Top] [All Lists]

Re: xfs_fsr broken again?

To: Juha K Kallio <bunnyh@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: xfs_fsr broken again?
From: Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 8 Oct 2002 10:21:59 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20021008081049.GA2018@xxxxxxxxxxxxxxxxxxxxxxxxxxx>; from bunnyh@xxxxxxxxxxxxxxxxxxxxxxxxxxx on Tue, Oct 08, 2002 at 10:10:49 +0200
References: <20021008065719.GA999@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20021008094316.A4351@xxxxxxxxxxxxxxxxxxxxxxxx> <20021008080615.GH13549@xxxxxxxxxxxxxxx> <20021008081049.GA2018@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On 08 Oct 2002 10:10:49 Juha K Kallio wrote:
On Tue, Oct 08, 2002 at 12:06:15AM -0800, Ethan Benson wrote:
> On Tue, Oct 08, 2002 at 09:43:16AM +0200, Christian Guggenberger wrote:
> > On 08 Oct 2002 08:57:19 Juha K Kallio wrote:
> > >Sorry, I just noticed that xfs_fsr was in xfsdump, not in xfsprogs.
So
> > >that should be it. But I ran into another problem when updating
> > >everything: I made a Debian package of attr with debuild, and it
made a
> > >very nice symlink /usr/lib/libattr.so -> /. The real lib seems to be
> > >missing from /usr/lib.
> > >
> > Hi,
> >
> > I have the same problems here on my debian/unstable box. According to

> > Nathan Scott the builds are fine on his box... maybe Nathan should
check
> > again?!
> > But I can build proper packages on a debian woody system....
> >
> > But you can use the latest xfsprogs, xfsdump and attr binary packages
from
> > debian/unstable, they contain the fixes Eric checked in last week.
>
> what does /bin/sh point to on your box?  this smells like evil
> bashisms in the xfsprogs build system, this would not show up on boxes
> using BloAtedSH as /bin/sh but would on boxes using a more purly posix
> shell such as debian's ash.
>
> --
> Ethan Benson
> http://www.alaska.net/~erbenson/


It points to bash, and the system is quite "debianish", no manual
hackings done. Yes, I'm using unstable



same here on my unstable box...




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