From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Steve French <smfrench@gmail.com>,
xfs@oss.sgi.com,
samba-technical <samba-technical@lists.samba.org>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: Re: setfacl fix
Date: Tue, 19 Nov 2013 09:44:26 +1100 [thread overview]
Message-ID: <20131118224426.GW6188@dastard> (raw)
In-Reply-To: <20131118152723.GA19649@infradead.org>
On Mon, Nov 18, 2013 at 07:27:23AM -0800, Christoph Hellwig wrote:
> On Sat, Nov 16, 2013 at 03:38:09PM -0600, Steve French wrote:
> > Makes sense to add a setfacl/getfacl test to xfstest and was trying to
> > build updated xfstests and look at what has changed but ran into a
> > strange error building xfstests and didn't see an obvious answer when
> > googling for it. Any idea how to workaround the build failure?
> >
> > Building src
> > [DEP]
> > [CC] dirstress
> > gcc: error: /lib64/libhandle.so: Too many levels of symbolic links
What's the circular link chain?
> > These are the steps I went through from a fairly clean Fedora 19 64
> > system before the make failure:
>
> No idea. Maybe some of the RedHat people on the xfs list have more
> experience with Fedora than I have.
Don't look at me - I use Debian for all my upstream stuff.... ;)
> > git clone git://oss.sgi.com/xfs/cmds/xfstests
> > git clone git://oss.sgi.com/xfs/cmds/xfsprogs
> > sudo yum install uuid-devel e2fsprogs-devel libuuid-devel
> > libattr-devel libacl-devel
> > cd xfsprogs
> > make
> > sudo make install-qa
> > cd ../xfstests
> > ./configure
> > make (which failed with the symlink error above)
Having the output of all the steps, especially the xfsprogs
install-qa step is probably going to be necessary to debug this. You
probably want to run "make Q= install-qa" so that it runs verbosely.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-18 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH2r5msswZg_NvY9qMNknh2FWht1jMgwW1s2umtaBj3mHreDAw@mail.gmail.com>
[not found] ` <20131116145507.GA22395@infradead.org>
[not found] ` <CAH2r5mtXjnAOpKzZzta_yWDGyEPzR7h1wb0UW2pnoicm9Qsgxg@mail.gmail.com>
2013-11-18 15:27 ` setfacl fix Christoph Hellwig
2013-11-18 22:44 ` Dave Chinner [this message]
2013-11-20 5:19 ` Eric Sandeen
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=20131118224426.GW6188@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox