Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	"linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	samba-technical
	<samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org>,
	xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org
Subject: Re: setfacl fix
Date: Mon, 18 Nov 2013 07:27:23 -0800	[thread overview]
Message-ID: <20131118152723.GA19649@infradead.org> (raw)
In-Reply-To: <CAH2r5mtXjnAOpKzZzta_yWDGyEPzR7h1wb0UW2pnoicm9Qsgxg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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
> 
> 
> 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.

> 
> 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)

  parent reply	other threads:[~2013-11-18 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-16  2:53 setfacl fix Steve French
     [not found] ` <CAH2r5msswZg_NvY9qMNknh2FWht1jMgwW1s2umtaBj3mHreDAw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-16  4:55   ` Jeremy Allison
2013-11-16 14:55   ` Christoph Hellwig
2013-11-16 15:15     ` steve
     [not found]       ` <1384614925.3216.6.camel-HkULYb+WTT7YCGPCin2YbQ@public.gmane.org>
2013-11-16 21:55         ` Steve French
     [not found]           ` <CAH2r5mvHzVXs4zuWZvL8ppBzaXSQHOykwu2Gdky3=ZQ9ZbPZcg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-18  8:05             ` AW: " Parzer, Peter
     [not found]     ` <20131116145507.GA22395-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-11-16 21:38       ` Steve French
     [not found]         ` <CAH2r5mtXjnAOpKzZzta_yWDGyEPzR7h1wb0UW2pnoicm9Qsgxg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-18 15:27           ` Christoph Hellwig [this message]
     [not found]             ` <20131118152723.GA19649-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-11-18 22:44               ` Dave Chinner
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=20131118152723.GA19649@infradead.org \
    --to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org \
    /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