State of FUSE on FreeBSD

[Nikolaus Rath]

On Aug 08 2017, Baptiste Daroussin <bapt at FreeBSD.org> wrote:
> On Thu, Aug 03, 2017 at 05:23:06PM +0200, Nikolaus Rath wrote:
>> On Aug 03 2017, Baptiste Daroussin <bapt at FreeBSD.org> wrote:
>> > On Thu, Aug 03, 2017 at 01:38:28PM +0200, Nikolaus Rath wrote:
>> >> Hello,
>> >> 
>> >> 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.
>> >> 
>> [...]
>> >> 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 :)
>> 
>> 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.
>> 
>> 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 only
> option, but I couldn't figure out what was doing it. Note that I can locally
> 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

-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«