osxfuse @3.5.0 build error

[Ryan Schmidt]

In addition to the other replies, another reason is dependencies. There are over a dozen ports that depend on osxfuse, so we need to offer osxfuse itself in MacPorts to be able to offer those other ports. 

> On Sep 24, 2016, at 20:18, Al Varnell <alvarnell at mac.com> wrote:
> 
> Sorry for my ignorance here, but why do we need MacPorts to maintain a port when there is are perfectly good installers available on GitHub <https://osxfuse.github.io> including a developer release of version 3.5.1 posted close to a week ago?
> 
> -Al-
> 
>> On Sat, Sep 24, 2016 at 11:45 AM, Ryan Schmidt wrote:
>> 
>>> On Sep 24, 2016, at 1:37 PM, Davide Liessi <davide.liessi at gmail.com> wrote:
>>> 
>>> 2016-09-24 20:17 GMT+02:00 Ryan Schmidt <ryandesign at macports.org>:
>>>> I'm not sure if that has anything to do with architecture mismatches; rather, it sounds like a perfectly normal bug in handling numbers of different sizes, that the developers of osxfuse should resolve.
>>> 
>>> But with my change the warning disappears,
>> 
>> In any case, it's a bug in osxfuse; please report the problem to the developers of osxfuse so they can fix it.
>> 
>> https://github.com/osxfuse/osxfuse/issues
>> 
>> 
>>> and the error for osxfuse
>>> @2.8.0 was directly related to the architecture mismatch (although I
>>> don't remember exactly what it was).
>>> So I think the error is somehow related to the architecture mismatch.
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users