Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

[Ryan Schmidt]

> On Nov 3, 2016, at 9:10 AM, Ken Cunningham  
> wrote:
> 
> (Why is this not coming to you as a prebuilt binary from the buldbots, I 
> wonder?)

The gmp portfile explains why this is so:


# Prevent precompiled binaries.
# See #41614.
# might not be needed if we decide to add:
#default_variants +core2
archive_sites


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

Re: 10.6.8 and ffmpeg

[Ryan Schmidt]

> On Nov 2, 2016, at 10:49 PM, Al Varnell <alvarn...@mac.com> wrote:
> 
> 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.

https://developer.apple.com/support/compare-memberships/

"If you’re looking to develop apps for Apple platforms, download the Xcode 
developer tools, SDKs, and resources for free on the Xcode downloads page. 
Program membership is not required. If you don’t already have an Apple ID, you 
can create one here."




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

Re: 10.6.8 and ffmpeg

[Ryan Schmidt]

> 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?

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

Re: 10.6.8 and ffmpeg

[Ryan Schmidt]

> On Nov 2, 2016, at 10:11 PM, Ken Cunningham  
> wrote:
> 
>> That's just:
>> 
>> #if MAC_OS_X_VERSION_MAX_ALLOWED < 1070
>> # error SDL for Mac OS X must be built with a 10.7 SDK or above.
>> #endif /* MAC_OS_X_VERSION_MAX_ALLOWED < 1070 */
>> 
> 
> that’s what I meant when I referred to using availability macros - sorry if 
> it was the wrong term.
> 
> Mojca did an extensive dissection of the process in the trac ticket, trying a 
> number of such things
> 
> https://trac.macports.org/ticket/52210
> 
> I haven’t dug into it like she has …
> 
> 
> Can I just distribute a 10.7SDK from a weblink?

No.

> I suppose I'd get a call from Apple Legal if I did that ..?

Yes.

Why would you do that? It can be downloaded from the Apple developer web site 
(in a newer version of Xcode).

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

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

[Ryan Schmidt]

> On Nov 2, 2016, at 5:48 PM, Murray Eisenberg  
> wrote:
> 
> After upgrading from OS X El Capitan to macOS Sierra (10.12.1), I’m following 
> the migration steps at https://trac.macports.org/wiki/Migration .
> 
> Got to step 3. e and after downloading script restore_ports.tcl and making it 
> executable, I executed:
> 
>sudo ./restore_ports.tcl myports.txt
> 
> Output:
> 
> Warning: Skipping p5.16-module-corelist (not in the ports tree)
> Warning: Skipping p5.20-module-corelist (not in the ports tree)
> Warning: Skipping p5.22-module-corelist (not in the ports tree)
> Error: we appear to be stuck, exiting...
> infinite loop
> while executing
> "sort_ports $portList"
> invoked from within
> "set operationList [sort_ports $portList]"
> (file "./restore_ports.tcl" line 285)
> 
> Help!!   
> 
> I’d certainly prefer NOT to have to restore all my ports (from list saved in 
> myports.txt) manually, one-by-one.
> 
> Any ideas?

Well, the warnings shown above are correct, there is no port 
p5.16-module-corelist in the ports tree at this time.

https://www.macports.org/ports.php?by=name=corelist

If those are listed in your myports.txt, try removing them.

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

Re: GitHub migration complete

[Ryan Schmidt]

> On Oct 31, 2016, at 4:18 AM, René J. V. Bertin  wrote:
> 
> Clemens Lang wrote:
> 
>> If your question is not yet answered, ask on the mailing lists so it can
>> be added.
> 
> I may have overlooked this, but does github have any provisions that would 
> allow 
> the PortIndex files to be generated on the server and served with the actual 
> repo 
> contents? That would probably give a very significant reduction in the 
> resources 
> spent collectively to regenerate those files...

This issue only affects the very small percentage of the MacPorts user 
population (including developers and maintainers) that clones the git 
repository. Most users will use the rsync server, on which we do generate 
portindexes for each macOS version.

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

Re: GitHub migration complete

[Ryan Schmidt]

> On Oct 30, 2016, at 10:28 PM, Carlo Tambuatco  wrote:
> 
> Is that mailto link macports-users@lists.macosforge.org in the signature 
> still valid…?

Yes, our previous mailing lists have not moved yet. And even when they do, the 
old addresses will remain valid.

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

Re: 10.6.8 and ffmpeg

[Ryan Schmidt]

> On Oct 29, 2016, at 5:32 PM, David Evans  wrote:
> 
> On 10/28/16 9:58 PM, Richard L. Hamilton wrote:
>> Am I right in thinking that  ffmpeg now requires libsdl2 while it previously 
>> required libsdl?  That causes ffmpeg to fail on 10.6.x, because libsdl2 
>> fails:
>> 
>> Error: org.macports.fetch for port libsdl2 returned: Building libsdl2 
>> requires OS X 10.7 SDK or later
>> Error: Failed to install libsdl2
>> Please see the log file for port libsdl2 for details:
>>
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/main.log
>> Error: The following dependencies were not installed: libsdl2
>> Error: Unable to upgrade port: 1
>> To report a bug, follow the instructions in the guide:
>>http://guide.macports.org/#project.tickets
>> 
> 
> Yep, it was a recent upstream decision to remove support for sdl1 and replace 
> it with sdl2.  Their rationale is that
> sdl2 is the mainstream version of the library and sdl has not been maintained 
> since about 2012. With the 3.2 release
> this effects both ffmpeg and ffmpeg-devel.  See 
> http://ffmpeg.org/index.html#news for the announcement.
> 
> Our choice then is to upgrade the port and go with sdl2 or stick with sdl and 
> never upgrade the port again.  We chose
> follow ffmpeg's update path.  But you could choose not to update locally and 
> stay with the ffmpeg <= 3.1.5 which only
> supports sdl (not sdl2).  This is probably a better way to go than trying to 
> shoehorn the 10.7 SDK into a 10.6
> environment.  Or if you're going to do that why not update to 10.7 or better.

There are Macs that cannot update to 10.7 or later, but which might still be 
viable as audio/video playing machines.

Requiring sdl2 in ffmpeg kinda sucks because now a lot of ports that use ffmpeg 
that worked fine on Snow Leopard don't anymore, including pianobar. I just 
finally convinced the pianobar developers to add a compatibility getline 
function so that it can build on Snow Leopard again, and now ffmpeg's sdl2 
requirement makes it not work on Snow Leopard again.

If sdl2 can be built on Snow Leopard using a copy of the 10.7 SDK obtained from 
a later Xcode, and that sdl2 then works ok on Snow Leopard, then I'd be happy 
if we could come up with an official way to support that, and then we could do 
that on the buildbot, which would cover a lot of users' needs.

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

Re: 10.6.8 and ffmpeg

[Ryan Schmidt]

> On Oct 29, 2016, at 12:05 AM, Ken Cunningham 
>  wrote:
> 
> libsdl2 will build without trouble on 10.6.8 if you find a copy of the 10.7 
> SDK and put it like so in /Developer/SDKs/MacOSX10.7.sdk

That is not a procedure we have ever recommended users do before. I know that 
using the 10.12 SDK on 10.11 will work. If using the 10.7 SDK on 10.6 will 
work, and we want to help users do that, maybe we should have a documented way 
for the user to do that. And maybe we should install the 10.7 SDK on the 10.6 
buildbot machines so that these ports can be built automatically.

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

Re: zenmap issues

[Ryan Schmidt]

On Oct 28, 2016, at 9:43 AM, William Woods <wood...@outlook.com> wrote:
> 
>> On Oct 28, 2016, at 9:23 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> 
>>> On Oct 28, 2016, at 6:18 AM, William Woods <wood...@outlook.com> wrote:
>>> 
>>> So, I installed nap +zenmap, it installed fine, but:
>>> 
>>> 
>>> 
>>> bash-4.4$ which zenmap
>>> /opt/local/bin/zenmap
>>> bash-4.4$ sudo zenmap
>>> Could not import the zenmapGUI.App module: 'No module named zenmapGUI.App'.
>>> I checked in these directories:
>>>  /opt/local/bin
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip
>>>  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/readline
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
>>>  
>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gtk-2.0
>>> If you installed Zenmap in another directory, you may have to add the
>>> modules directory to the PYTHONPATH environment variable.
>>> bash-4.4$
>>> 
>>> any ideas ?
>> 
>> See https://trac.macports.org/ticket/46429
>> 
> OK sure, but any idea of when will be fixed to work normally ?

I know nothing more about this issue than what I just read in the ticket. I see 
there is a workaround shown there that you can use until the maintainer 
resolves the problem.


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

Re: zenmap issues

[Ryan Schmidt]

> On Oct 28, 2016, at 6:18 AM, William Woods  wrote:
> 
> So, I installed nap +zenmap, it installed fine, but:
> 
> 
> 
> bash-4.4$ which zenmap
> /opt/local/bin/zenmap
> bash-4.4$ sudo zenmap
> Could not import the zenmapGUI.App module: 'No module named zenmapGUI.App'.
> I checked in these directories:
>/opt/local/bin
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip
>/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/readline
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages
>
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gtk-2.0
> If you installed Zenmap in another directory, you may have to add the
> modules directory to the PYTHONPATH environment variable.
> bash-4.4$
> 
> any ideas ?

See https://trac.macports.org/ticket/46429



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

Re: Moving to GitHub: Status Update, Action Required

[Ryan Schmidt]

> On Oct 28, 2016, at 9:02 AM, Craig Treleaven  wrote:
> 
>> On Oct 21, 2016, at 2:12 PM, Clemens Lang  wrote:
>> ...
>> Migration Timeline
>> ==
>> The switch to Git will happen on the weekend of October 29th/30th. ...
> 
> Is this still on track?

Yes.


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

Re: trouble building mtr 0.87 on snow leopard. portfile patched?

[Ryan Schmidt]

> On Oct 28, 2016, at 5:03 AM, Peter Hancock  wrote:
> 
> On a snow leopard machine, mtr won't upgrade from 0.86 to 0.87.
> The trouble, according to the log, is that IPPROTO_SCTP isn't defined.   The 
> failing compile is:
> 
> :info:build /usr/bin/gcc-4.2 -DHAVE_CONFIG_H  -I.   -I/opt/local/include  
> -pipe -Os -arch i386 -Wall -Wno-pointer-sign -MT net.o -MD -MP -MF 
> .deps/net.Tpo -c -o net.o net.c
> 
> This is after several "sudo port clean mtr "s.
> I'd no problems with upgrading mtr on a 2012 mini running yosemite.
> 
> I looked at the trac.macports.org, and the last 154082 changeset gives some 
> diffs to the
> portfile.  Quite possibly I'm not looking at the right thing, but the patch 
> doesn't
> seem to have been applied to the portfile used by the failing build.  (There 
> were no 
> complaints about checksums in the build.) 
> 
> I'm reluctant to uninstall mtr and reinstall it, as 0.86 functions and is 
> very useful.
> Anyone else have this issue?
> 
> Otherwise I've done most(?) things one should do before creating a ticket. 
> Worth doing?

Upstream already had a bug report and solution for this, so I applied it to the 
port:

https://trac.macports.org/changeset/154358

Hopefully that resolves it.


Since you already used a hack to install the port without that fix, you should 
probably rebuild it. Wait an hour or two for the fix to make it to our servers, 
then:

sudo port selfupdate
sudo port -n upgrade --force mtr


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

Re: Sierra 10.12.1 and NTP

[Ryan Schmidt]

> On Oct 27, 2016, at 01:36, Dave Horsfall  wrote:
> 
> Just upgraded to 10.12.1, and system.log began spewing out this:
> 
> Oct 27 14:54:36 ozzie com.apple.xpc.launchd[1] (org.macports.ntp): Service 
> only ran for 0 seconds. Pushing respawn out by 10 seconds.
> 
> along with annoying pop-ups.
> 
> Running "launchctl remove org.macports.ntp" fixed it, but I have a feeling 
> that I need it for the NTP client.
> 
> Anyone else seen this?  Same thing happened with "rsyncd" and "lighttpd" 
> too (all ports that I'd installed).
> 

That sounds like the programs crashed. Are there any crash logs in the usual 
directories?
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trac & Subversion available again

[Ryan Schmidt]

> On Oct 22, 2016, at 22:48, Jeremy Huddleston Sequoia  
> wrote:
> 
> 
>> On Oct 21, 2016, at 18:16, Clemens Lang  wrote:
>> 
>> Hello MacPorts users and developers,
>> 
>>> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
>>> Due to the current SVN and Trac downtime, we are also discussing to
>>> make the move of Trac sooner if that helps us restore service earlier.
>>> We will keep you informed on this.
>> 
>> Due to the current unplanned downtime, we brought the migration of our
>> Trac installation forward and finished it today. Pending DNS
>> propagation, you should be able to reach Trac at trac.macports.org
>> again. Note that you will need a GitHub account to log into Trac now.
>> 
>> Please make sure that you have added the email address you used in Trac
>> to your GitHub account. A cronjob will automatically associate your
>> tickets and other contributions with the GitHub login a few minutes
>> after your login.
> 
> How often does this job run?

Frequently, I'm told. 

> It's been about a day now, and I still cannot edit tickets (beyond making 
> comments).  My @macports.org email address was on my github account months 
> ago, so that's not the issue.

The ability to edit tickets depends on your membership in the Developers team 
of the MacPorts GitHub org. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Servers down?

[Ryan Schmidt]

> On Oct 22, 2016, at 16:11, Fielding, Eric J (329A) 
>  wrote:
> 
> I am guessing that the lack of access to MacPorts yesterday (Friday) may have 
> been related to the massive DDoS attack on the Dyn DNS servers. Because Dyn 
> uses their content delivery network to provide DNS, different areas were 
> affected to differing degrees from what I saw reported. The regular MacPorts 
> rsync mostly worked for me on Friday and still works today. As they say, your 
> mileage may vary.


Apple currently believes the outage was caused by a change Apple made to their 
network configuration which had unexpected consequences. 3 of the IP addresses 
used by MacPorts became inaccessible outside Apple. Other macOS forge IP 
addresses used by MacPorts and other projects were not affected. The services 
on the servers using those IP addresses have been moved to a new server outside 
of Apple. ___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Moving to GitHub: Status Update, Action Required

[Ryan Schmidt]

> On Oct 22, 2016, at 7:49 AM, Marko Käning  wrote:
> 
> Hi Clemens,
> 
> On 22 Oct 2016, at 14:41 , Clemens Lang  wrote:
>> Developers will merge them, either using the command line client, or the
>> GitHub UI. We haven't decided and documented which merge method to use,
>> although I'd prefer the rebase.
> 
> ok, I see.
> 
> BTW, you’ve mentioned in some thread lately this GitHub command line client!
> However, exactly that client doesn’t yet appear on the WorkingWithGit tools
> page [1]. I guess it would be worth adding.

There's the "git" command line program in the "git" port, as well as the "hub" 
command line program in the "hub" port.


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

Re: Moving to GitHub: Status Update, Action Required

[Ryan Schmidt]

> On Oct 22, 2016, at 6:54 AM, Richard Cobbe  wrote:
> 
> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
>> Hello MacPorts users and developers,
>> 
>> MacPorts will be moving to GitHub soon. We're sending this email to
>> inform you about changes in how you access the MacPorts repositories and
>> bug tracker. Additionally, this email contains information on planned
>> downtimes.
> 
> Is there/will there be a story for people who cannot use rsync to pull down
> updates because they're behind a restrictive proxy?
> 
> This affects one of the three computers on which I maintain a MacPorts
> installation.  I currently use the mechanisms described at
>  to get around this,
> but of course those instructions are coupled very tightly to SVN.

You will be able to use git or svn to do that after we switch to GitHub. 
(GitHub has an svn compatibility mode.)


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

Re: Moving to GitHub: Status Update, Action Required

[Ryan Schmidt]

> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez  wrote:
> 
>> On Oct 21, 2016, at 10:20 PM, Craig Treleaven  
>> wrote:
>> 
>> However, would it be possible to add a tangible example of updating
>> a port to that page?  
>> 
>> I know a little bit about Subversion and less about Git.  I would like
>> to see a soup-to-nuts example of cloning the ports tree, updating
>> a Portfile, maybe deleting an old patch and adding a new one, and
>> getting the updated port into MacPorts (direct commit v. pull
>> request).  It would be helpful if one-time requirements (setting name
>> and email address) were clearly separated from repetitive steps
>> (pulling changes from master?).  Otherwise, it is going to be a wee
>> bit nerve-wracking the first few times...
> 
> This would be good.
> 
>> Also, is the consensus that a graphical user interface over git more
>> likely to be harmful than helpful?  The Tools section at the bottom of
>> the page doesn’t give any kind of recommendation.
> 
> I don't know that there is any sort of consensus on that. Everyone has
> their own preferences, and Git is almost absurdly flexible about
> workflows. I don't think our documentation should recommend any
> particular tools. 

I think it would be reasonable for us to mention that GitHub Desktop is a GUI 
client that exists and works for basic operations like creating or switching 
between branches and committing changes and has a handy diff viewer to see your 
changes before committing and even lets you select which portions of your diff 
you want to commit. But it is of no help with even slightly more advanced git 
commands.



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

Re: Servers down?

[Ryan Schmidt]

> On Oct 21, 2016, at 5:45 PM, Manfred Antar <man...@pozo.comcastbiz.net> wrote:
> 
> 
>> On Oct 21, 2016, at 3:32 PM, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> 
>>> On Oct 21, 2016, at 4:31 PM, Lawrence Velázquez <lar...@macports.org> wrote:
>>> 
>>>> On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco <oraclmas...@gmail.com> wrote:
>>>> 
>>>> I can't even get to the migration page on macports.org...
>>> 
>>> Yes, {svn,trac}.macports.org is still down, and probably others.
>> 
>> The only other server that appears to have been affected was the one serving 
>> the web site and guide. We already moved this to new hosting, but have not 
>> yet set up the ports database on the new server, which is why that section 
>> of the web site is currently unavailable.
>> 
>> Until access is restored, you can probably find some of our wiki pages in 
>> the Internet Archive, such as:
>> 
>> https://web.archive.org/web/20160513042611/http://trac.macports.org/wiki/Migration
>> 
> 
> Does this mean that svn.macports.org will no longer work for updating the 
> ports tree ?
> It’s been down for a few days.

There is an unexpected problem on the network that our servers are on; access 
to these servers was inadvertently blocked. We are trying to get access 
unblocked again, or move the servers to another location, as quickly as 
possible, hopefully by tomorrow.

> will everything switch to git?

On October 29th/30th. After that time, you can use git to update your ports 
tree, or svn if you prefer, since GitHub provides an svn compatibility mode.

> Hopefully there will be a faq on changing over.

What we have written for now is here:

https://lists.macosforge.org/pipermail/macports-users/2016-October/041819.html

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

Re: Servers down?

[Ryan Schmidt]

> On Oct 21, 2016, at 4:31 PM, Lawrence Velázquez  wrote:
> 
>> On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco  wrote:
>> 
>> I can't even get to the migration page on macports.org...
> 
> Yes, {svn,trac}.macports.org is still down, and probably others.

The only other server that appears to have been affected was the one serving 
the web site and guide. We already moved this to new hosting, but have not yet 
set up the ports database on the new server, which is why that section of the 
web site is currently unavailable.

Until access is restored, you can probably find some of our wiki pages in the 
Internet Archive, such as:

https://web.archive.org/web/20160513042611/http://trac.macports.org/wiki/Migration


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

Re: Guile appears to be broken again...

[Ryan Schmidt]

A bug report was already filed for this:

https://trac.macports.org/ticket/52613



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

Re: gcc6 build failed on Snow Leopard

[Ryan Schmidt]

On Oct 15, 2016, at 11:07, Ken Cunningham wrote:

> Weird. Is this on the same exact machine? 

Yes. 


> on one hand the checksum differs and it says bootstrap fails.
> on the other, the checksum differs and it says comparison sucessful.
> 
> 
> No difference in file system / case sensitivitiy?
> ? race condition involving parallel build threads?

Parallel build race condition is the only explanation that was occurring to me. 


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

Re: gcc6 build failed on Snow Leopard

[Ryan Schmidt]

> On Oct 15, 2016, at 07:58, Davide Liessi <davide.lie...@gmail.com> wrote:
> 
> 2016-10-14 2:00 GMT+02:00 Ryan Schmidt <ryandes...@macports.org>:
>> For some reason the 10.6 x86_64 builder didn't build it either so we didn't 
>> have a gcc6-6.2.0_0.darwin_10.x86_64.tbz2 package. It's not easy to find old 
>> buildbot logs so I don't know if it failed because of the same bootstrap 
>> failure you saw or for some other reason.
>> 
>> Josh forced a build now, and it built successfully, so if you clean and try 
>> again, without the universal variant, you'll get the package from us without 
>> having to compile it yourself.
> 
> It happened again for gcc6 @6.2.0_1.
> https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds/7398

I forced another build and it succeeded:

https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds/7437

Does anybody want to compare the logs and try to figure out what's different?

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

Re: gcc6 build failed on Snow Leopard

[Ryan Schmidt]

On Oct 14, 2016, at 09:51, Richard L. Hamilton <rlha...@smart.net> wrote:
> 
> 
>> On Oct 13, 2016, at 20:00, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> On Oct 13, 2016, at 16:58, Richard L. Hamilton <rlha...@smart.net> wrote:
>>> 
>>> This was a build prerequisite for py27-numpy, so I can't build that either. 
>>>  It failed both with and without +universal (I think I have the latter set 
>>> as default).
>> 
>> For some reason the 10.6 x86_64 builder didn't build it either so we didn't 
>> have a gcc6-6.2.0_0.darwin_10.x86_64.tbz2 package. It's not easy to find old 
>> buildbot logs so I don't know if it failed because of the same bootstrap 
>> failure you saw or for some other reason.
>> 
>> Josh forced a build now, and it built successfully, so if you clean and try 
>> again, without the universal variant, you'll get the package from us without 
>> having to compile it yourself.
> 
> That worked, thanks!
> 
> I see that a similar situation applied to gcc49 and dpkg, that I couldn't 
> build them for myself with +universal, but pre-built binaries were available 
> without it.  That might well apply to the other things that aren't building 
> for me too, except they're libraries, and I already have a bunch of 
> dependencies on them in place, so that wouldn't be a good idea unless I redid 
> everything without universal.

"Bootstrap comparison failure" is an error message specific to the GCC build 
system. GCC is a very large and complex piece of software, and I don't 
understand its build system or why this error sometimes happens for some people.

If you are also having problems building other less complex software, like 
dpkg, would you please show us the main.log file from those failures? They may 
be easier to diagnose.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: gcc6 build failed on Snow Leopard

[Ryan Schmidt]

On Oct 13, 2016, at 16:58, Richard L. Hamilton  wrote:
> 
> This was a build prerequisite for py27-numpy, so I can't build that either.  
> It failed both with and without +universal (I think I have the latter set as 
> default).

For some reason the 10.6 x86_64 builder didn't build it either so we didn't 
have a gcc6-6.2.0_0.darwin_10.x86_64.tbz2 package. It's not easy to find old 
buildbot logs so I don't know if it failed because of the same bootstrap 
failure you saw or for some other reason.

Josh forced a build now, and it built successfully, so if you clean and try 
again, without the universal variant, you'll get the package from us without 
having to compile it yourself. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: HDF5 Problem

[Ryan Schmidt]

> On Oct 13, 2016, at 11:05 AM, Eric A. Borisch  wrote:
> 
> As the error message points out, you can set HDF5_DISABLE_VERSION_CHECK=1 (or 
> 2) to make things run. As they say, don't blame them if it crashes.
> 
> There are plenty of reports out there (outside of MP) on this HDF5 feature. 
> As far as I can tell, the HDF5 group's position is that they are used for 
> storing critical data (output from experiments that you don't want to have to 
> "re-do"), so they don't ever want to be the cause of errors from 
> unintentional / unexpected behavior, even if the program can happily link.
> 
> It would be nice if we had some centralized way to handle this rather than 
> rev-bumping each dependent port, but that is where we are currently at. Is it 
> possible to have an hdf5 PortGroup where we could centrally bump an epoch?

No; bumping the epoch is not sufficient; you must change the revision or 
version for MacPorts to see it as an upgrade.



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

Re: HDF5 Problem

[Ryan Schmidt]

> On Oct 13, 2016, at 10:14 AM, Adam Dershowitz  wrote:
> 
> I just updated hdf5 and hdf5-18:
> 
> hdf5   1.10.0_1 < 1.10.0-patch1_0   
> hdf5-181.8.16_6 < 1.8.17_0   
> 
> Now when I try to use pandas to open an HDF5 file I get this error:
> 
> Warning! ***HDF5 library version mismatched error***
> The HDF5 header files used to compile this application do not match
> the version used by the HDF5 library to which this application is linked.
> Data corruption or segmentation faults may occur if the application continues.
> This can happen when an application was compiled by one version of HDF5 but
> linked with a different version of static or shared HDF5 library.
> You should recompile the application or check your shared library related
> settings such as 'LD_LIBRARY_PATH'.
> You can, at your own risk, disable this warning by setting the environment
> variable 'HDF5_DISABLE_VERSION_CHECK' to a value of '1'.
> Setting it to 2 or higher will suppress the warning messages totally.
> Headers are 1.8.16, library is 1.8.17

Sounds like whatever library generated that error (you mentioned py27-pandas 
and py27-tables but I don't know) is being possibly overzealous in its hdf5 
version checking. Sounds like we should increase the revision of whichever port 
is triggering this error, and add a comment to the hdf5 port to remind us to do 
that every time the version of hdf5 is increased.

It looks to me like py27-tables is the one that depends on hdf5-18, so that's 
the one that probably needs to be rebuilt. py27-pandas only depends on 
py27-tables and other python modules. 


> I tried uninstalling and reinstalling pandas and py27-tables, but that didn’t 
> help.

If you received a binary from our server, it would be a binary built with the 
old version of hdf5. We need to increase that port's revision to cause it to 
rebuild with the new version of hdf5.

You can try rebuilding from source on your system to identify the problem. 

sudo port -ns upgrade --force py27-tables

If that works, let us know so we can increase its revision.


Looking a little further, I see that the "HDF5 library version mismatched 
error" actually comes from the hdf5-18 (and hdf5) source code. This makes me 
think that *any* port that uses hdf5-18 (or hdf5) will encounter this problem, 
and they should all be revbumped any time the version of hdf5-18 (or hdf5) is 
increased. This is a pain and the developers of hdf5 should be contacted to 
explain this to them, so that they can weigh in on why they are inflicting this 
pain on us and what they can do to mitigate it in subsequent versions of their 
software.


> So, I’m not sure where the bug actually is, what to do about it, or what port 
> to file a bug report against.
> Any suggestions?  


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

Re: python, port select and group

[Ryan Schmidt]

> On Oct 13, 2016, at 6:30 AM, Björn Raupach  wrote:
> 
> Dear group,
> 
> I am not very familiar with groups and the port select command. Maybe someone 
> can shed some light.
> 
> At first I assumed it sets the default symlink for the command in /usr/bin, 
> but then I don’t seem to understand the output of port select —summary
> 
> Name Selected Options
>   ===
> awscli   py34-awscli  py34-awscli none
> mavenmaven3   maven3 none
> mysqlmysql56  mysql56 none
> pip  none none
> python   none python26-apple python27-apple python34 none
> python3  none python34 none
> 
> Why is python in more than one group? If I call python from the command line 
> it launches the python3.4 even though port select shows that none is selected.
> 
> port select —set python python34 yields an error: Selection ‘python34’ for 
> ‘python’ failed: symlink: /opt/local/etc/select/python/current -> python34: 
> file already exists.

Maybe you had selected python3.x with MacPorts before, then you uninstalled 
MacPorts without un-selecting python, and now you've installed MacPorts again?

You could remove the /opt/local/etc/select/python/current symlink manually and 
try again, though I'm unclear on why it would be complaining that it already 
exists; it's normal for it to already exist.


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

Re: Migration from Mavericks to El Capitan failed

[Ryan Schmidt]

> On Oct 10, 2016, at 3:55 AM, list_em...@icloud.com wrote:
> 
> I’m trying to upgrade MacPorts after upgrading my OS from Mavericks to El 
> Capitan. (My computer is too old for Sierra.) I followed the migration 
> instructions at https://trac.macports.org/wiki/Migration but the process 
> related to the line 
> 
> sudo ./restore_ports.tcl myports.txt
> 
> generated a lot of errors. I have no idea what to do next. I’ve attached the 
> large Terminal output.
> 
> Jerry
> 

The log shows you encountered the error "too many open files" while running 
./restore_ports.tcl. This is probably:

https://trac.macports.org/ticket/50986

Please try installing fewer ports at once.

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

Re: lvm-3.3 problem with sierra

[Ryan Schmidt]

> On Oct 9, 2016, at 08:13, Comer Duncan  wrote:
> 
> I tried to follow the upgrade procedure and eventually got the complaint that 
> lvm-3.3 is not supported. I'm attaching the log file and ask for  advice 
> about ways around this obstacle. Thanks for your help!

llvm-3.3 and later should be supported on Sierra, as of my commit last night. 
Run "sudo port selfupdate" and try again. Or, preferably, use a newer version, 
like llvm-3.8. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Recommended upgrade order

[Ryan Schmidt]

> On Oct 8, 2016, at 5:44 PM, Bill Christensen  
> wrote:
> 
> Just got a successful install of MySQL 5.7.  
> 
> A couple of notes:  Instead of entering 
> 
>  sudo -u _mysql mysql_install_db
> 
> as was the instruction for MySQL 5.6 and earlier  
> (https://trac.macports.org/wiki/howto/MySQL), the instruction sequence is now:
> 
>  sudo /opt/local/lib/mysql57/bin/mysqld --initialize --user=_mysql
> 
> which creates the db and assigns a default root password (used to be set to 
> blank), followed by 
> 
>sudo port select mysql mysql57
> 
> then
> 
> /opt/local/lib/mysql57/bin/mysql_secure_installation
> 
> 
> 
> It might also be helpful to include that when you run
> 
>  ps -ax | grep mysql
> 
> you should expect to see something along the lines of:
> 
> 
> 
>   /opt/local/bin/daemondo --label=mysql57-server --start-cmd 
> /opt/local/lib/mysql57/bin/mysqld --user=_mysql ; --pid=exec
> 
>  /opt/local/lib/mysql57/bin/mysqld --user=_mysql
> 
> 
>  grep mysql
> 
> if it's running.  If the only response is 
> 
>grep mysql
> 
> then MySQL hasn't started.  

If you have improvements to make to the instructions in the wiki, please do so.

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

Re: question on PHP7.0 install

[Ryan Schmidt]

> On Oct 8, 2016, at 6:27 PM, Bill Christensen  
> wrote:
> 
> 
> Previous versions of php.ini contained a line such as:
> 
> mysql.default_socket=/opt/local/var/run/mysql56/mysqld.sock
> in php7.0, that line does not exist by default.  
> 
> Do I need to define mysql.default_socket for php7 (with the correct mysql 
> version, of course), or not?  Will adding such a line mess things up?

The mysql module, to which that setting applies, was removed for php 7. The 
mysqli and pdo_mysql modules remain, and you can set the corresponding settings 
for the socket for those modules.


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

Re: Recommended upgrade order

[Ryan Schmidt]

> On Oct 8, 2016, at 14:56, Bill Christensen  
> wrote:
> 
> That may explain the problems I was having when doing a dry-run install of 
> MySQL 5.7. 

mysql57 installed for me today, so maybe try it again?


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

Re: Subversion checkout failed...?

[Ryan Schmidt]

> On Oct 8, 2016, at 11:21 AM, Michael  wrote:
> 
> On 2016-10-08, at 8:11 AM, Ken Cunningham  
> wrote:
> 
>> looks like v8 is here now:
>> 
>> https://github.com/v8/v8
>> 
>>> 
>>> These projects were both hosted at Google Code. Google Code no longer 
>>> exists, so it's true that you can't check out the code from their now 
>>> nonexistent servers.
> 
> So this is version 8 of the Google javascript engine.

It refers to the Google JavaScript engine, whose name is "v8".

> Yea, I can see that being held at Google Code :-).

Many projects were. But Google decided to discontinue their service, so 
projects had to move.

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

Re: Subversion checkout failed...?

[Ryan Schmidt]

> On Oct 8, 2016, at 9:55 AM, Carlo Tambuatco  wrote:
> 
> Made the leap to Sierra yesterday and a few ports have had trouble 
> downloading.
> 
> The v8 and word2vec ports both failed to be checked out via subversion.
> 
> It’s a lot to get into, I’ll just include the log files for both of them here…

These projects were both hosted at Google Code. Google Code no longer exists, 
so it's true that you can't check out the code from their now nonexistent 
servers. The ports need to be updated for wherever those projects have moved to.

The ticket for v8 is https://trac.macports.org/ticket/52532

There are no open tickets for word2vec; feel free to file one.


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

Re: MacPorts question

[Ryan Schmidt]

> On Oct 7, 2016, at 10:13 AM, m...@macports.org wrote:
> 
> 
>> On Oct 7, 2016, at 8:18 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> 
>> On Oct 7, 2016, at 9:15 AM, m...@macports.org wrote:
>> 
>>> On Oct 7, 2016, at 7:55 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
>>> 
>>>> I was using nginx when I was encountering these problems.
>>> 
>>> I just installed and “load”ed nginx and added a firewall rule for it. It 
>>> survived reboot for me!
>> 
>> Does it survive upgrading (or downgrading) nginx?
> 
> I won’t know until it gets updated next.

If you wanted to test, you could downgrade:

https://trac.macports.org/wiki/howto/InstallingOlderPort

> In any event, I don’t think it is an issue. I think when you are updating the 
> port, you should relaunch the startupitem as part of that upgrade process. 
> What if the startupitem changed? We can know as Macports committers, but 
> normal users generally will not know. So it is best practice to do such. 

Restarting the computer is equivalent to unloading and then loading the launchd 
plist. I don't remember the specifics as it was months ago, and if I had even 
been able to specify exactly when the problem occurred that might have helped 
me look for a solution. What I remember is that I would seem to get things into 
a working state, and then something would happen--restart? upgrade port?--that 
would cause the firewall to be blocking connections again, even though the 
program was listed as allowed in the preferences.

I want my Tiger firewall back, where I just specify that traffic on port 80 
should be allowed. Simple. Works.


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

Re: MacPorts question

[Ryan Schmidt]

On Oct 7, 2016, at 9:15 AM, m...@macports.org wrote:

> On Oct 7, 2016, at 7:55 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
> 
>> I was using nginx when I was encountering these problems.
> 
> I just installed and “load”ed nginx and added a firewall rule for it. It 
> survived reboot for me!

Does it survive upgrading (or downgrading) nginx?



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

Re: MacPorts question

[Ryan Schmidt]

> On Oct 7, 2016, at 8:54 AM, m...@macports.org wrote:
> 
> [Cc’ing Macports Users this time]
> 
>> On Oct 7, 2016, at 7:39 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> 
>>> On Oct 7, 2016, at 8:35 AM, m...@macports.org wrote:
>>> 
>>> Hi Ryan,
>>> 
>>> 
>>> Thank you for the reply. So I think that you did not see my other post. I 
>>> wonder why the mailing list did not send it? Maybe because I had modified 
>>> the subject title? Here it is again:
>> 
>> You're right, I didn't see that message.
>> 
>> 
>>> OK, the solution was actually very simple. I added the httpd application to 
>>> the Firewall. It is located here:
>>> 
>>> /opt/local/apache2/bin/httpd
>>> 
>>> This survived a reboot for me. 
>>> 
>>> Steps to add it (sorry if this is obvious):
>>> 1. Starting from the Terminal type:
>>>   - cd /opt/local/apache2/bin/
>>>   - open .
>>> 2. Open System Preferences->Security & Privacy->Firewall tab.
>>> 3. Click the lock to unlock it.
>>> 4. Click Firewall Options…
>>> 5. Click +
>>> 6. In Finder, drag “httpd” (now visible in Finder from Step 1) to the 
>>> dialog. 
>>> 
>>> 
>> 
>> I'm familiar with this procedure; I've read it on many web sites. But it 
>> often simply does not work. Despite the program having been added to the 
>> firewall options in this manner, communication remains blocked. I was only 
>> able to get it to work by using a terminal command to add it to the 
>> firewall, and I don't recall whether that turned out to be a permanent 
>> solution or not; I have a feeling it either did not survive reboot or did 
>> not survive updating the port that provided that binary.
> 
> OK. I played around with this some more and did a bunch of rebooting. The 
> problem is that apache2 itself does not survive the reboot! I tested this by 
> looking at “httpd” in activity monitor. So the firewall rule is correct. But 
> we have another issue that the startupitem for Apache2 is not properly 
> working in El Capitan (at least). 
> 
> I use the port load command like so:
> 
> - sudo port load apache2
> - httpd is present and running in Activity Monitor
> - Reboot
> - httpd is gone!

I was using nginx when I was encountering these problems.


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

Re: Recommended upgrade order

[Ryan Schmidt]

On Oct 7, 2016, at 3:16 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
> 
> The phpXX-mysql ports don't yet have a +mysql57 variant. I was in the process 
> of trying to add that, but got delayed by mysql57 not building 
> (https://trac.macports.org/ticket/52185)

But you can still use the +mysqlnd variant with MySQL 5.7 or any other version, 
which should work fine.


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

Re: Recommended upgrade order

[Ryan Schmidt]

> On Oct 7, 2016, at 2:55 AM, Bill Christensen  
> wrote:
> 
> I'm planning to upgrade a couple MAMP servers, and wanted to check if any 
> gotchas may be out there.  I plan to upgrade:
> 
> OSX 10.9.5 and 10.10.x to 10.12.x (and obviously xcode)
> 
> PHP 5.5.x to 7.x
> 
> MySQL 5.5.x to 5.7.x
> 
> Does it matter if I do the OS before php/mysql, or the other way around?  I'm 
> guessing OS first.

When you upgrade the OS, you'll have to reinstall all ports, so you should 
upgrade the OS and MacPorts first, then reinstall MacPorts, then reinstall all 
ports. See the Migration wiki page.

The phpXX-mysql ports don't yet have a +mysql57 variant. I was in the process 
of trying to add that, but got delayed by mysql57 not building 
(https://trac.macports.org/ticket/52185)


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

Re: thanks

[Ryan Schmidt]

> On Oct 6, 2016, at 15:14, Stan Sanderson wrote:
> 
> It may seem obvious, but I would like to offer the following “hint:”
> 
> During the reinstall port process there were a few times when it halted for 
> some reason or another (e.g., "too many files open”).

https://trac.macports.org/ticket/50986

We probably need a ProblemHotlist entry for that at this point. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Locating libraries installed with MacPorts

[Ryan Schmidt]

> On Oct 5, 2016, at 5:21 PM, Mick Jordan  wrote:
> 
> I have several libraries installed via MacPorts (that also exists in /usr/lib 
> FWIW), e.g, libpcre and libz. I was rather surprised to see that these 
> resolve to the MacPorts location,i.e., /opt/local/lib even though I am not 
> passing -L/opt/local/lib to the link step. I thought this might be because I 
> was using gcc to do the compilation/linking and that is also installed via 
> MacPorts, but I get the same behavior when using clang. I added -Wl,-v to the 
> link step and it lists the directories it is searching and /opt/local/lib is 
> not included in the list. So my question is how is ld resolving to 
> /opt/local/include. I have no environment variables such as LDFLAGS set, 
> although /opt/local/bin is on my PATH.
> 
> I'm running MacPorts 2.3.4 in El Capitan.

I'm not able to reproduce this problem.


$ echo 'int main(void) { return 0; }' > main.c
$ clang main.c -lz
$ otool -L a.out 
a.out:
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 
1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 1226.10.1)


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

Re: kmymoney4 broken after update

[Ryan Schmidt]

> On Oct 4, 2016, at 6:40 AM, Stanton Sanderson <stans...@gmail.com> wrote:
> 
> 
>> On Oct 4, 2016, at 5:07 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> 
>>> On Oct 1, 2016, at 8:46 PM, Stanton Sanderson <stans...@gmail.com> wrote:
>>> 
>>>>> Thank you for your suggestion. I followed the steps as suggested (using 
>>>>> the correct spelling for the upgrade step) but the process again failed 
>>>>> at rebuilding kmymoney4.
>>>> 
>>>> Ok, but the activation conflict is resolved?
>>>> 
>>>>> I activated gpgme @1.6.0_2 and kdepimlibs4 @4.14.3_3 (which are still 
>>>>> installed) and kmoney4 opened as before.
>>>>> 
>>>>> I uninstalled gpgme @1.7.0_0 and kdepimlibs4 @4.14.3_4, then did a self 
>>>>> update and upgrade outdated. After the upgrades, kmymoney4 attempts to 
>>>>> upgrade and fails.
>>>> 
>>>> Can you show us a transcript or log of the failure?
>>> 
>>> I am at a point where port outdated (after sudo port selfupdate and sudo 
>>> port upgrade) returns
>>> The following installed ports are outdated:
>>> gpgme  1.6.0_2 < 1.7.0_0 
>>> kdepimlibs44.14.3_3 < 4.14.3_4 
>>> I don’t understand that. 
>> 
>> What don't you understand? You don't have the latest versions installed; 
>> MacPorts is telling you that.
>> 
> 
> Sorry for the confusion. What I don’t understand is that after running port 
> selfupdate and port upgrade outdated, gpgme and kdepimlibs4
> remain at the outdated versions. While this is convenient (since it allows me 
> to run kmymoney4), I don’t understand why
> the selfupdate and upgrade outdated scripts are skipping these two ports.

If a newer version of a port is installed, but an older version is active, it 
will be shown when you run "port outdated" but you will not be upgraded to it 
when running "sudo port upgrade outdated". If you want to upgrade, you can 
"sudo port activate" the new one.


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

Re: kmymoney4 broken after update

[Ryan Schmidt]

> On Oct 1, 2016, at 8:46 PM, Stanton Sanderson  wrote:
> 
>>> Thank you for your suggestion. I followed the steps as suggested (using the 
>>> correct spelling for the upgrade step) but the process again failed at 
>>> rebuilding kmymoney4.
>> 
>> Ok, but the activation conflict is resolved?
>> 
>>> I activated gpgme @1.6.0_2 and kdepimlibs4 @4.14.3_3 (which are still 
>>> installed) and kmoney4 opened as before.
>>> 
>>> I uninstalled gpgme @1.7.0_0 and kdepimlibs4 @4.14.3_4, then did a self 
>>> update and upgrade outdated. After the upgrades, kmymoney4 attempts to 
>>> upgrade and fails.
>> 
>> Can you show us a transcript or log of the failure?
> 
> I am at a point where port outdated (after sudo port selfupdate and sudo port 
> upgrade) returns
> The following installed ports are outdated:
>   gpgme  1.6.0_2 < 1.7.0_0 
>   kdepimlibs44.14.3_3 < 4.14.3_4 
> I don’t understand that. 

What don't you understand? You don't have the latest versions installed; 
MacPorts is telling you that.

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

Re: LLVM not supported on Sierra?

[Ryan Schmidt]

On Oct 2, 2016, at 22:05, Dave Horsfall wrote:
> 
> Doing a "port upgraded outdated" after installing Sierra (and had some 
> trouble with X11), I get this:
> 
> --->  Computing dependencies for llvm-3.5
> --->  Fetching distfiles for llvm-3.5
> Error: llvm-3.5 is not supported on macOS Sierra or newer.
> 

llvm-3.5 is not supported on Sierra but llvm-3.8 is. 

The usual instructions for upgrading to a new major OS version (see the 
Migration wiki page) call for uninstalling all ports and reinstalling what you 
need. If you do that, you won't be upgrading ports and you won't run into this. 

Since llvm-3.5 is not supported on Sierra, uninstall it. If anything you've 
installed depends on it, MacPorts will tell you, and then for each of those 
ports, you can investigate whether they need a different variant selected, or 
other changes, to support newer llvm. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: kmymoney4 broken after update

[Ryan Schmidt]

> On Sep 30, 2016, at 8:47 AM, Stanton Sanderson <stans...@gmail.com> wrote:
> 
> 
>> On Sep 30, 2016, at 5:17 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> I'm not sure if this will resolve this problem you're experiencing, but 
>> forcing the activation was definitely not good, and you should undo that. 
>> First you need to know which port you force-activated, and which other 
>> port's files got moved out of the way as a result. I assume you 
>> force-activated kdepimlibs4, and that it moved gpgme's files out of the way. 
>> This problem in kdepimlibs4 was fixed in r153292 on Wednesday. I suggest you 
>> `sudo port -f deactivate kdepimlibs4 gpgme`, then `sudo port activate 
>> gpgme`; gpgme's files should now be back in the right place. Then `sudo port 
>> selfupdate`. Then try `sudo port upgrade kdelimpibs4`. If you had the old 
>> conflicting version of kdepimlibs4, it should now be upgraded to the 
>> nonconflicting version. If you already had the nonconflicting version, 
>> nothing will happen, in which case you should be able to run `sudo port 
>> activate kdepimlibs4` without receiving an activation failure. You can then 
>> upgrade any remaining outdated ports with `
 sudo port upgrade outdated`. 
> 
> Thank you for your suggestion. I followed the steps as suggested (using the 
> correct spelling for the upgrade step) but the process again failed at 
> rebuilding kmymoney4.

Ok, but the activation conflict is resolved?

> I activated gpgme @1.6.0_2 and kdepimlibs4 @4.14.3_3 (which are still 
> installed) and kmoney4 opened as before.
> 
> I uninstalled gpgme @1.7.0_0 and kdepimlibs4 @4.14.3_4, then did a self 
> update and upgrade outdated. After the upgrades, kmymoney4 attempts to 
> upgrade and fails.

Can you show us a transcript or log of the failure?

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

Re: kmymoney4 broken after update

[Ryan Schmidt]

> On Sep 29, 2016, at 9:41 AM, Stanton Sanderson  wrote:
> 
> OS- El Capitan
> 
> Kmymoney4 is broken after yesterday updating yesterday (and again today). The 
> message received
> is
> Error rebuilding kmymoney4
>while executing
> "error "Error rebuilding $portname""
>(procedure "revupgrade_scanandrebuild" line 395)
>invoked from within
> "revupgrade_scanandrebuild broken_port_counts $opts"
>(procedure "macports::revupgrade" line 5)
>invoked from within
> "macports::revupgrade $opts"
>(procedure "action_revupgrade" line 2)
>invoked from within
> "action_revupgrade $action $portlist $opts"
>(procedure "action_upgrade" line 25)
>invoked from within
> "$action_proc $action $portlist [array get global_options]"
>(procedure "process_cmd" line 103)
>invoked from within
> "process_cmd $remaining_args"
>invoked from within
> "if { [llength $remaining_args] > 0 } {
> 
># If there are remaining arguments, process those as a command
>set exit_status [process_cmd $remaining..."
>(file "/opt/local/bin/port" line 5268)
> 
> The log file shows
> 
> …
> :info:configure -- Found gpgme-config at /opt/local/bin/gpgme-config
> :info:configure -- Found gpgme v1.7.0, checking for flavours...
> :info:configure --  Found flavour 'vanilla', checking whether it's 
> usable...yes
> :info:configure --  Found flavour 'pthread', checking whether it's 
> usable...yes
> :info:configure CMake Error at 
> /opt/local/share/cmake-3.6/Modules/FindPackageHandleStandardArgs.cmake:148 
> (message):
> :info:configure   Could NOT find QGpgme (missing: _QGPGME_EXTRA_LIBRARY)
> :info:configure Call Stack (most recent call first):
> :info:configure   
> /opt/local/share/cmake-3.6/Modules/FindPackageHandleStandardArgs.cmake:388 
> (_FPHSA_FAILURE_MESSAGE)
> :info:configure   /opt/local/share/apps/cmake/modules/FindQGpgme.cmake:43 
> (find_package_handle_standard_args)
> :info:configure   CMakeLists.txt:72 (find_package)
> :i..
> ——
> A few days ago, one of updated ports would not install (gpgme ? ), citing a 
> conflict but suggesting the use of 
> force-install. I (foolishly?) forced the install, but wasn’t too worried as 
> Kmymoney continued to function. However, after the latest update it is broken.
> 
> I’m not sure what to do, don’t want to break anything else, and am desperate 
> to restore Kmymoney4.
> I’ve considered uninstalling gpgme @1.7.0_0 (which is active) and 
> reinstalling it, but would appreciate some advice before
> making a bigger mess of things.

I'm not sure if this will resolve this problem you're experiencing, but forcing 
the activation was definitely not good, and you should undo that. First you 
need to know which port you force-activated, and which other port's files got 
moved out of the way as a result. I assume you force-activated kdepimlibs4, and 
that it moved gpgme's files out of the way. This problem in kdepimlibs4 was 
fixed in r153292 on Wednesday. I suggest you `sudo port -f deactivate 
kdepimlibs4 gpgme`, then `sudo port activate gpgme`; gpgme's files should now 
be back in the right place. Then `sudo port selfupdate`. Then try `sudo port 
upgrade kdelimpibs4`. If you had the old conflicting version of kdepimlibs4, it 
should now be upgraded to the nonconflicting version. If you already had the 
nonconflicting version, nothing will happen, in which case you should be able 
to run `sudo port activate kdepimlibs4` without receiving an activation 
failure. You can then upgrade any remaining outdated ports with `sudo port 
upgrade outdated`. 


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

Re: Address of nonexistent hosts...?

[Ryan Schmidt]

> On Sep 29, 2016, at 5:57 PM, Carlo Tambuatco  wrote:
> 
>> On Thursday, September 29, 2016, Lawrence Velázquez  
>> wrote:
>> > On Sep 29, 2016, at 6:04 PM, Carlo Tambuatco 
>> > wrote:
>> >
>> > Just installed a port and got this message:
>> >
>> > Warning: Your DNS servers incorrectly claim to know the address of
>> > nonexistent hosts. This may cause checksum mismatches for some ports.
>> > See this page for more information:
>> > 
>> >
>> > So I visited the site but it doesn’t look like any of the cases apply
>> > to me
>> 
>> Are you sure? What happens if you visit a nonexistent domain in your
>> browser?
> 
> vq
> 
> It sends me to a search page apologizing that it could not find the page was 
> looking for but offers alternative suggestions. So I guess this means AT is 
> breaking relevant internet standards?

Yes.


> Then this means I should switch to a different DNS server?

Yes.


> I'm a bit of a newb at that sort of thing, not my speciality. How do I go 
> about doing that?  

Apple menu > System Preferences > Network > Advanced > DNS

Click the "+" button, add "8.8.8.8" to the list of DNS servers.

Click the "+" button, add "8.8.4.4" to the list of DNS servers.

(These are the Google public DNS servers.)

Click OK, click Apply.

Or, you can configure your router to automatically distribute that DNS server 
address to all connected clients; instructions vary depending on your model of 
router.


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

Re: Address of nonexistent hosts...?

[Ryan Schmidt]

> On Sep 29, 2016, at 5:04 PM, Carlo Tambuatco  wrote:
> 
> Just installed a port and got this message: 
> 
> Warning: Your DNS servers incorrectly claim to know the address of 
> nonexistent hosts. This may cause checksum mismatches for some ports. See 
> this page for more information: 
> 
> 
> So I visited the site but it doesn’t look like any of the cases apply to me, 
> and I haven’t contacted my ISP since so far no checksum mismatches have been 
> found, so not sure if anything needs to be done on my part…

If your DNS server claims that nonexistent hostnames exist, your DNS server is 
broken, and you should tell your DNS provider (perhaps your ISP) to fix their 
DNS server to conform to the relevant standards, and until they do, you should 
switch to a DNS server that does conform (perhaps Google DNS: 8.8.8.8 / 
8.8.4.4).

You'll only run into problems if you try to install a port that has to build 
from source, and lists a download location on a hostname that no longer exists. 
That may be a rare circumstance, but wouldn't you rather not run into problems, 
even rarely?



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

Re: MacPorts question

[Ryan Schmidt]

> On Sep 29, 2016, at 10:30 AM, Zachary Waibel  wrote:
> 
> Sorry for the spam, but I have a question regarding my MacPorts installation, 
> and I’m not sure if filing a ticket is the right way to go to get my question 
> answered. If it is then I will do that.
> 
> Here’s my question: 
> 
> I've installed the latest MacPorts and my issue is that if I start apache2 
> using the command "sudo port load apache2” I can then find my website from 
> outside my network.  However, after restarting my Mac and I cannot find my 
> website anymore.  It turns out if I turn off macOS’s Firewall I can then find 
> the website from the outside again.  The other way I can solve it is by doing 
> "sudo port unload apache2” and then "sudo port load apache2”, which seems to 
> open port 80.  However, after a restart the port is not opened, but apache2 
> is running.  So is MacPorts not compatible with El Capitan’s Firewall?
> 
> Thank you for any help!

Writing to the macports-users mailing list is probably the right thing to do. 
I'm Cc'ing the list now. To reply, please make sure you're subscribed to the 
list first.

I've also been frustrated with the new macOS firewall for some years. I don't 
understand it. Maybe someone else on the list does and can give us both some 
advice.

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

Re: osxfuse @3.5.0 build error

[Ryan Schmidt]

> On Sep 24, 2016, at 11:18 AM, Davide Liessi  wrote:
> 
> :info:build dyld: Library not loaded: /opt/local/lib/libosxfuse.2.dylib
> :info:build   Referenced from:
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework/Versions/A/OSXFUSE
> :info:build   Reason: image not found
> :info:build Can't execute compiled C code... aborting

I've filed this as 

https://trac.macports.org/ticket/52435

It looks like it's specific to 32-bit Macs.

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

Re: osxfuse @3.5.0 build error - fixed

[Ryan Schmidt]

> On Sep 28, 2016, at 10:14 AM, Ken Cunningham 
>  wrote:
> 
>> 
>> I notice in the development tree there is some activity on this file 2 days 
>> ago:
>> 
>> https://github.com/osxfuse/support/tree/support/osxfuse-3/mount_osxfuse.
>> 
>> mount_osxfuse.c  (mount_osxfuse) Fix build warning on Mac OS X 10.6
>> 
> 
> 
> So that fixed the osxfuse build on 10.6 for me this morning.
> 
> Just go get that file 
> 
> sudo port extract osxfuse
> 
> and replace the current one with the new one
> 
> sudo port build osxfuse
> 
> and the build goes through to completion, for me just now on 10.6

Thanks for verifying that works. Committed:

https://trac.macports.org/ticket/52426


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

Re: fetching of some ports fails, but you can wget them from the same URL

[Ryan Schmidt]

> On Sep 27, 2016, at 8:45 AM, Ken Cunningham  
> wrote:
> 
> I've noticed this behaviour a few times recently, most recently today with 
> hexchat, but this is not the only example.
> 
> Trying to get a file using macports' fetch fails, but you can manually wget 
> it without trouble.
> 
> I'm not sure if it's an SSL certificate thing, or why this is happening, 
> exactly.
> 
> Sorry I don't know how to debug the exact problem further than that.
> 
> Here's an example.
> 
> Ken
> 
> 
> $ sudo port upgrade hexchat
> --->  Computing dependencies for hexchat
> --->  Fetching distfiles for hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> https://dl.hexchat.net/hexchat/
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://sea.us.distfiles.macports.org/macports/distfiles/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> https://distfiles.macports.org/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://cjj.kr.distfiles.macports.org/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://lil.fr.distfiles.macports.org/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://osl.no.distfiles.macports.org/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://nue.de.distfiles.macports.org/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://nou.nc.distfiles.macports.org/pub/macports/distfiles.macports.org/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://jog.id.distfiles.macports.org/macports/distfiles/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://jnb.za.distfiles.macports.org/distfiles/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://her.gr.distfiles.macports.org/hexchat
> --->  Attempting to fetch hexchat-2.12.1.tar.xz from 
> http://svn.macports.org/repository/macports/distfiles/hexchat
> Error: org.macports.fetch for port hexchat returned: fetch failed
> Please see the log file for port hexchat for details:
>   
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_irc_hexchat/hexchat/main.log

What does the log say?

What version of macOS is this?


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

Re: soreEyes (and where are my System 7 ports?)

[Ryan Schmidt]

> On Sep 27, 2016, at 4:10 AM, René J.V. Bertin <rjvber...@gmail.com> wrote:
> 
> On Tuesday September 27 2016 04:00:26 Ryan Schmidt wrote:
> 
>> Yes it would. I've changed it in the Trac footer. I expect there are many 
>> places in the guide and wiki where this needs to be changed, but the 
>> documentation needs a major overhaul anyway.
> 
> Might I suggest adding the small nuance that it's something for "users of the 
> Mac operating system"? 

People receiving messages from the ticket system already know what MacPorts is. 

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

Re: soreEyes (and where are my System 7 ports?)

[Ryan Schmidt]

> On Sep 27, 2016, at 3:53 AM, Davide Liessi <davide.lie...@gmail.com> wrote:
> 
> 2016-09-27 10:31 GMT+02:00 Ryan Schmidt <ryandes...@macports.org>:
>> [...] and "the Mac operating system" when not specifying a version.
> 
> I think this would favor describing MacPorts as "Ports system for the
> Mac operating system".

Yes it would. I've changed it in the Trac footer. I expect there are many 
places in the guide and wiki where this needs to be changed, but the 
documentation needs a major overhaul anyway.



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

Re: soreEyes (and where are my System 7 ports?)

[Ryan Schmidt]

> On Sep 27, 2016, at 2:54 AM, René J.V. Bertin  wrote:
> 
> Hi,
> 
> I just caught something from the corner of my eye which put me in rant mode:
> 
>> MacPorts 
>> Ports system for macOS
> 
> Am I the only one who gets sore eyes because of Apple's latest name change 
> for their OS? It's one thing seeing camelToe (...) case being used for 
> variables and functions, using it in a brand name for a system that aims so 
> much to hide its technicity is IMHO just as inappropriate as personifying 
> devices by omitting the (in)definite article when they are mentioned.
> 
> Let's just say I find it ugly, and that Mac OS without "X" evokes, well, the 
> days of an OS held together with hairpins and prehistoriX zip-ties, MacBugs 
> and A9F4. And I can hardly imagine that I'm the only one among the 
> not-so-young-if-not-more-mature users who have that kind of association.
> 
> I'll keep calling any Darwin version before 16 "Mac OS X" as long as "About 
> this Mac" continues to identify the system that way.
> 
> Anyway, this is indeed mostly a rant, but couldn't we come up with a somewhat 
> more agnostic and less (out-of-)fashionable MacPorts description?
> 
> Something like
> 
> "Ports system for the Mac and its OS"
> 
> or what I'd prefer because that's what it's all about:
> 
> "Ports system for Mac users"

The official word from Apple is that it is called "Mac OS" before 10.0, "Mac OS 
X" from 10.0 to 10.7, "OS X" from 10.7 to 10.11, "macOS" from 10.12 onwards, 
and "the Mac operating system" when not specifying a version. Whether we like 
Apple's OS names or not, it's less confusing to users if we use the same 
terminology Apple does.

I have fond memories of System 6 and 7. You can enjoy them again by running 
"sudo port install minivmac-devel" and visiting 
http://www.gryphel.com/c/sw/index.html

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

Re: Starting gimp2

[Ryan Schmidt]

On Sep 25, 2016, at 6:44 AM, Eneko Gotzon wrote:

> On Sun, Sep 25, 2016 at 1:41 PM, Chris Jones wrote:
>> these are not numbers put application versions. 2.8.2 is older than 2.8.18.
> 
> OK Chris, thank you.

It doesn't matter in this case. The GIMP.app installed by the gimp-app port is 
a skeleton app that runs /opt/local/bin/gimp as provided by the gimp2 port. So 
only the version of the gimp2 port is relevant.


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

Re: Macports fails under Sierra?

[Ryan Schmidt]

> On Sep 25, 2016, at 3:37 PM, Dave Horsfall  wrote:
> 
> Upgraded recently to 10.12 Sierra, and "port upgrade" now fails:
> 
>Welcome to the RSYNC daemon on ftp.fau.de.
>Not all of our mirrors are available through rsync.
> 
> 
>receiving file list ... done
>rsync: mkstemp 
> "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/.base.tar.sH7E8E"
>  failed: Permission denied (13)
>inflate returned -3 (19 bytes)
>rsync error: error in rsync protocol data stream (code 12) at 
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-51/rsync/token.c(419)
>  [receiver=2.6.9]
>rsync: connection unexpectedly closed (31 bytes received so far) 
> [generator]
>rsync error: error in rsync protocol data stream (code 12) at 
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-51/rsync/io.c(453)
>  [generator=2.6.9]
>Command failed: /usr/bin/rsync -rtzv --delete-after 
> rsync://rsync.macports.org/release/tarballs/base.tar 
>/opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit 
> code: 12
>Error: Error synchronizing MacPorts sources: command execution failed
>To report a bug, follow the instructions in the guide:
>http://guide.macports.org/#project.tickets
>Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing 
> MacPorts sources: command execution failed
> 
> Yet the directory exists, and is certainly writable by root:
> 
>ls -ld /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
> 
>drwxr-xr-x  5 root  admin  170 Sep 26 06:12 
> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
> 
> Qué?


This doesn't look specific to Sierra, nor does it look like this is the result 
of running "port upgrade"; it looks like the result of running "port 
selfupdate". Are you certain you ran it with "sudo"? "sudo port selfupdate"?


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

Re: 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 <alvarn...@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.lie...@gmail.com> wrote:
>>> 
>>> 2016-09-24 20:17 GMT+02:00 Ryan Schmidt <ryandes...@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@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

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

Re: osxfuse @3.5.0 build error

[Ryan Schmidt]

> On Sep 24, 2016, at 1:37 PM, Davide Liessi <davide.lie...@gmail.com> wrote:
> 
> 2016-09-24 20:17 GMT+02:00 Ryan Schmidt <ryandes...@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@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Ryan Schmidt]

> On Sep 24, 2016, at 1:08 PM, Davide Liessi <davide.lie...@gmail.com> wrote:
> 
> 2016-09-24 19:13 GMT+02:00 Ryan Schmidt <ryandes...@macports.org>:
>> The intention of the portfile is explained in the comments:
>> 
>> # We will build user-space components for the specified arch, and
>> # kernel modules for the kernel arch.
>> 
>> It sounds like your changes will cause it to build the user-space components 
>> for the kernel arch as well, which was not the intention.
> 
> Yes, but without my changes (both for @3.5.0 and @2.8.0) it tries to
> build also the kernel extension with the user-space architecture.
> My change to @2.8.0 was the only way I could get a working osxfuse on
> my machine.
> 
>> I'm not certain how to tell the build system what arch to build the kernel 
>> extension for. It would make sense that it would be able to figure it out on 
>> its own, but I don't know if it does.
> 
> Apparently it does not.
> 
> I copy the relevant part of main.log for the original Portfile without
> my change at the end of the message.
> You can find the same error on the 10.6 buildbot and a very similar
> one on the 10.7 buildbot:
> https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds/5740
> https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/10188

Those logs say the error is:

cc1: warnings being treated as errors
/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/mount_osxfuse/mount_osxfuse.c:
 In function 'send_fd':
/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/mount_osxfuse/mount_osxfuse.c:603:
 warning: implicit conversion shortens 64-bit value into a 32-bit value

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.

The 10.6 log then follows this with:

pbxcp: mount_osxfuse: No such file or directory
pbxcp: mount_osxfuse: No such file or directory


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

Re: A general upgrade question

[Ryan Schmidt]

> On Sep 23, 2016, at 09:41, William H. Magill  wrote:
> 
> I have two systems, an iMac and a Mac Mini. 
> The iMac doesn’t do much - mostly aspell, and so my update to Sierra went 
> quite smoothly. 
> 
> The Mac Mini on the other hand, is a bit more of a workhorse. Primarily 
> acting as a web server.
> And, as I updated to Sierra, I discovered to my chagrin that I had been 
> practicing —If it ain’t broke, don’t fix it. 
> Evidently not updating any ports since I upgraded to El Capitan!
> Oops.
> 
> To make a long story short. 
> Instead of first checking to see what kind of updating I needed to do before 
> tackling the new Mac Ports, I just went ahead
> and followed the migration guide.
> Everything went smoothly until I hit the rebuiild phase:  ./restore_ports.tcl 
> myports.txt
> 
> This command itself worked well — what happened was that the rebuild through 
> lots of warning errors.
> Typically of the type:
> 
> Error: p5.16-perl-ostype has been replaced by p5.22-perl-ostype; please 
> install that instead.
> Error: org.macports.configure for port p5.16-perl-ostype returned: obsolete 
> port

Yup, those are obsolete, replaced by newer perl versions. 


> In investigating, I noted that the command:
>> sudo port outdated
> No installed ports are outdated.
> 
> But that this command:
>> sudo port obsolete
> Error: Unrecognized action "port obsolete”
> 
> That behavior seems to be a bug, but I don’t know the expected behavior.

That's not a bug: "outdated" is a MacPorts subcommand; "obsolete" isn't. 

"outdated" is one of many MacPorts subcommands that prints lists of ports 
formatted in different ways. Other MacPorts list commands include "list", 
"installed" and "echo". "list" defaults to showing all ports. "echo" defaults 
to showing no ports. "installed" defaults to showing installed ports. 
"outdated" defaults to showing outdated ports. You can instruct any of the list 
commands to list a different set of ports. For example, you could "port echo 
obsolete" or "port installed name:^p5.16-". 


> At any rate, what I was attempting to do was generate a list of those 
> obsolete and therefore failed installs
> to make manual installation possible.
> 
> In particular, I’m assuming that there is a parent install which included 
> these as dependencies, and that if I
> re-installed that, it would pick-up all of the others. 
> (I seem to have had a bunch of P5.16 modules installed, which should have 
> been updated before I tried to begin the overall update.)
> 
> Is there an obvious way to find that parent?

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

Re: how to maintain multiple active versions of a port (e.g. octave)?

[Ryan Schmidt]

> On Sep 23, 2016, at 09:04, Ray Zimmerman  wrote:
> 
>> To build a previous version of a port:
>> 
>> https://trac.macports.org/wiki/howto/InstallingOlderPort
>> 
>> You can have multiple versions of a port installed at the same time, but 
>> only one active and usable at a time. You can switch between them by 
>> activating whichever one you want at the moment, but this may have 
>> consequences for any other installed ports that depend on the port whose 
>> version you're switching.
> 
> Ok, this sounds like something I could make use of now. I’m not familiar with 
> the details of what activating a port does. Is it simply a matter of what 
> get’s put in your executable path, or is there more to it?

An installed port is a compressed tarball of files. Activating a port extracts 
that tarball into /opt/local. 

> I guess my real question is, can I create a few symlinks to be able to 
> execute a deactivated octave port without activating it? If so, that may be 
> good enough for my purposes.

No, when a port is not active, the files you propose to symlink against do not 
exist. 


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

Re: status of `pdftk' package

[Ryan Schmidt]

On Sep 23, 2016, at 08:51, j. van den hoff  wrote:
> 
> installation and upgrading of the pdftk package fails (and does so for some 
> time) issuing:
> 
> "pdftk currently does not build on OS X 10.11 or greater"
> 
> any chance to see pdftk working again any time soon? or is it an upstream 
> problem?
> 
> 

See https://trac.macports.org/ticket/48528#comment:36

If this is going to ever work again, somebody needs to make the java compiler 
in the latest gcc work again. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: how to maintain multiple active versions of a port (e.g. octave)?

[Ryan Schmidt]

On Sep 23, 2016, at 08:01, Ray Zimmerman  wrote:
> 
> I am the developer of a Matlab/Octave package that I need to test against 
> multiple versions of Matlab and Octave. I’ve been using MacPorts to build and 
> install Octave on my system and was wondering what is the best way to …
> 
> (1) keep older versions of a port when the port is updated to use a new 
> version of the sources. E.g. the octave port was using octave 3.8.0 sources 
> and has recently changed to 4.0.3. How can I keep the 3.8.0 version available 
> (I can create differently named symlinks to point to the binaries), while 
> allowing MacPorts to build and install the new octave 4.0.3?

Most ports are not meant to be used that way. Most ports are only provided in a 
single version. 

In situations where there is a need to have multiple versions, multiple ports 
are offered and specifically engineered to install in separate locations that 
don't interfere with one another. The php, python, perl, gcc, llvm, clang ports 
are examples of this method. 

If there is a need to do this with the octave ports, the maintainer of the 
octave port would have to do that, or someone would have to help him do it or 
do it for him if he doesn't want to or have time. There are also lots of octave 
module ports, which would then probably have to be offered for each octave 
version. So this would be a major undertaking. 

Such an undertaking can be worthwhile. I'm glad I went to the effort to do it 
for the php ports. In other instances it might not make sense. We did it for 
the perl ports but are having second thoughts about that and may have to go to 
the additional effort of undoing it. So before such an effort is undertaken for 
octave we should be very sure that it's necessary and will be beneficial. 


> (2) build a previous version of a port, again without eliminating the current 
> version. E.g. I recently upgraded to OS X Sierra and had to rebuild all of my 
> ports, so now I have octave 4.0.3, but I’d like to go back and re-install 
> 3.8.0, which I need for testing (without eliminating 4.0.3).

To build a previous version of a port:

https://trac.macports.org/wiki/howto/InstallingOlderPort

You can have multiple versions of a port installed at the same time, but only 
one active and usable at a time. You can switch between them by activating 
whichever one you want at the moment, but this may have consequences for any 
other installed ports that depend on the port whose version you're switching. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: macOS Sierra / 10.12 support - where are we?

[Ryan Schmidt]

> On Sep 21, 2016, at 2:18 PM, Brandon Allbery  wrote:
> 
>> On Wed, Sep 21, 2016 at 3:15 PM, Lawrence Velázquez  
>> wrote:
>> > I recall Ryan mentioning that he was doing so.
>> 
>> I think that was just for Python modules.
>> 
> No, the one I recall was yesterday immediately after Apple released Sierra, 
> and specifically said he was kicking the buildbots to get Sierra builds going.

We've had a buildbot worker set up for Sierra since shortly after Apple 
released the Sierra GM on September 7. Any ports added or updated since then 
have already been built and packaged there, assuming the builds were 
successful. I've also manually kicked off several builds: some compilers, lots 
of libraries, all the python modules.

As of right now, we have packages for the following numbers of ports:

$ for DARWIN in $(seq 9 16); do printf "darwin_$DARWIN: " && find 
/opt/local/var/rsync/macports/packages -name "*darwin_$DARWIN*.rmd160" | cut -d 
/ -f 8 | sort -u | wc -l; done
darwin_9: 3577
darwin_10:15334
darwin_11:12955
darwin_12:16013
darwin_13:16203
darwin_14:19415
darwin_15:12546
darwin_16: 4948

I'm not kicking off a build of "all" ports yet, because we've never tested that 
on our new buildbot configuration. I don't know if it would work at all; don't 
know if we brought over the necessary parts of the old config that knew what to 
do when the port name "all" was provided. We also haven't finished bringing 
over optimizations from the old setup that allowed the previous builds of all 
ports to complete in "only" several weeks. Specifically, we still need the 
optimization that tells the buildbot to skip builds of already-installed ports. 
Without those optimizations, trying to build all ports would just take too 
long. We also still need build failure emails to be sending correctly, so that 
maintainers will know about failures and can look into them. I'm working on 
that now.

Developers are welcome to kick off builds they think would be helpful, by 
logging in here and filling in the name of the port(s) in the "port list" field:

https://build.macports.org/builders/ports-10.12_x86_64-watcher

It's probably best not to try to build more than 100 ports at a time. And 
please try to verify beforehand that the ports you're triggering builds of have 
not already been built.

Developers with commit access who don't yet have access to log in to the 
buildbot may request access by emailing me.

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

Re: is Docker port still supported?

[Ryan Schmidt]

> On Sep 18, 2016, at 9:36 PM, Ron Sidell  wrote:
> 
> Hi,
> 
> Please forgive my ignorance but I'm trying to understand whether the
> Docker port is still being maintained. When I look in Trac, I see
> Changeset 150908 which states that:
> Timestamp: 08/01/16 14:59:33 (7 weeks ago)
> Author: sean@…
> Message: docker: no longer have the time to maintain docker related packages
> And it appears that sean@ changed the maintainer from himself to
> "nomaintainer."
> 
> When I first looked, about 4 weeks ago, 150908 was the most recent
> change, and I assumed that the port was no longer being maintained.
> 
> Then I looked again today and found two changes sets from 3 weeks ago,
> by different users. The most recent is:
> 
> Changeset 152209
> Timestamp: 08/31/16 15:33:23 (3 weeks ago)
> Author: cal@…
> Message: docker: 1.12.1
> 
> But the maintainer is still set to nomaintainer.
> 
> Please help me understand if I should consider to be under active
> maintenance even though nomaintainer is still listed as the maintainer?
> 
> Thanks!
> Ron (a dedicated MacPorts user) thank you to all maintainers!

"nomaintainer" means nobody has agreed to be the port's maintainer, and that 
anybody with commit access may feel free to make changes to it.


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

Re: MacPorts missing links

[Ryan Schmidt]

> On Sep 13, 2016, at 2:06 AM, David Epstein <david.epst...@warwick.ac.uk> 
> wrote:
> 
> 
>> On 13 Sep 2016, at 03:19, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> 
>>> On Sep 12, 2016, at 9:08 PM, Brandon Allbery <allber...@gmail.com> wrote:
>>> 
>>> On Mon, Sep 12, 2016 at 9:59 PM, Ryan Schmidt <ryandes...@macports.org> 
>>> wrote:
>>> What do you get when you run:
>>> port provides /opt/local/lib/libpng.la
>>> 
>>> They actually provided that earlier:
>>> 
>>>> /opt/local/lib/libpng.la  is provided by: libpng
>> 
>> David provided this information about his installation but Sinan didn't yet.
>> 
>> But you know, not only should /opt/local/lib/libpng.la not exist on 
>> Mavericks or later, it shouldn't be a symlink on any system; it should be a 
>> text file.
>> 
>> If it's a symlink on your system, what's it a symlink to?
> 
> Here is the story from my file system
> Macintosh-2:/<2>lib% pwd
> /opt/local/lib
> Macintosh-2:/<2>lib% ls -l libpng.la
> lrwxr-xr-x  1 root  admin  11  6 Sep 10:13 libpng.la@ -> libpng16.la
> Macintosh-2:/<2>lib% port provides libpng.la
> /opt/local/lib/libpng.la is provided by: libpng
> Macintosh-2:/<2>lib% ls libpng*
> libpng.a@ libpng.la@  libpng16.a
> libpng.dylib@ libpng16.16.dylib*  libpng16.dylib@
> Macintosh-2:/<2>lib% ls -l libpng16.la
> ls: libpng16.la: No such file or directory
> Macintosh-2:/<2>lib% port installed libpng
> The following ports are currently installed:
>  libpng @1.6.21_0
>  libpng @1.6.22_0
>  libpng @1.6.23_0
>  libpng @1.6.25_0 (active)
> 
> This looks to me as though it is saying that Ryan was right. the .la file 
> does not exist, only a shadow of it which presumably won’t cause any harm. 
> One question: why the 6 Sept date. Would my uninstall of python have changed 
> the date on the broken symlink?

Let's forget about the libpng.la problem for now. It is a bug in MacPorts base. 
We fixed it in trunk. It will be in the next release of MacPorts. After that 
release, the fix will make its way to each port as those ports are updated.


> One thing that seems to be brought out (by the erroneous answer by “port 
> provides ligpng.la") is that I made a mistake when updating the OS, to have 
> updated my MacPorts installation, rather than reinstalled. I have been 
> hankering after reinstalling, but Ryan persuaded me not to. This seems to be 
> a new bit of evidence that I ought to reinstall, but I would like Ryan to 
> confirm that he now agrees with this, in the light of the new evidence.

You must have reinstalled MacPorts base after upgrading the OS; IIRC, MacPorts 
will not function if you don't; it will just display an error message telling 
you the OS it was built on doesn't match the OS it's running on and refer you 
to the migration instructions.

If you run "sudo port selfupdate" and "port outdated" now, and it shows no 
ports as outdated, then you're fine. If it shows any ports outdated, update 
them, then you'll be fine. No need to reinstall everything.


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

Re: MacPorts missing links

[Ryan Schmidt]

> On Sep 12, 2016, at 9:08 PM, Brandon Allbery <allber...@gmail.com> wrote:
> 
> On Mon, Sep 12, 2016 at 9:59 PM, Ryan Schmidt <ryandes...@macports.org> wrote:
> What do you get when you run:
> port provides /opt/local/lib/libpng.la
> 
> They actually provided that earlier:
> 
> > /opt/local/lib/libpng.la  is provided by: libpng

David provided this information about his installation but Sinan didn't yet.

But you know, not only should /opt/local/lib/libpng.la not exist on Mavericks 
or later, it shouldn't be a symlink on any system; it should be a text file.

If it's a symlink on your system, what's it a symlink to?

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

Re: MacPorts missing links

[Ryan Schmidt]

On Sep 12, 2016, at 6:25 AM, David Epstein wrote:

> When I now run
>> sudo find -L /opt/local -type l -exec port provides {} +
> 
> I get
>> /opt/local/lib/libpng.la is provided by: libpng
>> /opt/local/libexec/qt4/include/QtCLucene is provided by: qt4-mac
>> /opt/local/libexec/qt4/include/QtDesignerComponents is provided by: qt4-mac
>> /opt/local/libexec/qt4/Library/Frameworks/QtCLucene.framework/Headers is 
>> provided by: qt4-mac
> 
> With regard to your remark about libpng, isn’t it the case that the MacPorts 
> guide now indicates that it is not necessary to start from scratch when the 
> OS is upgraded? Anyway, I have not been starting from scratch on MacPorts 
> with recent OS upgrades. So libpng would perhaps have been left over from 
> previous operating systems,. I don’t see why it would have been uninstalled.

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.

Then you should uninstall and reinstall all ports. If you don't do that, 
MacPorts will consider all ports to be outdated, due to the change in macOS 
version number. You can then upgrade them by running "sudo port upgrade 
outdated". This might work, and I've used this method myself. But it's possible 
for you to run into problems with this due to undeclared dependencies. You may 
be able to avoid those problems by using trace mode ("port -t"), at the expense 
of some speed, and also at the expense of running into some other kinds of 
problems. Also, the trace mode in MacPorts 2.3.x may be insufficient; much work 
has been done to improve trace mode in trunk, which will be released as 
MacPorts 2.4, but that hasn't happened yet.

>>> I agree that some of the select group entry names we've chosen are not 
>>> optimal in the way in which they differ from the name of the port they 
>>> provide. It might be a pain to fix that at this late date.
> Presumably you have hard-wired this connection between a select group entry 
> name and some particular Apple binary. How do I find out which Apple binary?

Apple binary or MacPorts binary. One way to find out would be to actually 
select it (e.g. "sudo port select python python27-apple"), then see what binary 
/opt/local/bin/python points to. Usually "port select" makes many symlinks. In 
the case of the python select group, it's not just selecting what 
/opt/local/bin/python points to, but also a handful of other symlinks to other 
programs related to python.

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

Re: MacPorts missing links

[Ryan Schmidt]

> On Sep 12, 2016, at 10:53 AM, Sinan Karasu  wrote:
> 
> 
>> On Sep 12, 2016, at 4:25 AM, David Epstein  
>> wrote:
>> 
>>> sudo find -L /opt/local -type l
>>> For example, libpng.la should not have existed on your system, if your OS 
>>> is Mavericks or later.
> 
> Now you made me curious. My OS is Sierra, and has been for about a month. I 
> had installed MacPorts from sources. At first I couldn’t install much of 
> anything, since I always got an error on Sierra. About a week or so ago, 
> things sorted themselves out.

The Sierra GM has only been out for a few days, with the public release still a 
week away, so do expect a certain amount of problems with MacPorts on Sierra 
for the next month or two as port maintainers upgrade to Sierra, see what the 
problem are, and figure out how to solve them.


> Since then I’ve installed 3 ports(I believe).
> xfig
> ipe
> cgal
> 
> And this is the result I get:
> 
> pirlouit:~ sinan$ sudo find -L /opt/local -type l
> /opt/local/lib/libpng.la
> pirlouit:~ sinan$ 
> 
> The one you say I shouldn’t get. And that is the only one.

.la files are not installed by MacPorts, by default, for the vast majority of 
ports, as of OS X 10.9 Mavericks. The macports.conf setting that controls this 
is delete_la_files. (It is not listed in macports.conf by default because users 
probably shouldn't be overriding it.) Some ports (well, exactly three ports: 
ImageMagick, uriparser, xapian-core) override it because they require their own 
.la files for some reason. libpng does not override it so the .la file should 
not be there.

What do you get when you run:

port provides /opt/local/lib/libpng.la

I assume it will say it's not provided by a MacPorts port, in which case you 
have to ask yourself how it got there, if MacPorts didn't put it there. Did you 
run some third-party installer that put it (and probably other files) there? 
What is the file's creation date, and can you find any other files on your 
system created around the same time that might give you an idea of what it came 
with?

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

Re: qemu, and using gcc45+ compilers on systems set up with LibCxxOnOlderSystems and libc++

[Ryan Schmidt]

> On Sep 11, 2016, at 10:25 PM, Ken Cunningham 
>  wrote:
> 
> I would like to try building qemu, but it doesn't seem to be able to build 
> with clang-3.7 or clang-3.8 (on 10.68 with LibCxxOnOlderSystems and libc++)
> 
> the error for both 
> :info:configure ERROR: Your compiler does not support the __thread specifier 
> for 
> :info:configureThread-Local Storage (TLS). Please upgrade to a 
> version that does.

I remember this error but according to

http://clang.llvm.org/cxx_status.html

clang 3.3 and later do support thread-local storage, provided you have 
libc++abi 3.6 or later, which we do in MacPorts.

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

Re: MacPorts missing links

[Ryan Schmidt]

> On Sep 11, 2016, at 5:37 PM, Lawrence Velázquez <lar...@macports.org> wrote:
> 
>> On Sep 11, 2016, at 6:33 PM, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>>> On Sep 11, 2016, at 5:22 PM, Ryan Schmidt <ryandes...@macports.org> wrote:
>>> 
>>>> On Sep 11, 2016, at 4:57 PM, David Epstein <david.epst...@warwick.ac.uk> 
>>>> wrote:
>>>> 
>>>> I do not understand the issues involved and their ramifications, so I may 
>>>> be saying something stupid, but it seems to me, as a naive user, that this 
>>>> reveals a rather bad design fault in “port select”. An "available version" 
>>>> should either be “none” or the true name of an installed port. I realize 
>>>> that resources  to fix things are scarce, but could the ability to choose 
>>>> a random name at least be acknowledged as bad practice, and could a ticket 
>>>> be provided for work to be done so that this behaviour becomes impossible?
>>> 
>>> I think we don't consider this to be a design fault, but a feature. In 
>>> other words, it was not a mistake that the select group entry can differ 
>>> from a port; it was a deliberate decision to allow that. As has been 
>>> pointed out, we want to be able to select things that are part of macOS and 
>>> are not provided by a port.
>>> 
>>> I agree that some of the select group entry names we've chosen are not 
>>> optimal in the way in which they differ from the name of the port they 
>>> provide. It might be a pain to fix that at this late date.
>> 
>> Maybe we could also display the name of the port, if any, that provides each 
>> select group entry.
> 
> That's an idea, although then entries like "python27-apple" would appear to 
> come from "python_select", which would be a little weird.

Provide a way for a port to override it, so that we can fix that to say that it 
comes from macOS whatever.version.

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

Re: MacPorts missing links

[Ryan Schmidt]

> On Sep 11, 2016, at 5:33 PM, Lawrence Velázquez <lar...@macports.org> wrote:
> 
>> On Sep 11, 2016, at 6:29 PM, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>>> On Sep 11, 2016, at 5:24 PM, Brandon Allbery wrote:
>>>> On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote:
>>>> 
>>>> On my system I see the contents of that directory are provided by the 
>>>> following ports:
>>> 
>>> I think they're complaining that the directory itself should have been 
>>> cleaned up. We don't have the concept of files/directories shared between 
>>> ports, so it just doesn't get listed and therefore doesn't get cleaned up.
>> 
>> MacPorts does delete empty directories whenever a port is deactivated...
> 
> But not all the files in the etc/select tree come from ports.
> 
>   % port provides /opt/local/etc/select/**/current
>   /opt/local/etc/select/gcc/current is not provided by a MacPorts port.
>   /opt/local/etc/select/python/current is not provided by a MacPorts port.
>   /opt/local/etc/select/python2/current is not provided by a MacPorts 
> port.
>   /opt/local/etc/select/python3/current is not provided by a MacPorts 
> port.
>   /opt/local/etc/select/virtualenv/current is not provided by a MacPorts 
> port.
> 
> This is cut from the same cloth as the symlink issue: The selection mechanism 
> is implemented half in base and half in ports, and there's something of an 
> impedance mismatch.

Gotcha, so if you did not have something selected by that group, MacPorts would 
have removed the directory when the last port providing the select group was 
deactivated, but because something was selected, its "current" file prevented 
the deactivate phase from deleting the directory. So we should also fix "port 
select" to remove empty directories when removing the "current" symlink.

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

Re: MacPorts missing links

[Ryan Schmidt]

> On Sep 11, 2016, at 5:22 PM, Ryan Schmidt <ryandes...@macports.org> wrote:
> 
> 
>> On Sep 11, 2016, at 4:57 PM, David Epstein <david.epst...@warwick.ac.uk> 
>> wrote:
>> 
>> Thanks very much for all your work on my issue: much appreciated.
>> 
>> However, it’s looking like too much manual work, and also somewhat 
>> hazardous, at least to me as a non-expert. Moreover, I have no confidence 
>> that everything will be consistent, even if I successfully and correctly 
>> manually delete a number of symlinks, regular files and directories from 
>> /opt/local. Rather than spend more time on the problem, I will now move 
>> /opt/local to /opt/local.old and start again from scratch.
> 
> If you like, but that sounds like a lot of work to me. It didn't sound like 
> there was anything particularly wrong with your old MacPorts installation, 
> aside from a few broken symlinks created by port select, and maybe one or two 
> other broken symlinks whose origins I'm not sure of yet. For example, 
> libpng.la should not have existed on your system, if your OS is Mavericks or 
> later.
> 
> 
>> It will be nice to have a clean installation that I don’t need to work on. 
>> I'm hoping that everything I need will install without error messages, but 
>> maybe that is overoptimistic.
>> 
>> I will avoid using “port select”  on my new installation, until I get the 
>> go-ahead that the problems have been researched and sorted. I’m not sure if 
>> I am allowed to put my name on some kind of cc list for the ticket, since 
>> I’m not intending to work on the problem, but only want to know when it has 
>> gone away.
> 
> There's no need to avoid using "port select", if you want the functionality 
> it provides. It just doesn't automatically remove its symlinks if you later 
> uninstall the port you had asked "port select" to select. Until we fix that, 
> remember to "port select GROUP none", where GROUP is the name of the select 
> group.

And certainly you can Cc yourself on any tickets you're interested in 
following, by clicking the ticket's CcMe! button.



>> I do not understand the issues involved and their ramifications, so I may be 
>> saying something stupid, but it seems to me, as a naive user, that this 
>> reveals a rather bad design fault in “port select”. An "available version" 
>> should either be “none” or the true name of an installed port. I realize 
>> that resources  to fix things are scarce, but could the ability to choose a 
>> random name at least be acknowledged as bad practice, and could a ticket be 
>> provided for work to be done so that this behaviour becomes impossible?
> 
> I think we don't consider this to be a design fault, but a feature. In other 
> words, it was not a mistake that the select group entry can differ from a 
> port; it was a deliberate decision to allow that. As has been pointed out, we 
> want to be able to select things that are part of macOS and are not provided 
> by a port.
> 
> I agree that some of the select group entry names we've chosen are not 
> optimal in the way in which they differ from the name of the port they 
> provide. It might be a pain to fix that at this late date.

Maybe we could also display the name of the port, if any, that provides each 
select group entry.

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

Re: MacPorts missing links

[Ryan Schmidt]

On Sep 11, 2016, at 5:24 PM, Brandon Allbery wrote:
> On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote:
>> On my system I see the contents of that directory are provided by the 
>> following ports:
> 
> I think they're complaining that the directory itself should have been 
> cleaned up. We don't have the concept of files/directories shared between 
> ports, so it just doesn't get listed and therefore doesn't get cleaned up.

MacPorts does delete empty directories whenever a port is deactivated...


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

Re: MacPorts missing links

[Ryan Schmidt]

> On Sep 11, 2016, at 4:57 PM, David Epstein  
> wrote:
> 
> Thanks very much for all your work on my issue: much appreciated.
> 
> However, it’s looking like too much manual work, and also somewhat hazardous, 
> at least to me as a non-expert. Moreover, I have no confidence that 
> everything will be consistent, even if I successfully and correctly manually 
> delete a number of symlinks, regular files and directories from /opt/local. 
> Rather than spend more time on the problem, I will now move /opt/local to 
> /opt/local.old and start again from scratch.

If you like, but that sounds like a lot of work to me. It didn't sound like 
there was anything particularly wrong with your old MacPorts installation, 
aside from a few broken symlinks created by port select, and maybe one or two 
other broken symlinks whose origins I'm not sure of yet. For example, libpng.la 
should not have existed on your system, if your OS is Mavericks or later.


> It will be nice to have a clean installation that I don’t need to work on. 
> I'm hoping that everything I need will install without error messages, but 
> maybe that is overoptimistic.
> 
> I will avoid using “port select”  on my new installation, until I get the 
> go-ahead that the problems have been researched and sorted. I’m not sure if I 
> am allowed to put my name on some kind of cc list for the ticket, since I’m 
> not intending to work on the problem, but only want to know when it has gone 
> away.

There's no need to avoid using "port select", if you want the functionality it 
provides. It just doesn't automatically remove its symlinks if you later 
uninstall the port you had asked "port select" to select. Until we fix that, 
remember to "port select GROUP none", where GROUP is the name of the select 
group.

> Possibly I misunderstand, but your earlier emails seem to imply that you feel 
> that the only problem with “select” in MacPorts is the creation of symlinks 
> that are not deleted when uninstalling.

I would concur with that.

> However, I do not believe this is the whole story. For example, my command
>> port installed ‘*python*3*’
> 
> was answered
>> “None of the specified ports is installed”.
> 
> Nevertheless the directory /opt/local/etc/select/python3 remains on my system 
> as useless clutter and there is no obvious way to delete it except manually, 
> which ought to be a “No-no". This has nothing to do with symlinks.

On my system I see the contents of that directory are provided by the following 
ports:

$ port provides /opt/local/etc/select/python3/*
/opt/local/etc/select/python3/base is provided by: python3_select
/opt/local/etc/select/python3/none is provided by: python3_select
/opt/local/etc/select/python3/python33 is provided by: python33
/opt/local/etc/select/python3/python34 is provided by: python34
/opt/local/etc/select/python3/python35 is provided by: python35

What do you get if you run that "port provides" command?


> A final point, that I hope is not out-of-place. On my system
>> port select —list llvm
> 
> responds with
>> Available versions for llvm:
>>  mp-llvm-3.5
>>  none (active)
> and you have told me that “mp-llvm-3.5” is not the name of a port.

That's correct. The name of the port is llvm-3.5. The name of its llvm select 
group entry is mp-llvm-3.5.

> I do not understand the issues involved and their ramifications, so I may be 
> saying something stupid, but it seems to me, as a naive user, that this 
> reveals a rather bad design fault in “port select”. An "available version" 
> should either be “none” or the true name of an installed port. I realize that 
> resources  to fix things are scarce, but could the ability to choose a random 
> name at least be acknowledged as bad practice, and could a ticket be provided 
> for work to be done so that this behaviour becomes impossible?

I think we don't consider this to be a design fault, but a feature. In other 
words, it was not a mistake that the select group entry can differ from a port; 
it was a deliberate decision to allow that. As has been pointed out, we want to 
be able to select things that are part of macOS and are not provided by a port.

I agree that some of the select group entry names we've chosen are not optimal 
in the way in which they differ from the name of the port they provide. It 
might be a pain to fix that at this late date.





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

Re: MySQL #2002 - No such file or directory

[Ryan Schmidt]

> On Sep 7, 2016, at 10:49 AM, Ignatios Athanasiadis  
> wrote:
> 
> Hello,
> 
> Thank you for the information.
> Are you referring to a mysql.sock or a mysqld.sock file?

I'm referring to the MySQL socket file. Different people and distributions 
configure it in different ways, and with different names. It doesn't matter 
what the file is called, only that it was created by MySQL and is a socket to 
communicate with it.

> The problem was that there was no mysql.sock file anyware in my computer.
> The only socket file I could find was a mysqld.sock one.

Ok, then use mysqld.sock.

> To generate the mysql.sock, I included the code below in the my.cnf file.
> 
> [client]
> port=3306
> socket=/tmp/mysql.sock
> 
> [mysqld]
> port=3306
> socket=/tmp/mysql.sock
> key_buffer_size=16M
> max_allowed_packet=8M
> 
> [mysqldump]
> quick
> 
> Now it works, no error is generated.

You should not configure MySQL to put its socket file in /tmp; that's less 
secure. You should use the socket file in the location where MacPorts puts it, 
which, for mysql57, is /opt/local/var/run/mysql57/mysqld.sock. The default 
MacPorts PHP configuration should already be configured to use the MySQL socket 
from that location.

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

Re: MySQL #2002 - No such file or directory

[Ryan Schmidt]

> On Sep 6, 2016, at 8:33 AM, Ignatios Athanasiadis  
> wrote:
> 
> Hi all,
> 
> I have followed the links below to generate a phpmyadmin server and link it 
> to mysql.
> 
> https://trac.macports.org/wiki/howto/Apache2
> https://trac.macports.org/wiki/howto/MySQL
> https://trac.macports.org/wiki/howto/PHP
> https://trac.macports.org/wiki/howto/MAMP
> 
> and 
> https://coolestguidesontheplanet.com/get-apache-mysql-php-and-phpmyadmin-working-on-osx-10-11-el-capitan/
> 
> However I am getting the error : 
> #2002 - No such file or directory — The server is not responding (or the 
> local server's socket is not correctly configured).
> 
> As stated in the last link I try to make a link to mysql.sock as:
> sudo mkdir /var/mysql
> sudo ln -s /tmp/mysql.sock /var/mysql/mysql.sock
> However, there is no file mysql.sock in /tmp/.
> 
> Do you have any suggestions?
> Thank you very much in advance.

I think the third-party instructions you're referring to are talking about a 
non-MacPorts version of MySQL, which may put its socket file in a different 
location. MacPorts MySQL versions don't put their socket in either /tmp or 
/var/mysql nor is there a good reason for you to try to make it do so. Just use 
the socket file from the location where MacPorts puts it.


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

Re: Possible temporary unavailability of MacPorts due to DNS changes

[Ryan Schmidt]

On Sep 4, 2016, at 10:25 PM, Ryan Schmidt <macpo...@ryandesign.com> wrote:

> I'm switching macports.org to a new DNS provider momentarily.
> 
> Hopefully this will not result in an interruption of service, but it's 
> possible you'll be unable to access the services on macports.org for a short 
> time. This would include selfupdating or syncing MacPorts, downloading binary 
> archives or distfiles from our network of mirror servers, accessing our web 
> sites and source code repository, and sending email to our forwarding 
> addresses.
> 
> DNS changes can take some time to propagate throughout the Internet, so 
> different regions of the world may see outages at different times. If you 
> notice a problem where a server appears to be unavailable, a hostname does 
> not resolve or an email to a macports.org address bounces, please wait an 
> hour, then try again.
> 
> I'll be monitoring the transition and will send out another email once it 
> appears to be completed.
> 
> -Ryan Schmidt, MacPorts management

The change has taken effect everywhere that I can test and it working fine.

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

Possible temporary unavailability of MacPorts due to DNS changes

[Ryan Schmidt]

I'm switching macports.org to a new DNS provider momentarily.

Hopefully this will not result in an interruption of service, but it's possible 
you'll be unable to access the services on macports.org for a short time. This 
would include selfupdating or syncing MacPorts, downloading binary archives or 
distfiles from our network of mirror servers, accessing our web sites and 
source code repository, and sending email to our forwarding addresses.

DNS changes can take some time to propagate throughout the Internet, so 
different regions of the world may see outages at different times. If you 
notice a problem where a server appears to be unavailable, a hostname does not 
resolve or an email to a macports.org address bounces, please wait an hour, 
then try again.

I'll be monitoring the transition and will send out another email once it 
appears to be completed.

-Ryan Schmidt, MacPorts management



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

Re: Qt 5.6 LTS vs. 5.7 - should MacPorts provide both and how?

[Ryan Schmidt]

> On Sep 3, 2016, at 11:49 AM, René J.V. Bertin <rjvber...@gmail.com> wrote:
> 
> On Saturday September 03 2016 10:57:24 Ryan Schmidt wrote:
> 
>> You mustn't change the version in a variant, because MacPorts decides when a 
>> port is outdated based on what's in the portindex, and the portindex only 
>> includes one entry for each port, and the version recorded in the portindex 
>> for a port is the version that would occur with the default variants that 
>> were in effect at the time the portindex was generated 
> 
> Indeed, that's a sufficient reason to avoid this approach.
> 
> The argument doesn't entirely fly though for true legacy variants like Qt 
> 5.3.2 which won't ever change version O:^)

Suppose you hypothetically had a qt5 port with version 5.6.1 but a variant that 
changed version to 5.3.2. Suppose a user installed this port with that variant. 
If the user ran "port outdated", MacPorts would tell them the port is outdated 
because 5.3.2 is less than 5.6.1. If the user tried to upgrade the port, 
nothing would happen because the port is actually up to date, according to the 
variant.

So please, stop contemplating the idea of changing the version in a variant. It 
is not to be done.


>> Actual data would be required to make a decision. If, for example, 5.7 
>> decided to drop support for everything older than El Capitan, I would call 
>> that premature and would use that as a reason not to update to 5.7.
> 
> But then you'd condamn all software that depends on 5.7 features.

In this hypothetical scenario, yes, that's true. I have no knowledge of what 
those features might be or how detrimental omitting them might be.

> Either way, if a variant-based approach is out, the issue becomes less urgent 
> (urgent in the sense that I plan to move my qt5-kde-devel port to 5.7 soon, 
> and would have implement the variant logic straight away). When separate 
> ports are required the decision can be made any time to "fork off" the 
> current 5.6 port(s) (or not).
> 
> R.

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

Re: Qt 5.6 LTS vs. 5.7 - should MacPorts provide both and how?

[Ryan Schmidt]

> On Sep 3, 2016, at 10:10 AM, René J.V. Bertin <rjvber...@gmail.com> wrote:
> 
> On Saturday September 03 2016 08:31:21 Ryan Schmidt wrote:
> 
>> I am inclined to say we don't need to keep 5.6 after upgrading the ports to 
>> 5.7.
> 
> Shouldn't that depend at least in part on what Qt have in mind with that 
> so-called LTS version? If the intention is to are freeer to evolve the 5.7+ 
> versions because there is a supported/maintained "legacy" version, then we 
> may have no other choice but to provide 5.6 too.
> 
> The alternative attitude would be to stick to 5.6 as long as it's supported, 
> and heave a big sigh of relief because of the lull in port maintenance. Which 
> wouldn't exclude providing 5.7+ via a -devel port of course.
> 
>> In any case, using a variant to provide it is not an option. A variant shall 
>> not change the version field.
> 
> Hmmm, are you sure that's a hard rule that isn't violated by any of the 
> existing ports? I don't really see the reason either; what would be wrong 
> with a +legacy variant? Ports cannot depend on specific versions, so the 
> version provided by their dependents should be irrelevant to them. OTOH, it's 
> easier to provide 2 (or more) different versions via variants because that 
> allows ports to use the simplest depends_* declarations if they don't care 
> about version, while those that do can exclude the undesirable variant(s).

You mustn't change the version in a variant, because MacPorts decides when a 
port is outdated based on what's in the portindex, and the portindex only 
includes one entry for each port, and the version recorded in the portindex for 
a port is the version that would occur with the default variants that were in 
effect at the time the portindex was generated (which might have occurred on 
the server, or on the user's system, depending on circumstances).

If there are existing ports that modify the version in a variant, they are 
wrong and need to be fixed.


> Also, ports exist that introduce different version dependencies (on Clang, 
> GCC, python, ...) via variants. Not exactly the same thing, but IMHO not 
> completely different either.

Not related and not a problem.


>> You mentioned support for older OS. What is the minimum OS version for 5.7, 
>> vs 5.6?
> 
> I mentioned that as a possibility I haven't yet had the time to look into 
> this in detail but there's a good chance that later versions will have 
> stricter requirements. With 5.8 already being under active development it 
> seems quite likely that it (or even 5.9) will be released before the 5.6LTS 
> EOL.

Actual data would be required to make a decision. If, for example, 5.7 decided 
to drop support for everything older than El Capitan, I would call that 
premature and would use that as a reason not to update to 5.7.


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

Re: Qt 5.6 LTS vs. 5.7 - should MacPorts provide both and how?

[Ryan Schmidt]

> On Sep 3, 2016, at 5:45 AM, René J.V. Bertin  wrote:
> 
> Hi,
> 
> You may be aware that Qt have designated v5.6 a long-term support version 
> that will be maintained in parallel to 5.7 (already released) and (probably) 
> beyond.
> 
> I still have to look at the exact implications, but this could well put us in 
> a situation where we will need to provide a 5.6 port and a current/latest 
> release version port. In any event it will be necessary to provide a Qt5 port 
> that follows the current/latest release, because that's probably where the 
> real evolution will take place. Qt are usually pretty good at maintaining 
> backward compatibility (even at the ABI level) so it may not be absolutely 
> required to keep a 5.6 release port around, except possibly to ensure 
> compatibility with earlier OS X versions, but again, I have to look into this.
> 
> Anyway, how should we approach this? The Qt portfiles are already pretty 
> complicated, the one for port:qt5 probably even more so than mine for 
> port:qt5-kde. However, my port file and directory have already been set up to 
> support multiple versions.
> 
> So if we're going to support Qt 5.6LTS and Qt 5.7+, it would be most logical 
> for me to implement this via a +LTS variant. Basically that variant would
> 
> - setting a 5.6.x version plus the corresponding checksums (maclhoun's 
> port:qt5 would probably want to put its checksum tables into version-specific 
> files, like I do for the KF5 frameworks)
> - maintain an LTS subdir in ${filespath}, for those patches that are 
> different between 5.6.x and 5.7+
> 
> The drawback would be that the LTS version will require building from source 
> for everyone. If that's an unacceptable hurdle we'd probably be looking at a 
> separate set of ports with their own port dir because I don't really want to 
> introduce yet more subports to my own port:qt5-kde (and I presume mcalhoun 
> will be equally enthusiastic about the idea).
> 
> Using separate ports in their own port dirs *may* be the approach given the 
> least maintenance though, if we presume that 5.6 is going to evolve less 
> (often). Especially since my efforts to make port:qt5-kde and port:qt5 
> drop-in alternatives using path:-style dependency declarations in the 
> PortGroup have already prepared the way for supporting different versions 
> rather than different build flavours through a single mechanism to declare 
> dependencies on Qt.

I am inclined to say we don't need to keep 5.6 after upgrading the ports to 5.7.

In any case, using a variant to provide it is not an option. A variant shall 
not change the version field.

You mentioned support for older OS. What is the minimum OS version for 5.7, vs 
5.6?

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

Re: command not found

[Ryan Schmidt]

Sorry, I really don't know why that would be. It doesn't sound like it's 
related to MacPorts. 

> On Sep 2, 2016, at 09:41, Ignatios Athanasiadis <ignatha...@gmail.com> wrote:
> 
> I just tried to install it again.
> When I use open again nothing happens.
> 
> What is written on Comesole is
> 
> 02/09/2016 15:39:51.424 com.apple.xpc.launchd[1]: 
> (com.adobe.Reader.46112[827]) Service exited due to signal: Interrupt: 2
> 02/09/2016 15:39:55.191 WindowServer[191]: send_datagram_available_ping: pid 
> 443 failed to act on a ping it dequeued before timing out.
> 
> 
>> On 2 Sep 2016, at 15:36, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> Ok, that sounds like a problem with your Adobe Reader. Maybe reinstall that. 
>> 
>>> On Sep 2, 2016, at 09:18, Ignatios Athanasiadis <ignatha...@gmail.com> 
>>> wrote:
>>> 
>>> What I got from Console when i hit the open whatever.pdf command was 
>>> 
>>> 02/09/2016 15:17:17.172 com.apple.xpc.launchd[1]: 
>>> (com.adobe.Reader.46112[741]) Service exited due to signal: Interrupt: 2
>>> 02/09/2016 15:17:18.003 acwebsecagent[219]: License : One or more of the 
>>> License/Public Key can't be NULL
>>> 02/09/2016 15:17:18.004 acwebsecagent[219]: SSLExt : Failed to get ScanSafe 
>>> headers
>>> 02/09/2016 15:17:18.004 acwebsecagent[219]: DownloadUpdatedConfig : Failed 
>>> to download updated config. Host hostedconfig.scansafe.net. Code 0x80004005
>>> 
>>> 
>>>> On 2 Sep 2016, at 15:13, Ignatios Athanasiadis <ignatha...@gmail.com> 
>>>> wrote:
>>>> 
>>>> The file /usr/bin/open is there, however when I type open whatever.pdf, 
>>>> nothing happens nothing is written on terminal and nothing pops up.
>>>>> On 2 Sep 2016, at 15:08, Ryan Schmidt <ryandes...@macports.org> wrote:
>>>>> 
>>>>> 
>>>>>> On Sep 2, 2016, at 9:05 AM, Ignatios Athanasiadis <ignatha...@gmail.com> 
>>>>>> wrote:
>>>>>> 
>>>>>> The files, /opt/local and /opt/local/var/macports/software exist and 
>>>>>> when I run echo $PATH it includes the path /opt/local/bin.
>>>>> 
>>>>> Ok, that's good.
>>>>> 
>>>>>> However, the file /opt/local/bin/port does not exist.
>>>>> 
>>>>> Not sure why the MacPorts program itself got deleted. You could restore 
>>>>> it from your backups, or run our installer again.
>>>>> 
>>>>>> Also when I used to run open whatever.pdf file a pdf file would open. Is 
>>>>>> this a macports related problem as well?
>>>>> 
>>>>> Yes, that's normal macOS behavior. You say that used to happen... what 
>>>>> happens now?
>>>>> 
>>>>> /usr/bin/open is a command provided by macOS. If that's no longer there, 
>>>>> then you have bigger problems, and should reinstall macOS.
>>> 
>> 
> 

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

Re: command not found

[Ryan Schmidt]

Ok, that sounds like a problem with your Adobe Reader. Maybe reinstall that. 

> On Sep 2, 2016, at 09:18, Ignatios Athanasiadis <ignatha...@gmail.com> wrote:
> 
> What I got from Console when i hit the open whatever.pdf command was 
> 
> 02/09/2016 15:17:17.172 com.apple.xpc.launchd[1]: 
> (com.adobe.Reader.46112[741]) Service exited due to signal: Interrupt: 2
> 02/09/2016 15:17:18.003 acwebsecagent[219]: License : One or more of the 
> License/Public Key can't be NULL
> 02/09/2016 15:17:18.004 acwebsecagent[219]: SSLExt : Failed to get ScanSafe 
> headers
> 02/09/2016 15:17:18.004 acwebsecagent[219]: DownloadUpdatedConfig : Failed to 
> download updated config. Host hostedconfig.scansafe.net. Code 0x80004005
> 
> 
>> On 2 Sep 2016, at 15:13, Ignatios Athanasiadis <ignatha...@gmail.com> wrote:
>> 
>> The file /usr/bin/open is there, however when I type open whatever.pdf, 
>> nothing happens nothing is written on terminal and nothing pops up.
>>> On 2 Sep 2016, at 15:08, Ryan Schmidt <ryandes...@macports.org> wrote:
>>> 
>>> 
>>>> On Sep 2, 2016, at 9:05 AM, Ignatios Athanasiadis <ignatha...@gmail.com> 
>>>> wrote:
>>>> 
>>>> The files, /opt/local and /opt/local/var/macports/software exist and when 
>>>> I run echo $PATH it includes the path /opt/local/bin.
>>> 
>>> Ok, that's good.
>>> 
>>>> However, the file /opt/local/bin/port does not exist.
>>> 
>>> Not sure why the MacPorts program itself got deleted. You could restore it 
>>> from your backups, or run our installer again.
>>> 
>>>> Also when I used to run open whatever.pdf file a pdf file would open. Is 
>>>> this a macports related problem as well?
>>> 
>>> Yes, that's normal macOS behavior. You say that used to happen... what 
>>> happens now?
>>> 
>>> /usr/bin/open is a command provided by macOS. If that's no longer there, 
>>> then you have bigger problems, and should reinstall macOS.
> 

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

Re: command not found

[Ryan Schmidt]

> On Sep 2, 2016, at 9:05 AM, Ignatios Athanasiadis  
> wrote:
> 
> The files, /opt/local and /opt/local/var/macports/software exist and when I 
> run echo $PATH it includes the path /opt/local/bin.

Ok, that's good.

> However, the file /opt/local/bin/port does not exist.

Not sure why the MacPorts program itself got deleted. You could restore it from 
your backups, or run our installer again.

> Also when I used to run open whatever.pdf file a pdf file would open. Is this 
> a macports related problem as well?

Yes, that's normal macOS behavior. You say that used to happen... what happens 
now?

/usr/bin/open is a command provided by macOS. If that's no longer there, then 
you have bigger problems, and should reinstall macOS.



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

Re: command not found

[Ryan Schmidt]

> On Sep 2, 2016, at 7:54 AM, Ignatios Athanasiadis  
> wrote:
> 
> Hi all,
> 
> I tried to restore some files in my mac and they were restored unsuccesfully.
> Now whe I try to access macports I get a command like: command not found.
> Does this mean that I have lost all my ports?
> 
> Many thanks.

This doesn't necessarily mean that anything is gone. It could just mean that 
your PATH has been reset to its default value.

Does /opt/local still exist? Does /opt/local/bin/port still exist? If so, 
proceed:

What happens if you run:

echo $PATH

Does it include /opt/local/bin? If not, fix your PATH definition in your 
~/.profile or ~/.bash_profile.


If you follow Chris' suggestion to re-run the MacPorts installer, it will 
automatically fix your PATH for you, if that was the problem. It will also 
reinstall /opt/local/bin/port and the other parts of MacPorts, without 
affecting any ports you had installed.


You can also check /opt/local/var/macports/software. That's where your 
installed ports are stored. If that directory exists and contains lots of 
stuff, then your ports are still installed.

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

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ryan Schmidt]

On Aug 27, 2016, at 12:41, [ftp83plus]  wrote:
> 
> So, after reinstalling Mac OS X as I did to get out of the startup crash as I 
> did, even if ports stayed in place, I should re-perform the 
> LibcxxOnOlderSystems steps?

In general, no, reinstalling the same version of macOS does not necessitate 
reinstalling MacPorts and your ports. However, the issues Mihai noted may 
require reinstalling the affected ports. I'm not an expert at reading crash 
logs so I can't say for certain why your crash occurred. I just know that when 
a crash occurs, you should provide the crash log so that someone who is more 
familiar might be able to help. 



>> El 2016-08-27, a las 12:17, Mihai Moldovan escribió:
>> 
>>> On 27.08.2016 04:00 PM, [ftp83plus] wrote:
>>> Crash log, approximately when gtk3 segfaulted:
>>> 
>>> http://pastebin.com/bzuez8Xp
>> 
>> In there, I see two things that look weird:
>> 
>> - you're using ld64-136, although step 8 and 9 of the LibcxxOnOlderSystems
>>   guide explicitly says to switch to ld64-latest
>> - ld64-136 was installed with +llvm37, although step 5 and 7 make sure that
>>   +llvm38 is used
>> 
>> The second problem may be explicable by upgrading - earlier versions probably
>> used llvm37 and the llvm38 change is relatively new.
>> 
>> Still, your setup is broken/deviates from what is advertised to work on 10.6.
>> That crash is probably a consequence of that.

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

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ryan Schmidt]

> On Aug 27, 2016, at 00:45, [ftp83plus] <ges...@ftp83plus.net> wrote:
> 
> See attached:
> 
> Link:
> http://ovh.to/jgFHoPk

That's the main.log generated by MacPorts. I meant the crash log generated by 
macOS. It'll be in your DiagnosticReports directory. 


> 
>> El 2016-08-26, a las 19:24, Ryan Schmidt escribió:
>> 
>> 
>>> On Aug 26, 2016, at 10:51 AM, [ftp83plus] <ges...@ftp83plus.net> wrote:
>>> 
>>> Knowing that a Segmentation fault doesn't mean much, I cleaned gtk3 at 
>>> attempted a rebuild, but it still segfaults for some reason.
>> 
>> Could you attach the crash log?
> 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

[Ryan Schmidt]

> On Aug 26, 2016, at 10:51 AM, [ftp83plus]  wrote:
> 
> Knowing that a Segmentation fault doesn't mean much, I cleaned gtk3 at 
> attempted a rebuild, but it still segfaults for some reason.

Could you attach the crash log?

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

Re: MacPorts fail to "upgrade outdated" after reinstalling Mac OS X

[Ryan Schmidt]

> On Aug 25, 2016, at 11:59, [ftp83plus]  wrote:
> 
> However I do remember one dialog asking me if I wanted to install command 
> line tools. Does it come up with a "clean" install of XCode / Mac OS X?

I think Apple added that in Lion.


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

Re: MacPorts fail to "upgrade outdated" after reinstalling Mac OS X

[Ryan Schmidt]

> On Aug 24, 2016, at 21:37, Brandon Allbery <allber...@gmail.com> wrote:
> 
> 
>> On Wed, Aug 24, 2016 at 10:33 PM, Ryan Schmidt <ryandes...@macports.org> 
>> wrote:
>> 
>> That change came in Xcode 4.
> 
> hrr, right, I did end up getting xcode 4 on there (still don't understand how 
> unless there was a brief window before they made it pay only...)

I think that must have been the case. You're not the first person I've heard 
say that. ___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: MacPorts fail to "upgrade outdated" after reinstalling Mac OS X

[Ryan Schmidt]

On Aug 24, 2016, at 21:29, Brandon Allbery <allber...@gmail.com> wrote:
> 
> On Wed, Aug 24, 2016 at 10:03 PM, Ryan Schmidt <ryandes...@macports.org>
> wrote:
>> 
>> ...which, back in the Snow Leopard days, were not separate from Xcode.
>> Rerun the Xcode installer.
> 
> Hm, I recall them being installable via the download pane in Preferences
> back then (I stayed with SL quite a while).

That change came in Xcode 4. 

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

Re: MacPorts fail to "upgrade outdated" after reinstalling Mac OS X

[Ryan Schmidt]

On Aug 24, 2016, at 20:56, Brandon Allbery  wrote:
> 
> 
>> On Wed, Aug 24, 2016 at 9:55 PM, [ftp83plus]  wrote:
>> Unable to open port: can't read "build.cmd": Failed to locate 'make' in 
>> path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at 
>> its MacPorts configuration time location, did you move it?
> 
> You forgot to install the command line tools.

...which, back in the Snow Leopard days, were not separate from Xcode. Rerun 
the Xcode installer. 

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

Re: rxvt-unicode extremely slow to start

[Ryan Schmidt]

> On Aug 24, 2016, at 3:29 PM, Clemens Lang  wrote:
> 
> Hi,
> 
> On Wed, Aug 24, 2016 at 02:02:22PM -0500, Ken Preslan wrote:
>>> Smells an aweful lot like a font-cache update going on in the
>>> background. Start urxvt under opensnoop:
>>> 
>>> Shell 1: sudo opensnoop -n rxvt-unicode (or whatever the process name is)
>>> Shell 2: urxvt
>>> 
>>> If it shows opening thousands of font files it's updating the font
>>> cache. The question then would be why it doesn't keep the cache. Maybe
>>> the location where it tries to put the cache isn't writable?
>> 
>> I see the same thing with "emacs +x11".  If I revert the "fontconfig"
>> package back to r149841, the problem goes away.
> 
> I'd say that's the very definition of a regression (even though it
> doesn't happen for me). Can I ask you to file a ticket with your
> findings so that the maintainer can have a look?

Possibly related to https://trac.macports.org/ticket/52088

We also have another regression in https://trac.macports.org/ticket/52029

I'm not looking into these issues as I'm busy with other things.

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

Re: Updating tk +quartz failed on Snow Leopard

[Ryan Schmidt]

> On Aug 23, 2016, at 9:10 PM, Kevin Walzer <k...@codebykevin.com> wrote:
> 
> On 8/23/16 10:04 PM, Ryan Schmidt wrote:
>> 
>> This is weird because the backingScaleFactor method is supposed to return a 
>> double, not an id, and is part of the Retina display API introduced in Mac 
>> OS X 10.7. It is not in 10.6. The window should not be responding to the 
>> backingScaleFactor selector on 10.6, so that if statement should never have 
>> returned true and that code should never have been run.
> 
> While I'm not the author of that code, I did commit it, and you're right, it 
> should not have run. What compiler is this error being triggered on?

Apple gcc-4.2.1, the default compiler on Snow Leopard with Xcode 3.2.6.


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

Re: Updating tk +quartz failed on Snow Leopard

[Ryan Schmidt]

> On Aug 23, 2016, at 8:40 PM, Richard L. Hamilton <rlha...@smart.net> wrote:
> 
> 
>> On Aug 23, 2016, at 21:06, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> 
>>> On Aug 23, 2016, at 8:03 PM, Richard L. Hamilton <rlha...@smart.net> wrote:
>>> 
>>> 
>>>> On Aug 23, 2016, at 10:38, Ryan Schmidt <ryandes...@macports.org> wrote:
>>>> 
>>>> On Aug 23, 2016, at 07:02, Mojca Miklavec <mo...@macports.org> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>>> On 23 August 2016 at 02:00, Ken Cunningham wrote:
>>>>>>> On 2016-08-22, at 3:48 PM, Richard L. Hamilton wrote:
>>>>>>> Updating tk failed on Snow Leopard, trying to update to the current 
>>>>>>> tk@8.6.6 (probably +quartz+universal, given that's what the current 
>>>>>>> @8.6.5_0 is)
>>>>>> Hi Richard,
>>>>>> 
>>>>>> I have tk 8.6.6 running on snow leopard, but with +x11 (and not 
>>>>>> universal, but x86_64)
>>>>>> 
>>>>>> $ port -v installed tk
>>>>>> The following ports are currently installed:
>>>>>> tk @8.6.6_0+x11 (active) platform='darwin 10' archs='x86_64'
>>>>>> 
>>>>>> for what that's worth. I installed it with clang-3.7, and my first 
>>>>>> thought is that your compiler might be too old. You might try installing 
>>>>>> clang-3.7 (and ld64/cctools/llvm-3.7 that go along with it) and see 
>>>>>> where that takes you
>>>>> 
>>>>> The "official" binaries are indeed available for 10.6 and they were
>>>>> compiled with the default compiler:
>>>>> http://packages.macports.org/tk/
>>>>> 
>>>>> I can confirm that tk +quartz compiles fine for me on 10.7, but not on
>>>>> 10.6 (not even with clang 3.4, I didn't test with 3.7).
>>>>> 
>>>>> I don't find a ticket in the tracker, so feel free to open one. The
>>>>> closest one I found was
>>>>> https://trac.macports.org/ticket/22994
>>>>> but that one is ancient and most likely unrelated.
>>>> 
>>>> The official binaries are built on a system with Xcode 3.2.6 and therefore 
>>>> use gcc-4.2, which evidently works. 
>>>> 
>>>> The user is using Xcode 4.2, and the log shows llvm-gcc-4.2 is being used, 
>>>> which evidently doesn't work. We should blacklist that compiler in the 
>>>> port. 
>>>> 
>>> 
>>> While the problems may not be identical depending on the compiler, that 
>>> alone isn't the answer.  I installed Xcode 3.2.6 (and made sure that 
>>> xcode-select -print-path showed that version), and it still failed.  I 
>>> cleaned and added -universal...and it still failed.  I did that again 
>>> adding -quartz...and it found the pre-built binaries.
>>> 
>>> I see the pre-built hasn't used +quartz for a number of versions, although 
>>> I have evidently gotten it to work before:
>>> sh-3.2# port installed tk
>>> The following ports are currently installed:
>>> tk @8.6.5_0+quartz+universal
>>> tk @8.6.6_0+x11 (active)
>>> 
>>> So the problem may be specific to trying to build tk@8.6.6_0+quartz.
>> 
>> Yes, I agree, sorry, Mojca responded to me privately that the problem isn't 
>> the compiler, it's the +quartz variant, and I confirmed that on my system 
>> too. This problem needs to be reported to the developers of tk so it can be 
>> fixed.
>> 
>> +quartz used to be the default variant but it was changed last year:
>> 
>> https://trac.macports.org/changeset/141308
> 
> The problem is also specific to some OS versions, Snow Leopard for sure.  I 
> have the current version on El Capitan with +quartz, no problem.

No doubt they made a change and tested it on a recent version of macOS before 
releasing it.


> Is there an email or URL for reporting that?  And someone other than me with 
> Snow Leopard around for testing, since I certainly don't know how to turn 
> their tarball into a locally installable port bundle.

Looks like these are the bug reporting instructions:

http://wiki.tcl.tk/1020


I think the problem is the addition of this code in tk 8.6.6, though I don't 
understand why it's a problem:


@@ -885,7 +890,19 @@
 intbitmap_pad = 0;
 intbytes_per_row = 4*width;
 int 

Re: Updating tk failed on Snow Leopard

[Ryan Schmidt]

> On Aug 23, 2016, at 8:03 PM, Richard L. Hamilton <rlha...@smart.net> wrote:
> 
> 
>> On Aug 23, 2016, at 10:38, Ryan Schmidt <ryandes...@macports.org> wrote:
>> 
>> On Aug 23, 2016, at 07:02, Mojca Miklavec <mo...@macports.org> wrote:
>>> 
>>> Hi,
>>> 
>>>> On 23 August 2016 at 02:00, Ken Cunningham wrote:
>>>>> On 2016-08-22, at 3:48 PM, Richard L. Hamilton wrote:
>>>>> Updating tk failed on Snow Leopard, trying to update to the current 
>>>>> tk@8.6.6 (probably +quartz+universal, given that's what the current 
>>>>> @8.6.5_0 is)
>>>> Hi Richard,
>>>> 
>>>> I have tk 8.6.6 running on snow leopard, but with +x11 (and not universal, 
>>>> but x86_64)
>>>> 
>>>> $ port -v installed tk
>>>> The following ports are currently installed:
>>>> tk @8.6.6_0+x11 (active) platform='darwin 10' archs='x86_64'
>>>> 
>>>> for what that's worth. I installed it with clang-3.7, and my first thought 
>>>> is that your compiler might be too old. You might try installing clang-3.7 
>>>> (and ld64/cctools/llvm-3.7 that go along with it) and see where that takes 
>>>> you
>>> 
>>> The "official" binaries are indeed available for 10.6 and they were
>>> compiled with the default compiler:
>>>  http://packages.macports.org/tk/
>>> 
>>> I can confirm that tk +quartz compiles fine for me on 10.7, but not on
>>> 10.6 (not even with clang 3.4, I didn't test with 3.7).
>>> 
>>> I don't find a ticket in the tracker, so feel free to open one. The
>>> closest one I found was
>>>  https://trac.macports.org/ticket/22994
>>> but that one is ancient and most likely unrelated.
>> 
>> The official binaries are built on a system with Xcode 3.2.6 and therefore 
>> use gcc-4.2, which evidently works. 
>> 
>> The user is using Xcode 4.2, and the log shows llvm-gcc-4.2 is being used, 
>> which evidently doesn't work. We should blacklist that compiler in the port. 
>> 
> 
> While the problems may not be identical depending on the compiler, that alone 
> isn't the answer.  I installed Xcode 3.2.6 (and made sure that xcode-select 
> -print-path showed that version), and it still failed.  I cleaned and added 
> -universal...and it still failed.  I did that again adding -quartz...and it 
> found the pre-built binaries.
> 
> I see the pre-built hasn't used +quartz for a number of versions, although I 
> have evidently gotten it to work before:
> sh-3.2# port installed tk
> The following ports are currently installed:
>  tk @8.6.5_0+quartz+universal
>  tk @8.6.6_0+x11 (active)
> 
> So the problem may be specific to trying to build tk@8.6.6_0+quartz.

Yes, I agree, sorry, Mojca responded to me privately that the problem isn't the 
compiler, it's the +quartz variant, and I confirmed that on my system too. This 
problem needs to be reported to the developers of tk so it can be fixed.

+quartz used to be the default variant but it was changed last year:

https://trac.macports.org/changeset/141308



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