Re: Can brew and port be used on the same system?

[Al Varnell]

I'm told it can be done now, but can get messy. I gave up on brew several years 
ago. Too many conflicts back then.

Sent from Janet's iPad

-Al-
-- 
Al Varnell
Mountain View, CA

On May 27, 2017, at 7:13 PM, Michael  wrote:
> So apparently the open source code version of Jedi Knights Academy and 
> Outcast https://github.com/JACoders/OpenJK rely on brew's SDL 2, and have 
> that installation pathname in their binaries.
> 
> Can I install brew, with its use of /usr/local/, at the same time as ports?
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: 10.6.8 and ffmpeg

[Al Varnell]

On Nov 2, 2016, at 8:43 PM, Ryan Schmidt wrote:
> On Nov 2, 2016, at 10:41 PM, Al Varnell wrote:
>> On Nov 2, 2016, at 8:38 PM, Brandon Allbery wrote:
>>> On Wed, Nov 2, 2016 at 11:37 PM, Al Varnell wrote:
>>> Most users don't have access to Apple's developer download site and cannot 
>>> be expected to pay $99 to be able to do so.
>>> 
>>> Um? $99 is only if you want signing certificates. The Mac Developer 
>>> subscription granting access to downloads is free.
>> 
>> Last time I checked Apple had done away with all new free subscriptions. 
>> Have they reinstated them?
> 
> This is the first I'm hearing about that. Can you provide further 
> information? Citation?

When I first heard about it, over a year ago, I tried to sign my wife up and 
the only thing offered for free was Safari Extension developement and that free 
program was dropped at the same time as they reorganized the entire Development 
program a few months back.

-Al-
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: 10.6.8 and ffmpeg

[Al Varnell]

On Nov 2, 2016, at 8:38 PM, Brandon Allbery wrote:
> On Wed, Nov 2, 2016 at 11:37 PM, Al Varnell wrote:
> Most users don't have access to Apple's developer download site and cannot be 
> expected to pay $99 to be able to do so.
> 
> Um? $99 is only if you want signing certificates. The Mac Developer 
> subscription granting access to downloads is free.

Last time I checked Apple had done away with all new free subscriptions. Have 
they reinstated them?

-Al-___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: 10.6.8 and ffmpeg

[Al Varnell]

On Nov 2, 2016, at 8:14 PM, Ken Cunningham wrote:
>> Why would you do that? It can be downloaded from the Apple developer web 
>> site (in a newer version of Xcode).
> 
> Well, everyone seems to feel it’s way to difficult to expect a user to do 
> that, so I’m trying to help you come up with an easier way.
> 
> Of course, I just downloaded the darned thing myself, and I don’t see why 
> that is too much to expect everyone else to do…

Most users don't have access to Apple's developer download site and cannot be 
expected to pay $99 to be able to do so.


Sent from Janet's iPad

-Al-
-- 
Al Varnell
Mountain View, CA___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

sea.us.rsync.macports.org mirror

[Al Varnell]

On Aug 22, 2016, at 5:25 PM, Lawrence Velazquez wrote:
> On Aug 22, 2016, at 3:41 PM, Jonathan Stickel wrote:
> >
> > OK, thanks. Maybe put a note on the wiki until resolved?
> 
> Done: 
> https://trac.macports.org/wiki/Mirrors?action=diff&version=85
> 
> vq

I found it to be back on-line after re-checking the wiki today.


-Al-
-- 
Al Varnell
Mountain View, CA

smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Al Varnell]

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 
 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  wrote:
>> 
>> 2016-09-24 20:17 GMT+02:00 Ryan Schmidt :
>>> 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.


smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: MacPorts missing links

[Al Varnell]

On Sep 12, 2016, at 8:23 PM, Lawrence Velázquez  wrote:

>> I would also encourage somebody to look into the need for both Xcode and 
>> Command Line Tools since Xcode 7. Apple makes it quite clear on the download 
>> page that Xcode now contains the CLTs, so installing both might well cause 
>> issues and clearly waste valuable space.
> 
> Some stubborn build systems look for stuff in /usr/include and similar 
> locations and complain if they don't exist. If anything, working on the 
> inverse configuration (CLT only, no Xcode) would be a better use of time.

Thanks for clearing that up (hard coding, that is) and I agree with you that 
CLT only is a better use of time. I have been operating that way for the last 
couple of years and have yet to run into a port that I need which actually 
required Xcode, but maybe I’ve just been lucky. I see that 
https://trac.macports.org/ticket/29172 has been there for five years now, so I 
won’t hold my breath until it happens.

-Al-
-- 
Al Varnell
Mountain View, CA






smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: MacPorts missing links

[Al Varnell]

Perhaps the Wiki page needs to state more clearly that this only needs to be 
done for major OS X/macOS upgrades, that is from 10.11.x to 10.12, for 
instance. In all the years I've been using MacPorts I have never needed to 
reinstall the MacPorts base for a minor upgrade.

I would also encourage somebody to look into the need for both Xcode and 
Command Line Tools since Xcode 7. Apple makes it quite clear on the download 
page that Xcode now contains the CLTs, so installing both might well cause 
issues and clearly waste valuable space.

Sent from Janet's iPad

-Al-

On Sep 12, 2016, at 7:15 PM, Ryan Schmidt wrote:
> Officially, per the Migration wiki page, when you upgrade to a new version of 
> macOS, you should install the latest Xcode and command line tools and 
> reinstall MacPorts base. Those steps aren't optional.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports fails to build in macOS 10.12 Sierra

[Al Varnell]

Although that is in fact what happened, it was more because thousands of public 
beta users chose to ignore the NDA, probably because they didn't really read or 
understand it. Apple hosts on the Apple Support Community Forum were quick to 
delete all postings in violation, but that was really the only thing they 
control. Far too many e-mail lists and blogs to monitor and not enough lawyers 
to shut them down, even if they wanted to. Apple seems willing to accept a few 
violations in exchange for a broader testbed.

Sent from Janet's iPad

-Al-

On Sun, Jun 19, 2016 at 08:52 PM, Jeremy Huddleston Sequoia wrote:
> 
> Also note that in the past, such restrictions loosened once the first public 
> beta was made available, so it's possible that such open discussion will be 
> ok once that happens.


smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports fails to build in macOS 10.12 Sierra

[Al Varnell]

Unless somebody can show that Apple announced at WWDC the results of attempting 
to migrate MacPorts to Sierra, then no, it does not allow a discussion such as 
this. The exemption was only meant to cover Sierra capabilities announced at 
WWDC, not the results of actually using it, including what may or may not be 
working in an early Developer Preview.

That being said, I was under the impression that before we can attempt to 
migrate from an older OS, we must wait for MacPorts to release a Sierra version 
of the MacPorts installation package. That's what I have always done in the 
past, but I don't recall how long it took to get such a package put together 
after a new OS X was announced. 

Sent from Janet's iPad

-Al-

On Jun 18, 2016, at 8:44 PM, Mark Anderson wrote:
> Doesn't this exception cover the asked question?
> 
> Further, Apple agrees that You will not be bound by the foregoing 
> confidentiality terms with regard to technical information about pre-release 
> Apple Software and services disclosed by Apple at WWDC (Apple’s Worldwide 
> Developers Conference), except that You may not post screen shots, write 
> public reviews or redistribute any pre-release Apple Software or services.
> 
> Mark
> 
> On Sat, Jun 18, 2016 at 11:24 PM, Jeremy Huddleston Sequoia wrote:
> As a reminder, macOS 10.12 Sierra has only been released as a developer 
> preview to developers and is covered by an NDA.  Please do not discuss it on 
> this list.  If you have issues, please feel free to reach out to me directly.
> 
> In this case, you forgot to install the Xcode command line tools
> 
> Thanks,
> Jeremy
> 
> > On Jun 15, 2016, at 13:09, Artemio González López wrote:
> >
> > I’ve installed the Developer preview of macOS 10.12 Sierra, and I have been 
> > trying to rebuild my MacPorts installation following the Migration 
> > instructions at MacPorts. The problem is that ./configure —enable-readline 
> > fails with the error message found at the end of the complete output of 
> > this command below). I of course know that I am using a beta system, so 
> > that I’m not entitled to any support from the MacPorts team. However, I 
> > would really appreciate any pointers as to how to fix this (if  possible).
> >
> > Thanks a lot,
> >
> > Artemio
> >
> > mba:~/Downloads/mports/trunk/base artemio$ ./configure --enable-readline
> > checking build system type... x86_64-apple-darwin16.0.0
> > checking host system type... x86_64-apple-darwin16.0.0
> > checking target system type... x86_64-apple-darwin16.0.0
> > checking MacPorts version... 2.3.99
> > checking for sw_vers... /usr/bin/sw_vers
> > checking for defaults... /usr/bin/defaults
> > checking for xcode-select... /usr/bin/xcode-select
> > checking Mac OS X version... 10.12
> > checking Xcode location... /Applications/Xcode.app/Contents/Developer
> > checking Xcode version... 7.3.1
> > checking for clang... clang
> > checking whether the C compiler works... yes
> > checking for C compiler default output file name... a.out
> > checking for suffix of executables...
> > checking whether we are cross compiling... no
> > checking for suffix of object files... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether clang accepts -g... yes
> > checking for clang option to accept ISO C89... none needed
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether ln -s works... yes
> > checking whether make sets $(MAKE)... yes
> > checking for clang... clang
> > checking whether we are using the GNU Objective C compiler... yes
> > checking whether clang accepts -g... yes
> > checking for bsdmake... no
> > checking for pmake... no
> > checking for bzip2... /usr/bin/bzip2
> > checking for bzr... no
> > checking for chown... /usr/sbin/chown
> > checking for cp... /bin/cp
> > checking for cpio... /usr/bin/cpio
> > checking for cvs... no
> > checking for diff... /usr/bin/diff
> > checking for dscl... /usr/bin/dscl
> > checking for dseditgroup... /usr/sbin/dseditgroup
> > checking for file... /usr/bin/file
> > checking for find... /usr/bin/find
> > checking for git... /usr/bin/git
> > checking for gnumake... /usr/bin/gnumake
> > checking for gnupatch... no
> > checking for gpatch... no
> > checking for gnutar... no
> > checking for gtar... no
> > checking for gzip... /usr/bin/gzip
> > checking for hdiutil... /usr/bin/hdiutil
> > checking for hg... no
> > checking for launchctl... /bin/launchctl
> > checking for lipo... /usr/bin/lipo
> > checking for lsbom... /usr/bin/lsbom
> > checking for lzma... no
> > checking for make... /usr/bin/make
> > checking for man... /usr/bin/man
> > checking for mdfind... /usr/bin/mdfind
> > checking for mdls... /usr/bin/mdls
> > checking for mkbom... /usr/bin/mkbom
> > checking for mtree... /usr/sbin/mtree
> > checking for open... /usr/bin/open
> > checking for openssl... /usr/bin/openssl
> > checking for patch... /usr/bin/patch
> > checking for pax... /bin/pax
> > checking for rmdir... /bin/rmdir
> > c

Re: port terminates under OS X 10.11.4

[Al Varnell]

The change to Darwin 15.0.0 occurred with the release of OS X 10.11 in 
September of last year.  Yesterday it was updated to Darwin 15.4.0 with OS X 
10.11.4.  That should not have produced that error at this time.
>

-Al-

On Tue, Mar 22, 2016 at 09:43 PM, Carlo Tambuatco wrote:
> I also upgraded to 11.4 from 11.3 this afternoon and also upgraded all my 
> macports after upgrading XCode command line tools to Darwin Kernel Version 
> 15.4.0 and encountered no problems at all.
> 
> XCode is still 7.0, though.
> 
>> On Mar 22, 2016, at 11:29 PM, Brandon Albert wrote:
>> On Tue, Mar 22, 2016 at 10:50 PM, Merton Campbell Crockett wrote:
>> I upgraded to OS X 10.11.4 this afternoon.  Also, I upgraded Xcode to Xcode 
>> 7.3.  I thought that I should check for any MacPorts updates and encountered 
>> the following error.
>> 
>> Error: Current platform "darwin 15" does not match expected platform "darwin 
>> 14"
>> Error: If you upgraded your OS, please follow the migration instructions: 
>> https://trac.macports.org/wiki/Migration 
>>  
>> OS platform mismatch
>> while executing
>> "mportinit ui_options global_options global_variations"
>> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform 
>> mismatch
>> 
>> It seems strange that the Darwin version would change with OS X 10.11.4.  
>> Have I just been “lucky” with using the port command since upgrading to OS X 
>> 10.11?
>> 
>> You've been lucky, yes; past OS upgrades without following the Migration 
>> steps have led to lots of pain for people, as applications continue to work 
>> but libraries can end up quite broken.
>> You need to do more than just reinstall MacPorts base, unless you want to 
>> end up with an impossible mess.
>> 
>> -- 
>> brandon



smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users