From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay2.corp.sgi.com [137.38.102.29]) by oss.sgi.com (Postfix) with ESMTP id 0C88E7F37 for ; Wed, 13 Jan 2016 01:58:58 -0600 (CST) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay2.corp.sgi.com (Postfix) with ESMTP id DC663304062 for ; Tue, 12 Jan 2016 23:58:57 -0800 (PST) Received: from bombadil.infradead.org ([198.137.202.9]) by cuda.sgi.com with ESMTP id pzQhdEGUx07nc3z5 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 12 Jan 2016 23:58:56 -0800 (PST) Date: Tue, 12 Jan 2016 23:58:55 -0800 From: Christoph Hellwig Subject: Re: [PATCH 6/6] Add configure check for members of dirent for use in io/readdir.c Message-ID: <20160113075855.GG21939@infradead.org> References: <20160112200022.GG568@nyan> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20160112200022.GG568@nyan> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Felix Janda Cc: xfs@oss.sgi.com I think we're having a deeper issue here. For an LFS build we absolutely should have these values as the kernel dirent64 has them. Either we manage to not pull in the LFS version of readdir/getdents or musl is doing something inredibly stupid. Can you investigate if and why we're not using the LFS getdents64 here? _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs