After the MacPorts update to osxfuse 2.8.0, I get this on 10.10.5:
:notice:build ---> Building osxfuse
:debug:build Executing org.macports.build (osxfuse)
:debug:build Environment:
CC_PRINT_OPTIONS='YES'
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.
Never mind. I realized it was a stray outgoing firewall rule that was
blocking it for terminal apps. Sorry. Ignore.
Art
On Sat, May 30, 2015 at 2:38 AM, Art McGee wrote:
> This is supposed to be fixed:
>
> https://trac.macports.org/ticket/47724
>
> But I still get this:
>
This is supposed to be fixed:
https://trac.macports.org/ticket/47724
But I still get this:
:debug:extract Executing proc-post-org.macports.extract-extract-0
:info:extract Cloning into 'test'...
:info:extract fatal: unable to access '
http://anongit.freedesktop.org/git/poppler/test/': Couldn't re
Terry Barnum wrote:
> The freeswitch devs are updating the Mac section of their wiki and are
> claiming that homebrew is more widely supported between platforms. They are
> reluctant to add information on using macports for freeswitch dependencies
> because a) they don't want to support what the
Command output:
sudo port install clex
---> Computing dependencies for clex
---> Fetching archive for clex
---> Attempting to fetch clex-4.6.patch6_0.darwin_13.x86_64.tbz2 from
http://packages.macports.org/clex
---> Attempting to fetch clex-4.6.patch6_0.darwin_13.x86_64.tbz2 from
http://mse.uk
> I understand why installing in /usr/local can mess up macports, but
> macports doesn't have everything, and most third-party software wants to go
> into /usr/local. Where should this stuff go, if not /usr/local?
>
Actually, I don't think there is that much of a problem with installing
software i
gt; On Tue, Feb 11, 2014 at 4:12 PM, Art McGee wrote:
>
>> They keep their environment segregated from the rest of the system, and
>> because of this, even though any MacPorts admin will strongly and
>> vehemently advise against even trying it, they can work in concert with
&
gregated from the rest of the system, and because of this,
even though any MacPorts admin will strongly and vehemently advise against
even trying it, they can work in concert with each other.
Yes, you can delete Ghostscript from Homebrew and it won't destroy anything
in MacPorts, but the bigg
Yep, did that, same result. If this were happening with other ports I'd
think it was my macports setup or my system, but this only happens with
crafty.
Art
On Tue, Nov 12, 2013 at 4:55 AM, Ryan Schmidt wrote:
> On Nov 12, 2013, at 06:50, Art McGee wrote:
>
> > Unable to compil
Unable to compile crafty. Running 5.0.1 and 10.9 now, but had the same
problem with 5.0 and 10.8. Log attached.
crafty.log
Description: Binary data
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/
10 matches
Mail list logo
