From owner-freebsd-fs@freebsd.org Tue Aug 8 11:08:48 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3620DD4011 for ; Tue, 8 Aug 2017 11:08:48 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 760117FE26 for ; Tue, 8 Aug 2017 11:08:47 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3F56120A70 for ; Tue, 8 Aug 2017 07:08:46 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 08 Aug 2017 07:08:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=LdeiXde4TBS1RZWByDsBe9uRSGRZctxi/lsr4FKdqhg=; b=NK70MDfd U1zAOLo+EoQ+fZCxD1XpSY5Mj7mm3m8GG3TlJfiVhZYV/QqMVi7r6RNfFaFAuA/N 18DdQUHH7g/FFM0kUuqumhtFVG0tcW7EqdwYkB1sexj6QFwUr16h2sNTaHb51Ofc I+vL7PMnoTzJ+aRdIhtQTEv7u1Zc+0m7IWNFpAIyv1+jLmUHIUxWnekVfqML2KV5 aUubp0JnN40SrENTtVGnnSbttCIfCdOCOLFZ9zOZ2TatsYgDYGYnKF/kMVyOWjbl f1ndqxv+PXEYjMPFZndQKb/q6V8Tz6q0mIk0/yIGug7jAIBgwBJhOTkXOtKDfNIR 3WU9ZyrL+OQlNA== X-ME-Sender: X-Sasl-enc: uCTgrLYYZhLimr5U2+3uXl5wFUjj8+YmBCBUPUSLqBkU 1502190525 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id ECAA57E4EA for ; Tue, 8 Aug 2017 07:08:45 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id B57E03E79 for ; Tue, 8 Aug 2017 11:08:44 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id 10863102B9A; Tue, 8 Aug 2017 13:08:43 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <20170803115705.agsg6dm745dsriab@ivaldir.net> <87shh8ad5x.fsf@vostro.rath.org> <20170808080231.2chm2cz2qdcgvj2a@ivaldir.net> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Tue, 08 Aug 2017 13:08:43 +0200 In-Reply-To: <20170808080231.2chm2cz2qdcgvj2a@ivaldir.net> (Baptiste Daroussin's message of "Tue, 8 Aug 2017 10:02:31 +0200") Message-ID: <87valywc3o.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 11:08:48 -0000 On Aug 08 2017, Baptiste Daroussin wrote: > On Thu, Aug 03, 2017 at 05:23:06PM +0200, Nikolaus Rath wrote: >> On Aug 03 2017, Baptiste Daroussin wrote: >> > On Thu, Aug 03, 2017 at 01:38:28PM +0200, Nikolaus Rath wrote: >> >> Hello, >> >>=20 >> >> I am the upstream maintainer of libfuse. I'd like to refresh / improve >> >> the FreeBSD support in libfuse. My goal is for libfuse not to require >> >> any FreeBSD specific patches. >> >>=20 >> [...] >> >> Personally, I don't use FreeBSD and I don't have an easy way to test = on >> >> FreeBSD either. So I would appreciate any input. >> > >> > I can help you testing if you need, do not hesitate to bother me :) >>=20 >> Thanks for the pull request! I've merged it and applied some extra >> fixups on top that seemed right to me. It would be great if you could >> give it a shot. >>=20 >> Code is at https://github.com/libfuse/libfuse, master branch. > > Note that the pull request was made testing with meson+ninja, I bet this = is the > direction you are taking, (deprecating autotools?) Yes. > I got one issue left to build > out of box, something is generating a target which calls cp with GNU cp o= nly > option, but I couldn't figure out what was doing it. Note that I can loca= lly > patch it to use gcp (GNU cp from coreutils) if needed. > > But knowing what is generating it would be better so I can maybe patch it= to > have a compatible usage of cp ? Well, what option is it? I think the only usage of cp is for "building" the tests (which just involves copying the Python scripts). Currently this uses -fPu. Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB