unbound logfile rotation, how?

[FritzS - gmx]

I use on my mac unbound as my own resolve DNS.
Before I used ISC BIND named.

At unbound I miss the feature (as ISC BIND named have) to take a automatically 
logfile rotation.

How could that with unbound do?  Start or stop script? Or additional tool?

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

sometimes unbound restart don't work well from terminal

[FritzS - gmx]

Hi,
sometimes need to restart unbound from the terminal.

To stop I use
$ sudo /opt/local/bin/port unload unbound

to start
$ sudo /opt/local/bin/port load unbound

But it don’t running.

If I use again
$ sudo /opt/local/bin/port load unbound

it comes the message unbound it's running, but it don’t work well and not seen 
in the process list.

This option don’t work too:
$ launchctl unload -w /Library/LaunchDaemons/org.macports.unbound.plist
$ launchctl load -w /Library/LaunchDaemons/org.macports.unbound.plist

I use macOS El Capitan 10.11.6 and the application firewall LittleSnitch too, 
the Mac firewall is enabled and unbound could communicate in both directions by 
rules.

The only way I could do to run unbound, reboot my Mac. What could be wrong?

…… 

About LittleSnitch
https://obdev.at/products/littlesnitch/

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

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

[Ken Cunningham]

OK Mike,

If you care to try out a MacPorts build of OpenJK yourself, the Portfile is in 
reasonable working condition.

> 

I have not yet added in all the deps -- this builds through on my system. I 
have SDL1.2 and SDL2 installed, and lots of others. I'll figure that out on a 
VM I use for that.

You might run into a missing dependency. Let me know.

Also - I don't actually own this game, so I don't have the associated files to 
make it actually work at present.

This site  
seems to have sorted out where to put the files.

I think they can go in ~/Library/Application Support/OpenJK/base

but let me know.

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

Fork in MacPorts Users list?

[Fielding, Eric J (329A)]

Hello,

Since yesterday, I noticed that I am now getting MacPorts “macports-users 
Digest” email from two different lists, one at “macosforge.org” (Vol 125, Issue 
10 today) and one at “macports.org” (Vol 129, Issue 19 today). Is this a fork 
of the MacPorts Users mailing list or a transition? I am sending this to both 
lists, so I apologize to those who get two copies if they are subscribed to 
both. I remember there was some transition last year, but I don’t remember the 
details of what was supposed to happen to the lists.

Thanks,
++Eric

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

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

[Mike Crawford]

HFS had file IDs.  I'm not sure about HFS+.  You could open a file by its ID.

Suppose you had a file on the desktop then copied it into a folder.
Or alternatively you have a file in a folder and copy it to the
desktop.  The file IDs for each scenario will be different.

(Hope that makes sense.)
Mike Crawford, Baritone
mdcrawf...@gmail.com

  One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light.


On Sat, May 27, 2017 at 11:32 PM, Ken Cunningham
 wrote:
>>
>> Oh -- did you know that the filenames displayed in finder do not have to 
>> have any correlation to the filenames as seen by the shell and other 
>> programs? Or that Finder is perfectly happy to display two different "files 
>> with the same name"?
>
> In fact, I did notice that, and was rather confused by it. Maybe a fresh look 
> in the morning might sort that out!
>
> Ken
> ___
> 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: Can brew and port be used on the same system?

[Ken Cunningham]

> 
> Oh -- did you know that the filenames displayed in finder do not have to have 
> any correlation to the filenames as seen by the shell and other programs? Or 
> that Finder is perfectly happy to display two different "files with the same 
> name"?

In fact, I did notice that, and was rather confused by it. Maybe a fresh look 
in the morning might sort that out!

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

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

[Michael]

On 2017-05-27, at 11:24 PM, Ken Cunningham  
wrote:

> It sounds like you got a build working already, so you probably done care 
> about this anymore, but this Portfile

Works? It launches. It behaved so poorly that ... yuck.

> 
> 
> with it's associated patches actually does build the port.
> 
> I have not added in the deps yet. It builds just fine on my system, but I 
> have hundreds of deps installed already. You might run into a missing dep.
> 
> Also, although I downloaded the game from the wayback machine
> 
> 
> 
> I have not yet figured out where to exactly put all the files to make 
> everything work.
> 
> Perhaps you can help with that?

Sure. I'll go over all that in the morning when my brain is fresh.

The source code on github has a lot of bug fixes and patches (about 2 years of 
active development).

Oh -- did you know that the filenames displayed in finder do not have to have 
any correlation to the filenames as seen by the shell and other programs? Or 
that Finder is perfectly happy to display two different "files with the same 
name"?

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

---
Entertaining minecraft videos
http://YouTube.com/keybounce

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

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

[Ken Cunningham]

It sounds like you got a build working already, so you probably done care about 
this anymore, but this Portfile



with it's associated patches actually does build the port.

I have not added in the deps yet. It builds just fine on my system, but I have 
hundreds of deps installed already. You might run into a missing dep.

Also, although I downloaded the game from the wayback machine



I have not yet figured out where to exactly put all the files to make 
everything work.

Perhaps you can help with that?

Thanks, 

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

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

[Mike Crawford]

You could install OS X in a VirtualBox virtual machine, then use
nothing but brew there.
Mike Crawford, Baritone
mdcrawf...@gmail.com

  One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light.


On Sat, May 27, 2017 at 9:33 PM, Ken Cunningham
 wrote:
> I'm about 95% finished a Portfile for OpenJK. It doesn't take but a few
> minutes to make one for a port like this. It's fully built and sitting on my
> hard drive. Just working out a patchfile or two for an openGL glitch on
> MacOS that is widely known, and I'll test it out. If it works, I'll send you
> the Portfile.
>
> Portfiles for games like this usually involve a couple of "hacks" that are
> generally frowned upon in the rather pure environment of the MacPorts repo.
> So you might need to install it "rogue". We'll see.
>
> Ken
>
>
> On 2017-05-27, at 9:02 PM, Mark Anderson wrote:
>
> Yes, but I'd advise against it. I thought I had to for RVM and it caused me
> loads of trouble. Then I learned I could set it to MacPorts and a deleted
> brew and never looked back. I've been using MacPorts since before Intel, so
> I'm attached.
>
> —Mark
> ___
> Mark E. Anderson 
>
> On Sat, May 27, 2017 at 10:22 PM, Al Varnell  wrote:
>>
>> I'm told it can be done now, but can get messy. I gave up on brew several
>> years ago. Too many conflicts back then.
>>
>> Sent from Janet's iPad
>>
>> -Al-
>> --
>> Al Varnell
>> Mountain View, CA
>>
>> On May 27, 2017, at 7:13 PM, Michael  wrote:
>> > So apparently the open source code version of Jedi Knights Academy and
>> > Outcast https://github.com/JACoders/OpenJK rely on brew's SDL 2, and have
>> > that installation pathname in their binaries.
>> >
>> > Can I install brew, with its use of /usr/local/, at the same time as
>> > ports?
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
>
>
> ___
> 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
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

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

[Michael]

On 2017-05-27, at 9:33 PM, Ken Cunningham  
wrote:

> I'm about 95% finished a Portfile for OpenJK. It doesn't take but a few 
> minutes to make one for a port like this. It's fully built and sitting on my 
> hard drive. Just working out a patchfile or two for an openGL glitch on MacOS 
> that is widely known, and I'll test it out. If it works, I'll send you the 
> Portfile.

Oh, do you mean any of the following:
1. Screen color calibration is ignored and it suddenly goes "very blue" as soon 
as an openGL program launches,
2. External trackpads (not USB, but with a system driver program) fail to work
3. "resolution settings" that forget about the size of the menu bar / title bar 
for a window mode
4. "resolution settings" that don't actually fetch the 16:10 settings? Or that 
don't fetch the actual monitor
5. Only the built-in monitor's calibration is ignored, an external monitor 
stays unaffected

I found it amazing that the original version could identify the retina 
resolutions, and use them (nb: the default was the raw 2800-something highest 
resolution, even if you asked for a window), while the OpenJK (I got it to work 
with a symlink to the macports SDL) wanted to give me IBM style 4:3 
resolutions. Neither could tell that I had a 720p external monitor, nor give me 
the resolutions for that, and the openJK was willing to give me a triple width 
(labeled surround) which seemed to assume I had a three monitor setup.

For what it's worth, I still hate games that assume "Your computer is nothing 
more than a 1984-era single process thing, just more powerful; we'll take over 
everything on your system/screen, because you can't possibly have anything else 
happening if you want to play a game".

(NB: If you have to hard-code in stuff like a 1024x576, or similar for a 698p 
(720 - 22), to get a window mode that actually fits on-screen because there's 
no programmatic way to fetch "available windowed space", that's OK with me :-).

> Portfiles for games like this usually involve a couple of "hacks" that are 
> generally frowned upon in the rather pure environment of the MacPorts repo. 
> So you might need to install it "rogue". We'll see.
> 
> Ken
> 
> 
> On 2017-05-27, at 9:02 PM, Mark Anderson wrote:
> 
>> Yes, but I'd advise against it. I thought I had to for RVM and it caused me 
>> loads of trouble. Then I learned I could set it to MacPorts and a deleted 
>> brew and never looked back. I've been using MacPorts since before Intel, so 
>> I'm attached.
>> 
>> —Mark
>> ___
>> Mark E. Anderson 
>> 
>> On Sat, May 27, 2017 at 10:22 PM, Al Varnell  wrote:
>> I'm told it can be done now, but can get messy. I gave up on brew several 
>> years ago. Too many conflicts back then.
>> 
>> Sent from Janet's iPad
>> 
>> -Al-
>> --
>> Al Varnell
>> Mountain View, CA
>> 
>> On May 27, 2017, at 7:13 PM, Michael  wrote:
>> > So apparently the open source code version of Jedi Knights Academy and 
>> > Outcast https://github.com/JACoders/OpenJK rely on brew's SDL 2, and have 
>> > that installation pathname in their binaries.
>> >
>> > Can I install brew, with its use of /usr/local/, at the same time as ports?

---
Entertaining minecraft videos
http://YouTube.com/keybounce

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

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

[Ken Cunningham]

I'm about 95% finished a Portfile for OpenJK. It doesn't take but a few minutes 
to make one for a port like this. It's fully built and sitting on my hard 
drive. Just working out a patchfile or two for an openGL glitch on MacOS that 
is widely known, and I'll test it out. If it works, I'll send you the Portfile.

Portfiles for games like this usually involve a couple of "hacks" that are 
generally frowned upon in the rather pure environment of the MacPorts repo. So 
you might need to install it "rogue". We'll see.

Ken


On 2017-05-27, at 9:02 PM, Mark Anderson wrote:

> Yes, but I'd advise against it. I thought I had to for RVM and it caused me 
> loads of trouble. Then I learned I could set it to MacPorts and a deleted 
> brew and never looked back. I've been using MacPorts since before Intel, so 
> I'm attached.
> 
> —Mark
> ___
> Mark E. Anderson 
> 
> On Sat, May 27, 2017 at 10:22 PM, Al Varnell  wrote:
> I'm told it can be done now, but can get messy. I gave up on brew several 
> years ago. Too many conflicts back then.
> 
> Sent from Janet's iPad
> 
> -Al-
> --
> Al Varnell
> Mountain View, CA
> 
> On May 27, 2017, at 7:13 PM, Michael  wrote:
> > So apparently the open source code version of Jedi Knights Academy and 
> > Outcast https://github.com/JACoders/OpenJK rely on brew's SDL 2, and have 
> > that installation pathname in their binaries.
> >
> > Can I install brew, with its use of /usr/local/, at the same time as ports?
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
> 
> ___
> 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: Can brew and port be used on the same system?

[Mark Anderson]

Yes, but I'd advise against it. I thought I had to for RVM and it caused me
loads of trouble. Then I learned I could set it to MacPorts and a deleted
brew and never looked back. I've been using MacPorts since before Intel, so
I'm attached.

—Mark
___
Mark E. Anderson 

On Sat, May 27, 2017 at 10:22 PM, Al Varnell  wrote:

> I'm told it can be done now, but can get messy. I gave up on brew several
> years ago. Too many conflicts back then.
>
> Sent from Janet's iPad
>
> -Al-
> --
> Al Varnell
> Mountain View, CA
>
> On May 27, 2017, at 7:13 PM, Michael  wrote:
> > So apparently the open source code version of Jedi Knights Academy and
> Outcast https://github.com/JACoders/OpenJK rely on brew's SDL 2, and have
> that installation pathname in their binaries.
> >
> > Can I install brew, with its use of /usr/local/, at the same time as
> ports?
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

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

[Al Varnell]

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

Sent from Janet's iPad

-Al-
-- 
Al Varnell
Mountain View, CA

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

Can brew and port be used on the same system?

[Michael]

So apparently the open source code version of Jedi Knights Academy and Outcast 
https://github.com/JACoders/OpenJK rely on brew's SDL 2, and have that 
installation pathname in their binaries.

Can I install brew, with its use of /usr/local/, at the same time as ports?
---
Entertaining minecraft videos
http://YouTube.com/keybounce

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

Error installing bash on Sierra

[Barrie Stott]

Some months ago I moved to Sierra from El Capitan and started upgrading my 
ports. Nothing went as it should and I became ill at about the same time. I 
abandoned everything until I was feeling better and that time has now arrived. 
Following the instructions in MacPorts Guide I cleaned out all my old ports 
and, using the list of ports given in myports.txt, began installing the ports 1 
by 1 from the beginning: ack, autoconf, automake, bash. (I would give variants 
but there has been none so far.)

All went quickly and smoothly until bash which gave errors. I enclose the log 
file but line 9 gave me some cause for concern:

:debug:main OS darwin/16.6.0 (Mac OS X 10.12) arch i386

My 'Apple->About this Mac' says I have Sierra 10.12.5 and, being on an iMac, it 
should say arch x86_64. Also my Updates log says that my latest Sierra update 
was to 10.12.5 on 24th May.

If anyone can give me suggestions as to where to go from here, I’m all ears.

Barrie.   

main.log
Description: Binary data
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: py34-rpy2 port dependence on R...

[Carlo Tambuatco]

> On May 11, 2017, at 1:10 PM, Christopher Jones  
> wrote:
> 
> 
>> On 11 May 2017, at 5:56 pm, Carlo Tambuatco  wrote:
>> 
>> 
>>> On May 11, 2017, at 12:52 PM, Christopher Jones  
>>> wrote:
>>> 
>>> I would suggest the opposite instead. Remove your external R and just use 
>>> the MacPorts version. Any reason not to do this ? In general MacPorts 
>>> (rightly) ignores anything outside its ${prefix}.
>> 
>> 
>> Well, the version of R under macports is a version or two behind the R 
>> project version, so I was wondering if I could just tell macports to 
>> recognize my version.
> 
> The version in MacPorts is already 3.4.0 Is this not the most recent release ?

Is it? Alright, it wasn’t the last time I checked several days ago...


> 
> https://www.r-project.org
> 
> 
>> 
>>> 
>>> Chris
>>> 
 On 6 May 2017, at 3:54 am, Carlo Tambuatco  wrote:
 
 I have the R.app application installed from the R project which also 
 installs the R binary executable in my /usr/local/bin directory, so the 
 point is I have R installed but it is not under macports control.
 
 Is there a way to tell macports that I have R installed externally and get 
 the py34-rpy2 port to use my installation instead of having to install the 
 R port via macports? And if so, have this change persist through port 
 upgrades…?
 
 Thanks.
 ___
 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: py34-rpy2 port dependence on R...

[Christopher Jones]

> On 11 May 2017, at 5:56 pm, Carlo Tambuatco  wrote:
> 
> 
>> On May 11, 2017, at 12:52 PM, Christopher Jones  
>> wrote:
>> 
>> I would suggest the opposite instead. Remove your external R and just use 
>> the MacPorts version. Any reason not to do this ? In general MacPorts 
>> (rightly) ignores anything outside its ${prefix}.
> 
> 
> Well, the version of R under macports is a version or two behind the R 
> project version, so I was wondering if I could just tell macports to 
> recognize my version.

The version in MacPorts is already 3.4.0 Is this not the most recent release ?

https://www.r-project.org


> 
>> 
>> Chris
>> 
>>> On 6 May 2017, at 3:54 am, Carlo Tambuatco  wrote:
>>> 
>>> I have the R.app application installed from the R project which also 
>>> installs the R binary executable in my /usr/local/bin directory, so the 
>>> point is I have R installed but it is not under macports control.
>>> 
>>> Is there a way to tell macports that I have R installed externally and get 
>>> the py34-rpy2 port to use my installation instead of having to install the 
>>> R port via macports? And if so, have this change persist through port 
>>> upgrades…?
>>> 
>>> Thanks.
>>> ___
>>> macports-users mailing list
>>> macports-users@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>> 
> 



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

Re: py34-rpy2 port dependence on R...

[Christopher Jones]

> On 11 May 2017, at 5:56 pm, Carlo Tambuatco  wrote:
> 
> 
>> On May 11, 2017, at 12:52 PM, Christopher Jones  
>> wrote:
>> 
>> I would suggest the opposite instead. Remove your external R and just use 
>> the MacPorts version. Any reason not to do this ? In general MacPorts 
>> (rightly) ignores anything outside its ${prefix}.
> 
> 
> Well, the version of R under macports is a version or two behind the R 
> project version, so I was wondering if I could just tell macports to 
> recognize my version.

Then submit a pull request updating the version ;)

> 
>> 
>> Chris
>> 
>>> On 6 May 2017, at 3:54 am, Carlo Tambuatco  wrote:
>>> 
>>> I have the R.app application installed from the R project which also 
>>> installs the R binary executable in my /usr/local/bin directory, so the 
>>> point is I have R installed but it is not under macports control.
>>> 
>>> Is there a way to tell macports that I have R installed externally and get 
>>> the py34-rpy2 port to use my installation instead of having to install the 
>>> R port via macports? And if so, have this change persist through port 
>>> upgrades…?
>>> 
>>> Thanks.
>>> ___
>>> macports-users mailing list
>>> macports-users@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>> 
> 



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

Re: py34-rpy2 port dependence on R...

[Carlo Tambuatco]

> On May 11, 2017, at 12:52 PM, Christopher Jones  
> wrote:
> 
> I would suggest the opposite instead. Remove your external R and just use the 
> MacPorts version. Any reason not to do this ? In general MacPorts (rightly) 
> ignores anything outside its ${prefix}.


Well, the version of R under macports is a version or two behind the R project 
version, so I was wondering if I could just tell macports to recognize my 
version.

> 
> Chris
> 
>> On 6 May 2017, at 3:54 am, Carlo Tambuatco  wrote:
>> 
>> I have the R.app application installed from the R project which also 
>> installs the R binary executable in my /usr/local/bin directory, so the 
>> point is I have R installed but it is not under macports control.
>> 
>> Is there a way to tell macports that I have R installed externally and get 
>> the py34-rpy2 port to use my installation instead of having to install the R 
>> port via macports? And if so, have this change persist through port 
>> upgrades…?
>> 
>> Thanks.
>> ___
>> 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: py34-rpy2 port dependence on R...

[Christopher Jones]

I would suggest the opposite instead. Remove your external R and just use the 
MacPorts version. Any reason not to do this ? In general MacPorts (rightly) 
ignores anything outside its ${prefix}.

Chris

> On 6 May 2017, at 3:54 am, Carlo Tambuatco  wrote:
> 
> I have the R.app application installed from the R project which also installs 
> the R binary executable in my /usr/local/bin directory, so the point is I 
> have R installed but it is not under macports control.
> 
> Is there a way to tell macports that I have R installed externally and get 
> the py34-rpy2 port to use my installation instead of having to install the R 
> port via macports? And if so, have this change persist through port upgrades…?
> 
> Thanks.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users



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

Re: py34-rpy2 port dependence on R...

[Russell Jones]

Generally using MacPorts with anything in /usr/local will cause 
problems, so see if R will install to another location.


You may be able to use binpaths in macports.conf in the way one can with 
MacTeX, though this relies on ports having binary rather than port name 
dependencies. Let me know if you want more details.


Russell


On 06/05/17 03:54, Carlo Tambuatco wrote:

I have the R.app application installed from the R project which also installs 
the R binary executable in my /usr/local/bin directory, so the point is I have 
R installed but it is not under macports control.

Is there a way to tell macports that I have R installed externally and get the 
py34-rpy2 port to use my installation instead of having to install the R port 
via macports? And if so, have this change persist through port upgrades…?

Thanks.
___
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: Failure to build glib2 as part of xsane dependency

[Chris Jones]

You need to uninstall any ports built using 4.0, then uninstall 
clang-4.0 and llvm-4.0, then reinstall the ports you need using clang 3.9.


Chris

On 09/05/17 19:56, ges...@ftp83plus.net wrote:

Doesn't work.

The following ports will break:
 cctools @895_4
 ld64-latest @274.2_1

I selected "y" anyway, but as expected, got the same error message:

cctools: Variant llvm39 conflicts with llvm40

El 2017-05-09, a las 13:58, Ken Cunningham escribió:


sudo port uninstall clang-4.0 llvm-4.0 should do it for you.

don't forget to change the line in macports.conf about
default_compilers, removing clang-4.0.

BTW I appear to have fixed clang-4.0 for snow leopard, and depending
on what Jeremy wants to do with that, it should be working in macports
or upstream eventually.

Although I'd recommend you stick with clang-3.8 or clang-3.9 for now,
clang-4.0 for snow leopard will work soonishly. There's a word... :>

Best,

Ken



On 2017-05-09, at 10:53 AM, ges...@ftp83plus.net
 wrote:


Me again.

I forgot, but how do I uninstall the broken llvm40 version?
On Step 7, it complains about conflict between llvm39 and llvm 40.

Thanks

El 2017-05-05, a las 19:05, Ken Cunningham escribió:



On 2017-05-04, at 12:32 PM, ges...@ftp83plus.net
 wrote:


Hello there,

I needed to reinstall MacPorts on Snow Leopard, and followed the
instructions in LibcxxOnOlderSystems (I recall some ports wouldn't
compile properly without it), including the experimental steps.
Only there, I replaced clang 3.9 by clang 4.0.

However, it failed on completing xsane compilation, as glib2 failed:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/main.log

is pasted there:
https://pastebin.com/dmNJFQKU

From what I could read, it can't find a given header file. How did
it went missing?





As mentioned privately, it seems likely you've stumbled across this
bug  which Jeremy
reported a few months ago.

It looks like a new regression and I don't see that error on 10.6
with clang-3.7, clang-3.8, or clang-3.9, so if you back up in the
libcxxonoldersystems instructions and install clang-3.8 or clang-3.9
you should be OK.

I haven't tried clang-4.0 to confirm this bug / error on my system
yet, but I could assume I'd see it too if I did.

Best,

Ken










___
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: Failure to build glib2 as part of xsane dependency

[gestos]

Doesn't work. 

The following ports will break:
 cctools @895_4
 ld64-latest @274.2_1

I selected "y" anyway, but as expected, got the same error message:

cctools: Variant llvm39 conflicts with llvm40

El 2017-05-09, a las 13:58, Ken Cunningham escribió:

> sudo port uninstall clang-4.0 llvm-4.0 should do it for you.
> 
> don't forget to change the line in macports.conf about default_compilers, 
> removing clang-4.0.
> 
> BTW I appear to have fixed clang-4.0 for snow leopard, and depending on what 
> Jeremy wants to do with that, it should be working in macports or upstream 
> eventually.
> 
> Although I'd recommend you stick with clang-3.8 or clang-3.9 for now, 
> clang-4.0 for snow leopard will work soonishly. There's a word... :>
> 
> Best,
> 
> Ken
> 
> 
> 
> On 2017-05-09, at 10:53 AM, ges...@ftp83plus.net wrote:
> 
>> Me again. 
>> 
>> I forgot, but how do I uninstall the broken llvm40 version?
>> On Step 7, it complains about conflict between llvm39 and llvm 40.
>> 
>> Thanks
>> 
>> El 2017-05-05, a las 19:05, Ken Cunningham escribió:
>> 
>>> 
>>> On 2017-05-04, at 12:32 PM, ges...@ftp83plus.net wrote:
>>> 
> Hello there, 
> 
> I needed to reinstall MacPorts on Snow Leopard, and followed the 
> instructions in LibcxxOnOlderSystems (I recall some ports wouldn't 
> compile properly without it), including the experimental steps. Only 
> there, I replaced clang 3.9 by clang 4.0.
> 
> However, it failed on completing xsane compilation, as glib2 failed:
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/main.log
> 
> is pasted there:
> https://pastebin.com/dmNJFQKU
> 
> From what I could read, it can't find a given header file. How did it 
> went missing?
 
>>> 
>>> 
>>> As mentioned privately, it seems likely you've stumbled across this bug 
>>>  which Jeremy reported a few 
>>> months ago.
>>> 
>>> It looks like a new regression and I don't see that error on 10.6 with 
>>> clang-3.7, clang-3.8, or clang-3.9, so if you back up in the 
>>> libcxxonoldersystems instructions and install clang-3.8 or clang-3.9 you 
>>> should be OK.
>>> 
>>> I haven't tried clang-4.0 to confirm this bug / error on my system yet, but 
>>> I could assume I'd see it too if I did.
>>> 
>>> Best,
>>> 
>>> Ken
>>> 
>>> 
>> 
> 

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

Re: Failure to build glib2 as part of xsane dependency

[Ken Cunningham]

sudo port uninstall clang-4.0 llvm-4.0 should do it for you.

don't forget to change the line in macports.conf about default_compilers, 
removing clang-4.0.

BTW I appear to have fixed clang-4.0 for snow leopard, and depending on what 
Jeremy wants to do with that, it should be working in macports or upstream 
eventually.

Although I'd recommend you stick with clang-3.8 or clang-3.9 for now, clang-4.0 
for snow leopard will work soonishly. There's a word... :>

Best,

Ken



On 2017-05-09, at 10:53 AM, ges...@ftp83plus.net wrote:

> Me again. 
> 
> I forgot, but how do I uninstall the broken llvm40 version?
> On Step 7, it complains about conflict between llvm39 and llvm 40.
> 
> Thanks
> 
> El 2017-05-05, a las 19:05, Ken Cunningham escribió:
> 
>> 
>> On 2017-05-04, at 12:32 PM, ges...@ftp83plus.net wrote:
>> 
 Hello there, 
 
 I needed to reinstall MacPorts on Snow Leopard, and followed the 
 instructions in LibcxxOnOlderSystems (I recall some ports wouldn't compile 
 properly without it), including the experimental steps. Only there, I 
 replaced clang 3.9 by clang 4.0.
 
 However, it failed on completing xsane compilation, as glib2 failed:
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/main.log
 
 is pasted there:
 https://pastebin.com/dmNJFQKU
 
 From what I could read, it can't find a given header file. How did it went 
 missing?
>>> 
>> 
>> 
>> As mentioned privately, it seems likely you've stumbled across this bug 
>>  which Jeremy reported a few 
>> months ago.
>> 
>> It looks like a new regression and I don't see that error on 10.6 with 
>> clang-3.7, clang-3.8, or clang-3.9, so if you back up in the 
>> libcxxonoldersystems instructions and install clang-3.8 or clang-3.9 you 
>> should be OK.
>> 
>> I haven't tried clang-4.0 to confirm this bug / error on my system yet, but 
>> I could assume I'd see it too if I did.
>> 
>> Best,
>> 
>> Ken
>> 
>> 
> 

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

Re: Failure to build glib2 as part of xsane dependency

[gestos]

Me again. 

I forgot, but how do I uninstall the broken llvm40 version?
On Step 7, it complains about conflict between llvm39 and llvm 40.

Thanks

El 2017-05-05, a las 19:05, Ken Cunningham escribió:

> 
> On 2017-05-04, at 12:32 PM, ges...@ftp83plus.net wrote:
> 
>>> Hello there, 
>>> 
>>> I needed to reinstall MacPorts on Snow Leopard, and followed the 
>>> instructions in LibcxxOnOlderSystems (I recall some ports wouldn't compile 
>>> properly without it), including the experimental steps. Only there, I 
>>> replaced clang 3.9 by clang 4.0.
>>> 
>>> However, it failed on completing xsane compilation, as glib2 failed:
>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/main.log
>>> 
>>> is pasted there:
>>> https://pastebin.com/dmNJFQKU
>>> 
>>> From what I could read, it can't find a given header file. How did it went 
>>> missing?
>> 
> 
> 
> As mentioned privately, it seems likely you've stumbled across this bug 
>  which Jeremy reported a few 
> months ago.
> 
> It looks like a new regression and I don't see that error on 10.6 with 
> clang-3.7, clang-3.8, or clang-3.9, so if you back up in the 
> libcxxonoldersystems instructions and install clang-3.8 or clang-3.9 you 
> should be OK.
> 
> I haven't tried clang-4.0 to confirm this bug / error on my system yet, but I 
> could assume I'd see it too if I did.
> 
> Best,
> 
> Ken
> 
> 

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

Re: Feature request

[rmgls]

Hi,

Thanks for  your advice.
I will  set  a feature request on trac.


Rmgls
rm...@orange.fr 

> On 5 May 2017, at 23:06, Mojca Miklavec  wrote:
> 
> On 5 May 2017 at 22:04, rmgls wrote:
>> hi all,
>> 
>> installing a port compute all dependancies, and print:
>> installing ... do you want to continue Y/N?
>> 
>> its ok! but what would be useful is to print the required space for all 
>> packages:
> 
> Yes, it would be nice, but we don't always know how big they are as
> they are often compiled from source. In case of binary packages (or if
> the same kind of package was already compiled on the buildbot, only
> not distributed) we could do that, yes, but someone still needs to
> write the code to:
> - collect the data
> - show the data.
> 
> You may open a feature request on Trac (just don't expect too much as
> we are currently somewhat understaffed; if you really want that
> feature, asking for advice to help you get it done would give you
> higher chances :).
> 
> (I know we have a ticket for showing percentage of the build, but
> don't know where. This is somewhat related.)
> 
> Mojca

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

py34-rpy2 port dependence on R...

[Carlo Tambuatco]

I have the R.app application installed from the R project which also installs 
the R binary executable in my /usr/local/bin directory, so the point is I have 
R installed but it is not under macports control.

Is there a way to tell macports that I have R installed externally and get the 
py34-rpy2 port to use my installation instead of having to install the R port 
via macports? And if so, have this change persist through port upgrades…?

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

Re: Failure to build glib2 as part of xsane dependency

[Ken Cunningham]

On 2017-05-04, at 12:32 PM, ges...@ftp83plus.net wrote:

>> Hello there, 
>> 
>> I needed to reinstall MacPorts on Snow Leopard, and followed the 
>> instructions in LibcxxOnOlderSystems (I recall some ports wouldn't compile 
>> properly without it), including the experimental steps. Only there, I 
>> replaced clang 3.9 by clang 4.0.
>> 
>> However, it failed on completing xsane compilation, as glib2 failed:
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/main.log
>> 
>> is pasted there:
>> https://pastebin.com/dmNJFQKU
>> 
>> From what I could read, it can't find a given header file. How did it went 
>> missing?
> 


As mentioned privately, it seems likely you've stumbled across this bug 
 which Jeremy reported a few 
months ago.

It looks like a new regression and I don't see that error on 10.6 with 
clang-3.7, clang-3.8, or clang-3.9, so if you back up in the 
libcxxonoldersystems instructions and install clang-3.8 or clang-3.9 you should 
be OK.

I haven't tried clang-4.0 to confirm this bug / error on my system yet, but I 
could assume I'd see it too if I did.

Best,

Ken


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

Re: Feature request

[Mojca Miklavec]

On 5 May 2017 at 22:04, rmgls wrote:
> hi all,
>
> installing a port compute all dependancies, and print:
> installing ... do you want to continue Y/N?
>
> its ok! but what would be useful is to print the required space for all 
> packages:

Yes, it would be nice, but we don't always know how big they are as
they are often compiled from source. In case of binary packages (or if
the same kind of package was already compiled on the buildbot, only
not distributed) we could do that, yes, but someone still needs to
write the code to:
- collect the data
- show the data.

You may open a feature request on Trac (just don't expect too much as
we are currently somewhat understaffed; if you really want that
feature, asking for advice to help you get it done would give you
higher chances :).

(I know we have a ticket for showing percentage of the build, but
don't know where. This is somewhat related.)

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

Feature request

[rmgls]

hi all,

installing a port compute all dependancies, and print:
installing ... do you want to continue Y/N?

its ok! but what would be useful is to print the required space for all 
packages:
i.e. say latex or texlive ...  which are big packages.
it semms to be important in some situations:
laptops with small ssd for example.


am i wrong?
if i miss something, please let me know.

Thanks.

rmgls
rmgls@



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

Fwd: Failure to build glib2 as part of xsane dependency

[gestos]

> Hello there, 
> 
> I needed to reinstall MacPorts on Snow Leopard, and followed the instructions 
> in LibcxxOnOlderSystems (I recall some ports wouldn't compile properly 
> without it), including the experimental steps. Only there, I replaced clang 
> 3.9 by clang 4.0.
> 
> However, it failed on completing xsane compilation, as glib2 failed:
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_glib2/glib2/main.log
> 
> is pasted there:
> https://pastebin.com/dmNJFQKU
> 
> From what I could read, it can't find a given header file. How did it went 
> missing?

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

Re: Frescobaldi @2.20.0_1+app apparently broken

[Thomas Ruedas]

Hi Davide,
thanks for enlightening me about the $PATH settings. I have fixed that 
now and repeated the upgrade of Frescobaldi once more, and now it works 
(at least from the Terminal, but I'm sure the other one will also).

Best,
Thomas

Am 04.05.17 um 14:03 schrieb Davide Liessi:

2017-05-04 13:08 GMT+02:00 Thomas Ruedas :

PYTHONPATH=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/:$PYTHONPATH


the problem is the PYTHONPATH variable, which should not point to a
Python version different from the one you are using.
Also, if you are using the MacPorts-provided Python, there is no need
to set PYTHONPATH, so my recommendation is to simply delete that line.
After deleting that line (and opening a new Terminal) you should get a
working Python 3.5 (the error for 'import sip' was not the only one).


Macports seems to have amended my .profile on earlier occasions when I made
Python upgrades, and I have never touched them. Actually, the $PATH
modification appears three times there, because apparently it was never
checked whether it was already there.


MacPorts edits the .profile only when you update MacPorts itself, not
when you update single ports.
Also, it only adds /opt/local/bin in front of the PATH and doesn't set
PYTHONPATH.
Those lines in your .profile come from a different source.
If you want to use only MacPorts' Pythons I would get rid also of the
lines setting the PATH:

PATH="/Library/Frameworks/Python.framework/Versions/2.7/bin:${PATH}"
export PATH

and ensure instead that /opt/local/bin is the first path in PATH, as
MacPorts sets it.

Best wishes.
Davide



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

Re: Frescobaldi @2.20.0_1+app apparently broken

[Davide Liessi]

Dear Thomas,

2017-05-04 13:08 GMT+02:00 Thomas Ruedas :
> PYTHONPATH=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/:$PYTHONPATH

the problem is the PYTHONPATH variable, which should not point to a
Python version different from the one you are using.
Also, if you are using the MacPorts-provided Python, there is no need
to set PYTHONPATH, so my recommendation is to simply delete that line.
After deleting that line (and opening a new Terminal) you should get a
working Python 3.5 (the error for 'import sip' was not the only one).

> Macports seems to have amended my .profile on earlier occasions when I made
> Python upgrades, and I have never touched them. Actually, the $PATH
> modification appears three times there, because apparently it was never
> checked whether it was already there.

MacPorts edits the .profile only when you update MacPorts itself, not
when you update single ports.
Also, it only adds /opt/local/bin in front of the PATH and doesn't set
PYTHONPATH.
Those lines in your .profile come from a different source.
If you want to use only MacPorts' Pythons I would get rid also of the
lines setting the PATH:
> PATH="/Library/Frameworks/Python.framework/Versions/2.7/bin:${PATH}"
> export PATH
and ensure instead that /opt/local/bin is the first path in PATH, as
MacPorts sets it.

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

Re: Frescobaldi @2.20.0_1+app apparently broken

[Thomas Ruedas]

Hi Davide,
Am 04.05.17 um 10:09 schrieb Davide Liessi:

2017-05-04 1:39 GMT+02:00 Thomas Ruedas :
Your problem is really strange: Frescobaldi simply does 'import sip',
which should result in importing the Python 3.5 sip module, since you
are running Frescobaldi with Python 3.5; it should not even see the
Python2.7 module.

Please do the following in a Terminal and send the output:
/opt/local/bin/python3.5 -v
import sip
exit()
See below. If it shouldn't even see the 2.7 module, maybe it has to do 
with some entries in my .profile from some earlier installation:

# Setting PATH for Python 2.7
# The orginal version is saved in .profile.pysave
PATH="/Library/Frameworks/Python.framework/Versions/2.7/bin:${PATH}"
export PATH
export 
PYTHONPATH=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/:$PYTHONPATH


Macports seems to have amended my .profile on earlier occasions when I 
made Python upgrades, and I have never touched them. Actually, the $PATH 
modification appears three times there, because apparently it was never 
checked whether it was already there.

Best,
Thomas

> /opt/local/bin/python3.5 -v
import _frozen_importlib # frozen
import _imp # builtin
import sys # builtin
import '_warnings' # 
import '_thread' # 
import '_weakref' # 
import '_frozen_importlib_external' # '_frozen_importlib.FrozenImporter'>

import '_io' # 
import 'marshal' # 
import 'posix' # 
import _thread # previously loaded ('_thread')
import '_thread' # 
import _weakref # previously loaded ('_weakref')
import '_weakref' # 
# installing zipimport hook
import 'zipimport' # 
# installed zipimport hook
# 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/__pycache__/__init__.cpython-35.pyc 
matches 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/__init__.py
# code object from 
'/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/__pycache__/__init__.cpython-35.pyc'
# 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/__pycache__/codecs.cpython-35.pyc 
matches 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/codecs.py
# code object from 
'/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/__pycache__/codecs.cpython-35.pyc'

import '_codecs' # 
import 'codecs' # <_frozen_importlib_external.SourceFileLoader object at 
0x10c8cf518>
# 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/__pycache__/aliases.cpython-35.pyc 
matches 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/aliases.py
# code object from 
'/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/__pycache__/aliases.cpython-35.pyc'
import 'encodings.aliases' # 
<_frozen_importlib_external.SourceFileLoader object at 0x10c8ea128>
import 'encodings' # <_frozen_importlib_external.SourceFileLoader object 
at 0x10c8cf128>
# 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/__pycache__/utf_8.cpython-35.pyc 
matches 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/utf_8.py
# code object from 
'/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/__pycache__/utf_8.cpython-35.pyc'
import 'encodings.utf_8' # <_frozen_importlib_external.SourceFileLoader 
object at 0x10c8efeb8>

import '_signal' # 
# 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/__pycache__/latin_1.cpython-35.pyc 
matches 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/latin_1.py
# code object from 
'/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/encodings/__pycache__/latin_1.cpython-35.pyc'
import 'encodings.latin_1' # 
<_frozen_importlib_external.SourceFileLoader object at 0x10c8f3978>
# 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/__pycache__/io.cpython-35.pyc 
matches 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/io.py
# code object from 
'/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/__pycache__/io.cpython-35.pyc'
# 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/__pycache__/abc.cpython-35.pyc 
matches 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/abc.py
# code object from 
'/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/__pycache__/abc.cpython-35.pyc'
# 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/__pycache__/_weakrefset.cpython-35.pyc 
matches 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/_weakrefset.py
# code object from 
'/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/__pycache__/_weakrefset.cpython-35.pyc'
import '_weakrefset' # 

Re: Frescobaldi @2.20.0_1+app apparently broken

[Davide Liessi]

Hi.

2017-05-03 0:08 GMT+02:00 Thomas Ruedas :
> Traceback (most recent call last):
>   File "/opt/local/bin/frescobaldi", line 7, in 
> import main
>   File
> "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/frescobaldi_app/main.py",
> line 26, in 
> import sip
> ImportError:
> dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/sip.so,
> 2): Symbol not found: _PyCObject_Type
>   Referenced from:
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/sip.so
>   Expected in: flat namespace
>  in
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/sip.so

I don't understand why the Python 3.5 Frescobaldi tries to load the
Python 2.7 sip...

Did you run Frescobaldi via the application bundle in
/Applications/MacPorts or from the Terminal?
In the latter case what did you write exactly?

Please try again
sudo port clean frescobaldi py35-poppler-qt4 py35-pyqt4
sudo port install frescobaldi
and let me know if you still have this problem.

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

Frescobaldi @2.20.0_1+app apparently broken

[Thomas Ruedas]

Hi,
I made an upgrade of my ports recently, and today I tried to open 
frescobaldi, but it crashed with this error:

Traceback (most recent call last):
  File "/opt/local/bin/frescobaldi", line 7, in 
import main
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/frescobaldi_app/main.py", 
line 26, in 

import sip
ImportError: 
dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/sip.so, 
2): Symbol not found: _PyCObject_Type
  Referenced from: 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/sip.so

  Expected in: flat namespace
 in 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/sip.so


My Mac has the latest Macports release and is running on OS X 10.10.5, 
and the upgrade I made seemed to be fine and showed no errors. Can 
anybody confirm whether the port is broken?
Fortunately, I had a deactivated frescobaldi @2.18.1_0+app still 
installed, which I could activate after uninstalling the broken version, 
and that older version works.

Any ideas what could be wrong?
Thomas
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Do I need +universal to be used when installing ports?

[Dominik Reichardt]

And Dosbox.

> Am 30.04.2017 um 00:50 schrieb Ken Cunningham 
> :
> 
> WINE is the only thing that comes to mind that really only runs i386 even on 
> x86_64. 
> 
> And that triggers all it’s deps to be i386 as well.
> 
> K
> 
> 
>> On Apr 28, 2017, at 8:06 AM, Barrie Stott  wrote:
>> 
>> I have an iMac as my only computer and am near the beginning of installing 
>> ports for Sierra so it’s a good time to change from +universal way of 
>> working to -universal; it should save space and installations should be 
>> quicker. Does anyone know any good reasons why I should not go ahead? Are 
>> there situations where x86_64 cannot be used and i386 is necessary? Once I 
>> know which way to jump I can set some defaults and thereafter I suspect that 
>> installation would be the same.
>> 
>> Barrie.
>> ___
>> 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
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Do I need +universal to be used when installing ports?

[Ken Cunningham]

WINE is the only thing that comes to mind that really only runs i386 even on 
x86_64. 

And that triggers all it’s deps to be i386 as well.

K


> On Apr 28, 2017, at 8:06 AM, Barrie Stott  wrote:
> 
> I have an iMac as my only computer and am near the beginning of installing 
> ports for Sierra so it’s a good time to change from +universal way of working 
> to -universal; it should save space and installations should be quicker. Does 
> anyone know any good reasons why I should not go ahead? Are there situations 
> where x86_64 cannot be used and i386 is necessary? Once I know which way to 
> jump I can set some defaults and thereafter I suspect that installation would 
> be the same.
> 
> Barrie.
> ___
> 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

Do I need +universal to be used when installing ports?

[Barrie Stott]

I have an iMac as my only computer and am near the beginning of installing 
ports for Sierra so it’s a good time to change from +universal way of working 
to -universal; it should save space and installations should be quicker. Does 
anyone know any good reasons why I should not go ahead? Are there situations 
where x86_64 cannot be used and i386 is necessary? Once I know which way to 
jump I can set some defaults and thereafter I suspect that installation would 
be the same.

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

Re: Upgrading python from 27 to 36

[Russell Jones]

On which interpreter is used, you can control this with (IIRC) something 
like


port select --set python3 python3.6

port select --set python2 python2.7

port select --set python python2

# or "port select --set python python3" if you like

It's most flexible to say #!/usr/bin/env python2 or #!/usr/bin/env 
python3 in scripts (rather than, say, #!/opt/local/bin/python or 
#!/usr/bin/env python), as this ensures the right major version, and 
will use an enabled virtualenv's copy of the interpreter. 
#!/opt/local/bin/python3 would work too.


Don't forget there's also /usr/bin/python and /usr/bin/python2.7. These 
are best avoided.


The Apple-provided build of Python is installed in 
/System/Library/Frameworks/Python.framework and /usr/bin/python, 
respectively. You should never modify or delete these, as they are 
Apple-controlled and are used by Apple- or third-party software. 
Remember that if you choose to install a newer Python version from 
python.org, you will have two different but functional Python 
installations on your computer, so it will be important that your 
paths and usages are consistent with what you want to do.

https://docs.python.org/2/using/mac.html

Russell

On 27/04/17 14:38, Russell Jones wrote:
In short, most stuff works with 2 and 3, and you should use 3. You can 
install both, they're independent. virtualenvs are your friend. Also, 
"import this" if you haven't already :)


In full, it's quite complex. See 
https://wiki.python.org/moin/Python2orPython3


For most features and least hassle, use 3 and ignore 2 if you can. If 
you have old 2 code of your own, have a look at http://python-future.org/


Stuff being 2 only is a bit of a red flag. It's likely unmaintained or 
has architectural or testing problems such that it can't be ported. 
Some newer stuff is 3 only-- typically to rely on new 3 only features 
like asyncio. 2 and 3 stuff is so because of some effort by the 
developers to make it so.


Russell

On 26/04/17 20:59, Michael wrote:

What is involved in switching from python 27 to python 36?

I've been using python 27 for a while. I've run into a problem with 
youtube-dl needing a newer python.


But I don't know what I need to do to safely update. It's not like 
python2 is a different program than python3 (same "python" in both 
cases), and as I understand it, not everything written for P2 is 
compatible with P3.


So what's the proper way to upgrade?
Or is there a way to have both installed at the same time? (but then 
... !#/usr/bin/env python ...)


---
Entertaining minecraft videos
http://YouTube.com/keybounce

___
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


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

Re: Upgrading python from 27 to 36

[Russell Jones]

In short, most stuff works with 2 and 3, and you should use 3. You can 
install both, they're independent. virtualenvs are your friend. Also, 
"import this" if you haven't already :)


In full, it's quite complex. See 
https://wiki.python.org/moin/Python2orPython3


For most features and least hassle, use 3 and ignore 2 if you can. If 
you have old 2 code of your own, have a look at http://python-future.org/


Stuff being 2 only is a bit of a red flag. It's likely unmaintained or 
has architectural or testing problems such that it can't be ported. Some 
newer stuff is 3 only-- typically to rely on new 3 only features like 
asyncio. 2 and 3 stuff is so because of some effort by the developers to 
make it so.


Russell

On 26/04/17 20:59, Michael wrote:

What is involved in switching from python 27 to python 36?

I've been using python 27 for a while. I've run into a problem with youtube-dl 
needing a newer python.

But I don't know what I need to do to safely update. It's not like python2 is a different 
program than python3 (same "python" in both cases), and as I understand it, not 
everything written for P2 is compatible with P3.

So what's the proper way to upgrade?
Or is there a way to have both installed at the same time? (but then ... 
!#/usr/bin/env python ...)

---
Entertaining minecraft videos
http://YouTube.com/keybounce

___
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

Upgrading python from 27 to 36

[Michael]

What is involved in switching from python 27 to python 36?

I've been using python 27 for a while. I've run into a problem with youtube-dl 
needing a newer python.

But I don't know what I need to do to safely update. It's not like python2 is a 
different program than python3 (same "python" in both cases), and as I 
understand it, not everything written for P2 is compatible with P3.

So what's the proper way to upgrade?
Or is there a way to have both installed at the same time? (but then ... 
!#/usr/bin/env python ...)

---
Entertaining minecraft videos
http://YouTube.com/keybounce

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

A couple of queries about Xcode

[Barrie Stott]

I recently moved from El Capitan to Sierra and failed miserably when trying to 
upgrade MacPorts. I am now trying to get MacPorts going again from scratch 
rather than upgrading and had occasion to use port diagnose. Here’s what was 
displayed on the screen:

sudo port diagnose
Password:
Error: currently installed version of Xcode, 8.3.2, is not supported by 
MacPorts.  For your currently installed system, only the following versions of 
Xcode are supported:  8.3.1 8.3 8.2.1 8.2 8.1 8.0

The file guide.macports.org says in a Note in Section 2.1:

Always make sure to install the latest available version of Xcode for your OS X 
release; using outdated versions of Xcode may cause port install failures.

Which is right?

Also is it safe to assume that installing a new Xcode gets rid of any older one 
or does something extra need to be done?

Help with these queries would be much appreciated.

Barrie.
___
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)

[Joshua Root]

Bachsau wrote:

Am 02.11.2016 um 23:48 schrieb Murray Eisenberg:

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.


Against the recommendations in that article, I discovered the easiest
way to migrate is to reinstall MacPorts base and just do a port
selfupdate && port upgrade outdated. Chances to run into problems are
minimal and much lower than going the recomended way.


The best thing that can be said for that approach is that it may well 
work. It doesn't always, and it wouldn't have solved the OP's problem.


Trust me, if we could safely tell people to just run 'port upgrade 
outdated', we would. But experience over many years of OS updates has 
resulted in the recommended Migration procedure. We couldn't make this 
stuff up if we tried; real users ran into real, often confusing, 
problems. So I have to disagree with your statement that the recommended 
way has a higher chance of running into problems.


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

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

[Dave Horsfall]

On Fri, 4 Nov 2016, Dominik Reichardt wrote:

> For what it’s worth, as an admin of other projects and reporter of bugs 
> *I* do appreciate notifications of all those changes. When I report or 
> CC: me to a bug I want to know what happens to the report and attached 
> files.



Me too :-)



Seriously, I too want to be notified whenever the rug is about to pulled 
out from underneath me, and my utmost thanks go to the Macports bods for 
doing what must be a thankless job.

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."___
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)

[Bachsau]

Am 02.11.2016 um 23:48 schrieb Murray Eisenberg:

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.


Against the recommendations in that article, I discovered the easiest 
way to migrate is to reinstall MacPorts base and just do a port 
selfupdate && port upgrade outdated. Chances to run into problems are 
minimal and much lower than going the recomended way.

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

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

[Ralph Seichter]

On 04.11.2016 09:43, René J. V. Bertin wrote:

> Filtering these notifications means filtering on email content, and
> with the number of MUA's I'm using that'd have to be done on the server.

Which is why I suggested Sieve as the first option. Works fine for me. I
use Sieve "fileinto" to sort incoming mail into folders to avoid clutter,
and for some messages I use "addflag" to mark them as seen on arrival.
This way, I have them available for reference, but they don't grab more
attention than necessary.

> There's clearly even less of a community spirit here than I thought,
> so I'll just find alternative ways to make to with the tools at hand
> when I cannot get around using them.

And by "community spirit" you mean people agreeing with you on your
personal preferences? That's not it.

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

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

[Dominik Reichardt]

> 
> 
> I'm going to be dropping this. There's clearly even less of a community 
> spirit 
> here than I thought, so I'll just find alternative ways to make to with the 
> tools 
> at hand when I cannot get around using them.
> 

For what it’s worth, as an admin of other projects and reporter of bugs *I* do 
appreciate notifications of all those changes. When I report or CC: me to a bug 
I want to know what happens to the report and attached files.

I don’t quite see why you needed to add a snide remark about the MacPorts 
community spirit. What is your problem? Not enough people caring about this 
presumed problem or that the few people who responded don’t see it as a problem?
I don’t know where that entitlement attitude comes from and how one can get so 
worked up over this.

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

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

[René J . V . Bertin]

Ralph Seichter wrote:

> Have you tried using Sieve or your MUA's filter options to get rid of
> e-mails you personally don't consider of interest? Notifications are a

No, as I said I'd rather not. Filtering these notifications means filtering on 
email content, and with the number of MUA's I'm using that'd have to be done on 
the server.

Notifications stop being a boon if you're getting so many of them that are 
pointless that you start deleting them as soon as they start coming in.

I'm going to be dropping this. There's clearly even less of a community spirit 
here than I thought, so I'll just find alternative ways to make to with the 
tools 
at hand when I cannot get around using them.

___
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 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: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

[Murray Eisenberg]

Problem with re-installing my ports after migration from El Capitan to Sierra 
is SOLVED — at least with respect to installing gmp (upon which quite a few 
other ports depend)!

That ‘__SWIFT_UNAVAILABLE_MSG” error, which ultimately points back to 
Availability.h was the clue indeed: As a workaround some time ago for the bug 
discussed in ticket #48471, I had edited a local copy of Availability.h and put 
it into /opt/local/include.

Simply removing that local copy from /opt/local/include now allows installation 
of gmp to proceed to completion. And more.



> On Nov 2, 2016, at 11:17 PM, Ken Cunningham  
> wrote:
> 
> Murray, I note the error in your log looks somewhat like this error in trac:
> 
>  >
> 
> __SWIFT_UNAVAILABLE_MSG
> …
> 
> Ken

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334


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

Re: GitHub migration complete

[Michael]

On 2016-11-03, at 4:44 AM, René J.V. Bertin  wrote:

> On Thursday November 03 2016 11:35:43 Clemens Lang wrote:
> 
>> It's something we all have to deal with. Presumably, we will all learn over 
>> time.
> 
> Presumably. Question is, who has to learn what, and how reasonable is it to 
> require that of them when the general consensus usually is that "users 
> shouldn't have to ".
> 
>> Feel free to ask on the -dev list, that's what it's for.
> 
> Well, sure. At least I cannot f*** anything up permanently since I don't have 
> commit access, and I'm not so sure how inclined I still am to try to get that 
> after the move to git (a matter of trust in myself).

You can also subscribe to the git users mailing list, as there are plenty of 
people who will answer "how do I do X" questions there.

git-us...@googlegroups.com

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

---
Entertaining minecraft videos
http://YouTube.com/keybounce

___
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)

[Ken Cunningham]

>> 
>> If so, the workaround for that was to make a local copy of Availability.h in 
>> /opt/local/include and edit it there.
>> 

I'd still reinstall Xcode and the command line tools -- but you don't have a 
rogue Availability.h sitting  /opt/local/include do you? If so, that's your 
trouble.

K

___
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)

[Murray Eisenberg]

Looking more carefull, I see that the problematic "if defined(__has_feature)”  
in Availability discussed in ticket #48471 is different from the same phrase in 
the current Availability.h.  Namely, the new one has the whole new section, 
shown below, headed with “/* for use marking APIs unavailable for swift */“. 


> On Nov 3, 2016, at 10:43 AM, Murray Eisenberg  
> wrote:
> 
> OK, and in 
> 
>   
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/Availability.h
> 
> I find at lines 341-355:
> 
> /* for use marking APIs unavailable for swift */
> #if defined(__has_feature)
>   #if __has_feature(attribute_availability_swift)
> #define __SWIFT_UNAVAILABLE   
> __OS_AVAILABILITY(swift,unavailable)
> #define __SWIFT_UNAVAILABLE_MSG(_msg) 
> __OS_AVAILABILITY_MSG(swift,unavailable,_msg)
>   #endif
> #endif
> 
> #ifndef __SWIFT_UNAVAILABLE
>   #define __SWIFT_UNAVAILABLE
> #endif
> 
> #ifndef __SWIFT_UNAVAILABLE_MSG
>   #define __SWIFT_UNAVAILABLE_MSG(_msg)
> #endif
> 
> 
> Is there once again a problem in Availability.h with 'defined(__has_feature)’ 
>  which should really be 'defined(__has_feature)’ 
> again, as discussed in ticket #48471?
> 
> If so, the workaround for that was to make a local copy of Availability.h in 
> /opt/local/include and edit it there.
> 
> 
>> On Nov 3, 2016, at 10:29 AM, Ken Cunningham > > wrote:
>> 
>> Look at this ticket > > comment 3
>> 
>> pthreads is not picking up the definition from Availability.h for some 
>> reason.
>> 
>> Ken
>> 
>> 
>> On 2016-11-03, at 7:26 AM, Murray Eisenberg wrote:
>> 
>>> I looked at the tickets #46589, 51971, and 52326 about gmp, and I don’t see 
>>> mention of availability.h there.  
>>> 
>>> I thought the issue with availability.h concerned gcc48 and was resolved 
>>> somehow (with newer Xcode? with patched port?) some time ago.
>>> 
>>> The logs seem to indicate that the current issue with gmp involves 
>>> pthread.h.
>>> 
>>> 
 On Nov 3, 2016, at 10:10 AM, Ken Cunningham 
 > 
 wrote:
 
 Murray, that is very specific now
 
 I have that port installed.
 
 $ port -v installed gmp
 The following ports are currently installed:
 gmp @6.1.1_0 (active) platform='darwin 16' archs='x86_64'
 
 I just rebuilt it right now from source without trouble.
 
 so it's something on your machine. Jerermy points to a possibly corrupt 
 Availability.h file in the trac ticket.
 
 So you might look at that file, or just reinstall Xcode and the command 
 line tools.
 
 (Why is this not coming to you as a prebuilt binary from the buldbots, I 
 wonder?)
 
 
 Best,
 
 Ken
 
 
 
 
 On 2016-11-03, at 7:01 AM, Murray Eisenberg wrote:
 
> After the re-install script (from the migration instructions) got into an 
> infinite loop, I started to reinstall ports manually, starting with the 
> first one on my “myports.txt” list: analitza 
> 
> The failure came when installing that failed during the automatic 
> installation of dependencies, in that case gmp.
> 
> Today, looking at the dependencies for gmp, I see that all build and 
> library dependencies for that are already installed _except_ kdelibs.
> 
> So I tried reinstalling kdelibs, and that in turn choked at trying to 
> install its dependency gmp.
> 
> So everything pretty much comes down to failure to configure gmp. 
> 
> Configuring gmp (specifically, @6.1.1_0) fails with what appears in 
> main.log as:
> 
>  :info:configure configure: error: C++ compiler not available, see 
> config.log for details
> 
> In turn, config.log reports:
> 
>  /usr/include/pthread.h:423:1: error: C++ requires a type specifier for 
> all declarations
> __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead”)
> 
> And that seems to reduce to the issue of the problem with 
> /usr/include/pthread.h, namely:
> 
>  /usr/include/pthread.h:423:1: error: C++ requires a type specifier for 
> all declarations
> __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
> ^
> /usr/include/pthread.h:423:66: error: expected ';' after top level 
> declarator
> __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
>  ^
> 2 errors generated.
> configure:10556: $? = 1
> failed program was:
> /* This test rejects g++ 2.7.2 which doesn't have , only a
> pre-standard iostream.h. */
> #include 
> 
> I just was about to 

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

[Ken Cunningham]

Hi Murray,

Just to tell you I have not touched a thing on this Sierra install, and it 
works fine for me.


(Did you have a beta installed? Can you think of any reason why your SDK might 
not be stock?)

It takes 5 minutes to reinstall Xcode and the command line tools. That would be 
step 1 for me, but it's up to you.

Ken




On 2016-11-03, at 7:43 AM, Murray Eisenberg wrote:

> OK, and in 
> 
>   
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/Availability.h
> 
> I find at lines 341-355:
> 
> /* for use marking APIs unavailable for swift */
> #if defined(__has_feature)
>   #if __has_feature(attribute_availability_swift)
> #define __SWIFT_UNAVAILABLE   
> __OS_AVAILABILITY(swift,unavailable)
> #define __SWIFT_UNAVAILABLE_MSG(_msg) 
> __OS_AVAILABILITY_MSG(swift,unavailable,_msg)
>   #endif
> #endif
> 
> #ifndef __SWIFT_UNAVAILABLE
>   #define __SWIFT_UNAVAILABLE
> #endif
> 
> #ifndef __SWIFT_UNAVAILABLE_MSG
>   #define __SWIFT_UNAVAILABLE_MSG(_msg)
> #endif
> 
> 
> Is there once again a problem in Availability.h with 'defined(__has_feature)’ 
>  which should really be 'defined(__has_feature)’ 
> again, as discussed in ticket #48471?
> 
> If so, the workaround for that was to make a local copy of Availability.h in 
> /opt/local/include and edit it there.
> 
> 
>> On Nov 3, 2016, at 10:29 AM, Ken Cunningham 
>>  wrote:
>> 
>> Look at this ticket  comment 3
>> 
>> pthreads is not picking up the definition from Availability.h for some 
>> reason.
>> 
>> Ken
>> 
>> 
>> On 2016-11-03, at 7:26 AM, Murray Eisenberg wrote:
>> 
>>> I looked at the tickets #46589, 51971, and 52326 about gmp, and I don’t see 
>>> mention of availability.h there.  
>>> 
>>> I thought the issue with availability.h concerned gcc48 and was resolved 
>>> somehow (with newer Xcode? with patched port?) some time ago.
>>> 
>>> The logs seem to indicate that the current issue with gmp involves 
>>> pthread.h.
>>> 
>>> 
 On Nov 3, 2016, at 10:10 AM, Ken Cunningham 
  wrote:
 
 Murray, that is very specific now
 
 I have that port installed.
 
 $ port -v installed gmp
 The following ports are currently installed:
 gmp @6.1.1_0 (active) platform='darwin 16' archs='x86_64'
 
 I just rebuilt it right now from source without trouble.
 
 so it's something on your machine. Jerermy points to a possibly corrupt 
 Availability.h file in the trac ticket.
 
 So you might look at that file, or just reinstall Xcode and the command 
 line tools.
 
 (Why is this not coming to you as a prebuilt binary from the buldbots, I 
 wonder?)
 
 
 Best,
 
 Ken
 
 
 
 
 On 2016-11-03, at 7:01 AM, Murray Eisenberg wrote:
 
> After the re-install script (from the migration instructions) got into an 
> infinite loop, I started to reinstall ports manually, starting with the 
> first one on my “myports.txt” list: analitza 
> 
> The failure came when installing that failed during the automatic 
> installation of dependencies, in that case gmp.
> 
> Today, looking at the dependencies for gmp, I see that all build and 
> library dependencies for that are already installed _except_ kdelibs.
> 
> So I tried reinstalling kdelibs, and that in turn choked at trying to 
> install its dependency gmp.
> 
> So everything pretty much comes down to failure to configure gmp. 
> 
> Configuring gmp (specifically, @6.1.1_0) fails with what appears in 
> main.log as:
> 
>  :info:configure configure: error: C++ compiler not available, see 
> config.log for details
> 
> In turn, config.log reports:
> 
>  /usr/include/pthread.h:423:1: error: C++ requires a type specifier for 
> all declarations
> __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead”)
> 
> And that seems to reduce to the issue of the problem with 
> /usr/include/pthread.h, namely:
> 
>  /usr/include/pthread.h:423:1: error: C++ requires a type specifier for 
> all declarations
> __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
> ^
> /usr/include/pthread.h:423:66: error: expected ';' after top level 
> declarator
> __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
>  ^
> 2 errors generated.
> configure:10556: $? = 1
> failed program was:
> /* This test rejects g++ 2.7.2 which doesn't have , only a
> pre-standard iostream.h. */
> #include 
> 
> I just was about to try to do that  
>> On Nov 2, 2016, at 11:46 PM, Ken Cunningham 
>>  wrote:
>> 
>> can you remind me the name 

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

[Ken Cunningham]

Look at this ticket  comment 3

pthreads is not picking up the definition from Availability.h for some reason.

Ken


On 2016-11-03, at 7:26 AM, Murray Eisenberg wrote:

> I looked at the tickets #46589, 51971, and 52326 about gmp, and I don’t see 
> mention of availability.h there.  
> 
> I thought the issue with availability.h concerned gcc48 and was resolved 
> somehow (with newer Xcode? with patched port?) some time ago.
> 
> The logs seem to indicate that the current issue with gmp involves pthread.h.
> 
> 
>> On Nov 3, 2016, at 10:10 AM, Ken Cunningham 
>>  wrote:
>> 
>> Murray, that is very specific now
>> 
>> I have that port installed.
>> 
>> $ port -v installed gmp
>> The following ports are currently installed:
>> gmp @6.1.1_0 (active) platform='darwin 16' archs='x86_64'
>> 
>> I just rebuilt it right now from source without trouble.
>> 
>> so it's something on your machine. Jerermy points to a possibly corrupt 
>> Availability.h file in the trac ticket.
>> 
>> So you might look at that file, or just reinstall Xcode and the command line 
>> tools.
>> 
>> (Why is this not coming to you as a prebuilt binary from the buldbots, I 
>> wonder?)
>> 
>> 
>> Best,
>> 
>> Ken
>> 
>> 
>> 
>> 
>> On 2016-11-03, at 7:01 AM, Murray Eisenberg wrote:
>> 
>>> After the re-install script (from the migration instructions) got into an 
>>> infinite loop, I started to reinstall ports manually, starting with the 
>>> first one on my “myports.txt” list: analitza 
>>> 
>>> The failure came when installing that failed during the automatic 
>>> installation of dependencies, in that case gmp.
>>> 
>>> Today, looking at the dependencies for gmp, I see that all build and 
>>> library dependencies for that are already installed _except_ kdelibs.
>>> 
>>> So I tried reinstalling kdelibs, and that in turn choked at trying to 
>>> install its dependency gmp.
>>> 
>>> So everything pretty much comes down to failure to configure gmp. 
>>> 
>>> Configuring gmp (specifically, @6.1.1_0) fails with what appears in 
>>> main.log as:
>>> 
>>>   :info:configure configure: error: C++ compiler not available, see 
>>> config.log for details
>>> 
>>> In turn, config.log reports:
>>> 
>>>   /usr/include/pthread.h:423:1: error: C++ requires a type specifier for 
>>> all declarations
>>> __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead”)
>>> 
>>> And that seems to reduce to the issue of the problem with 
>>> /usr/include/pthread.h, namely:
>>> 
>>>   /usr/include/pthread.h:423:1: error: C++ requires a type specifier for 
>>> all declarations
>>>  __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
>>>  ^
>>>  /usr/include/pthread.h:423:66: error: expected ';' after top level 
>>> declarator
>>>  __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
>>>   ^
>>>  2 errors generated.
>>>  configure:10556: $? = 1
>>>  failed program was:
>>>  /* This test rejects g++ 2.7.2 which doesn't have , only a
>>>  pre-standard iostream.h. */
>>>  #include 
>>> 
>>> I just was about to try to do that  
 On Nov 2, 2016, at 11:46 PM, Ken Cunningham 
  wrote:
 
 can you remind me the name of a port that triggers the error so I can test 
 it (hopefully not clang-3.8 which would take all night to build ) ;>
 
 K
>>> 
>>> ---
>>> Murray Eisenbergmurrayeisenb...@gmail.com
>>> 503 King Farm Blvd #101 Home (240)-246-7240
>>> Rockville, MD 20850-6667Mobile (413)-427-5334
>>> 
>>> 
>> 
> 
> ---
> Murray Eisenberg  murrayeisenb...@gmail.com
> 503 King Farm Blvd #101   Home (240)-246-7240
> Rockville, MD 20850-6667  Mobile (413)-427-5334
> 
> 

___
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)

[Ken Cunningham]

Murray, that is very specific now

I have that port installed.

$ port -v installed gmp
The following ports are currently installed:
  gmp @6.1.1_0 (active) platform='darwin 16' archs='x86_64'

I just rebuilt it right now from source without trouble.

so it's something on your machine. Jerermy points to a possibly corrupt 
Availability.h file in the trac ticket.

So you might look at that file, or just reinstall Xcode and the command line 
tools.

(Why is this not coming to you as a prebuilt binary from the buldbots, I 
wonder?)


Best,

Ken




On 2016-11-03, at 7:01 AM, Murray Eisenberg wrote:

> After the re-install script (from the migration instructions) got into an 
> infinite loop, I started to reinstall ports manually, starting with the first 
> one on my “myports.txt” list: analitza 
> 
> The failure came when installing that failed during the automatic 
> installation of dependencies, in that case gmp.
> 
> Today, looking at the dependencies for gmp, I see that all build and library 
> dependencies for that are already installed _except_ kdelibs.
> 
> So I tried reinstalling kdelibs, and that in turn choked at trying to install 
> its dependency gmp.
> 
> So everything pretty much comes down to failure to configure gmp. 
> 
> Configuring gmp (specifically, @6.1.1_0) fails with what appears in main.log 
> as:
> 
> :info:configure configure: error: C++ compiler not available, see 
> config.log for details
> 
> In turn, config.log reports:
> 
> /usr/include/pthread.h:423:1: error: C++ requires a type specifier for 
> all declarations
>   __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead”)
> 
> And that seems to reduce to the issue of the problem with 
> /usr/include/pthread.h, namely:
> 
> /usr/include/pthread.h:423:1: error: C++ requires a type specifier for 
> all declarations
>__SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
>^
>/usr/include/pthread.h:423:66: error: expected ';' after top level 
> declarator
>__SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
> ^
>2 errors generated.
>configure:10556: $? = 1
>failed program was:
>/* This test rejects g++ 2.7.2 which doesn't have , only a
>pre-standard iostream.h. */
>#include 
> 
> I just was about to try to do that  
>> On Nov 2, 2016, at 11:46 PM, Ken Cunningham 
>>  wrote:
>> 
>> can you remind me the name of a port that triggers the error so I can test 
>> it (hopefully not clang-3.8 which would take all night to build ) ;>
>> 
>> K
> 
> ---
> Murray Eisenberg  murrayeisenb...@gmail.com
> 503 King Farm Blvd #101   Home (240)-246-7240
> Rockville, MD 20850-6667  Mobile (413)-427-5334
> 
> 

___
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)

[Murray Eisenberg]

After the re-install script (from the migration instructions) got into an 
infinite loop, I started to reinstall ports manually, starting with the first 
one on my “myports.txt” list: analitza 

The failure came when installing that failed during the automatic installation 
of dependencies, in that case gmp.

Today, looking at the dependencies for gmp, I see that all build and library 
dependencies for that are already installed _except_ kdelibs.

So I tried reinstalling kdelibs, and that in turn choked at trying to install 
its dependency gmp.

So everything pretty much comes down to failure to configure gmp. 

Configuring gmp (specifically, @6.1.1_0) fails with what appears in main.log as:

 :info:configure configure: error: C++ compiler not available, see 
config.log for details

In turn, config.log reports:

 /usr/include/pthread.h:423:1: error: C++ requires a type specifier for all 
declarations
   __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead”)

And that seems to reduce to the issue of the problem with 
/usr/include/pthread.h, namely:

 /usr/include/pthread.h:423:1: error: C++ requires a type specifier for all 
declarations
__SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
^
/usr/include/pthread.h:423:66: error: expected ';' after top level 
declarator
__SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
 ^
2 errors generated.
configure:10556: $? = 1
failed program was:
/* This test rejects g++ 2.7.2 which doesn't have , only a
pre-standard iostream.h. */
#include 

I just was about to try to do that  
> On Nov 2, 2016, at 11:46 PM, Ken Cunningham  
> wrote:
> 
> can you remind me the name of a port that triggers the error so I can test it 
> (hopefully not clang-3.8 which would take all night to build ) ;>
> 
> K

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334


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

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

[René J . V . Bertin]

On Thursday November 03 2016 12:46:18 Rainer Müller wrote:

> By now I received more mails from you with complaints about this than
> actual "duplicate" Trac notifications for attachment replacements...

You're welcome to filter out my emails, but you certainly won't receive any 
notifications about attachment replacements coming from me anymore.

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

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

[Rainer Müller]

On 2016-11-03 09:30, René J.V. Bertin wrote:
> Trac never sent notifications when you added or deleted (replaced) an
> attachment, but a recent introduced that as a new feature. I find
> this mostly useless and even annoying because when you update
> (replace, delete) an attachment there will be 2 emails. For active
> tickets I spend too much time weeding through and deleting emails
> devoid of interest.

By now I received more mails from you with complaints about this than
actual "duplicate" Trac notifications for attachment replacements...

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

Re: GitHub migration complete

[René J . V . Bertin]

On Thursday November 03 2016 11:35:43 Clemens Lang wrote:

> It's something we all have to deal with. Presumably, we will all learn over 
> time.

Presumably. Question is, who has to learn what, and how reasonable is it to 
require that of them when the general consensus usually is that "users 
shouldn't have to ".

> Feel free to ask on the -dev list, that's what it's for.

Well, sure. At least I cannot f*** anything up permanently since I don't have 
commit access, and I'm not so sure how inclined I still am to try to get that 
after the move to git (a matter of trust in myself).

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

Re: GitHub migration complete

[Clemens Lang]

Hi,

- On 3 Nov, 2016, at 10:57, René J.V. Bertin rjvber...@gmail.com wrote:

> last time I checked, github's issue tracker wasn't available for the ports 
> repo.
> I presume that's on purpose, but why? Even if "we already have a bug tracker",
> why would it make life harder and not easier at least for some things?

Because people are supposed to use Trac. We do not want multiple bug trackers.


> I must admit that while I like git's simpler features I have a very hard time
> getting my head around the more advanced stuff and associated not-always-that-
> intuitive-to-me terminology (or getting its details into my head). Working 
> with
> branches, rebasing, etc., I'd like to think it becomes second nature when you 
> do
> it everyday, but that won't be the case for many if not most MacPorts users
> (including me).

It's something we all have to deal with. Presumably, we will all learn over 
time.


> [lament]
> Personally I have to look many things up every time, provided I even remember 
> or
> know of their existence (or I simply forget steps and then find myself with a
> commit I don't know how or cannot back out of).
> [/lament]

Feel free to ask on the -dev list, that's what it's for.

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

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

[Ralph Seichter]

On 03.11.2016 09:30, René J.V. Bertin wrote:

> For active tickets I spend too much time weeding through and deleting
> emails devoid of interest.

Have you tried using Sieve or your MUA's filter options to get rid of
e-mails you personally don't consider of interest? Notifications are a
major boon of issue trackers, and I'd rather have too many than too few
of them, because filtering can be done on the recipient side if the
generating tracker software does not offer enough options.

-Ralph

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

Re: GitHub migration complete

[René J . V . Bertin]

A question that came up due to another ticket:

last time I checked, github's issue tracker wasn't available for the ports 
repo. 
I presume that's on purpose, but why? Even if "we already have a bug tracker", 
why would it make life harder and not easier at least for some things?

I must admit that while I like git's simpler features I have a very hard time 
getting my head around the more advanced stuff and associated not-always-that-
intuitive-to-me terminology (or getting its details into my head). Working with 
branches, rebasing, etc., I'd like to think it becomes second nature when you 
do 
it everyday, but that won't be the case for many if not most MacPorts users 
(including me). 

[lament]
Personally I have to look many things up every time, provided I even remember 
or 
know of their existence (or I simply forget steps and then find myself with a 
commit I don't know how or cannot back out of).
[/lament]

R.

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

Re: 10.6.8 and ffmpeg

[René J . V . Bertin]

Mojca Miklavec wrote:

> I'm pretty sure one can make it build without 10.7 SDK, it will just
> take quite a bit of work to do so. Perhaps you know if there is an
> elegant way to actually patch the code in a way that would be
> acceptable for upstream in case we manage to find a sufficient set of
> patches (other than using a bunch of #if statements all over the
> place)?

How could you not use a bunch of #ifs if the code actually uses 10.7+ API calls 
that have to be filtered out?

Well, there *is* a way to do it following Qt's approach with d-pointers, where 
you put new stuff and things that don't work across the board in a private 
class, but that only reduces the number of #ifs required for features that 
aren't available on all supported platforms. And it's (probably) trickier to do 
right in C than C++ (as far as that's relevant here). Of course it also 
requires 
a far more extensive refactoring effort than simply putting #ifs all over the 
place.

And such an effort and extensive changes would probably be deemed out of 
proportion upstream if they're only to support a legacy OS, unless you can make 
a case that it'll prove useful for future introduction of other features that 
require a newer SDK than they'd like to require.

R.

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

Poll: should Trac send email notifications when adding or replacing an attachment?

[René J . V . Bertin]

Hi,

This is a poll about MacPorts's bug reporting engine, Trac. If you don't (plan 
to) use that thing, just delete this message.

Trac never sent notifications when you added or deleted (replaced) an 
attachment, but a recent introduced that as a new feature. I find this mostly 
useless and even annoying because when you update (replace, delete) an 
attachment there will be 2 emails. For active tickets I spend too much time 
weeding through and deleting emails devoid of interest. 

I've asked the administrators if something can be done about it. Not to insult 
anyone, but to put it bluntly, it does seem they cannot be bothered by 
something they consider an upstream problem namely that Trac doesn't have a 
feature to let users decide what notifications they want (and I agree this 
isn't for us to fix though evidently someone could try and submit a patch).

However, the documentation suggests it *is* possible to disable *all* 
notifications concerning attachments, and this is of course a choice that is 
MacPorts' to make.

The poll is intended to get an idea how to proceed:
1- Do you agree there is no need for (this many) notifications concerning 
changes to attachments (= you never missed it)?
2- Do you agree that there should be control over which attachment changes 
trigger a notification (e.g. only for new attachments)?
3- Do you agree that ideally this should be a per-user setting?

The more users agree with 2 and 3, the more weight an upstream bug/request 
ticket will have, at least when the ticket is filed by one of the trac.macports 
administrators. 
I'd also like to think that enough users agree with 1 that should be enough 
motivation for those administrators to consider disabling attachment 
notifications.
(The questions are worded to avoid bias towards preference for the status quo 
through silent agreement.)

I personally have done just fine without being notified about attachments *I 
myself* changed, and since most people will describe the changes made when they 
replace an attachment to a ticket I'm following I don't think I've ever missed 
anything in that domain.

Thanks,
René
---
#52752: trac: send fewer emails when replacing an attachment
-+--
  Reporter:  RJVB|  Owner:  admin@…
  Type:  enhancement | Status:  closed
  Priority:  Normal  |  Milestone:
 Component:  server/hosting  |Version:
Resolution:  wontfix |   Keywords:  upstream
  Port:  |
-+--
Changes (by neverpanic):

 * keywords:   => upstream
 * status:  assigned => closed
 * resolution:   => wontfix


Comment:

 This is a Trac upstream problem. We will not attempt to tackle this for
 our installation.

--
Ticket URL: 
MacPorts 
Ports system for macOS
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: 10.6.8 and ffmpeg

[Brandon Allbery]

On Wed, Nov 2, 2016 at 11:49 PM, Al Varnell  wrote:

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


Last time I checked it was "below the fold" but still there. I'm checking
now.


-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
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  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

[Ken Cunningham]

Wouldn’t it just be a treat if Jeremy fixed libsdl2’s code and this all went 
away :>

Ken




> On Nov 2, 2016, at 8:49 PM, Al Varnell  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.
> 
> -Al-

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

Re: 10.6.8 and ffmpeg

[Al Varnell]

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

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

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

Re: 10.6.8 and ffmpeg

[Al Varnell]

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

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

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

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

[Ken Cunningham]

no, it just points into a pthread folder.

let me try building (from source) a port that triggers your err.



> On Nov 2, 2016, at 8:40 PM, Ken Cunningham  
> wrote:
> 
> hmmm, So do I
> 
> lrwxr-xr-x  1 root  wheel  17 31 Oct 09:43 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h
>  -> pthread/pthread.h
> 
> 
> feels like we’re finding a bug, maybe.
> 
> Where is that symlink pointing, I wonder?
> 
> K
> 
> 
> 
>> On Nov 2, 2016, at 8:38 PM, Murray Eisenberg > > wrote:
>> 
>> I do have a symlink there:
>> 
>> [~]$ ls -la 
>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h
>> lrwxr-xr-x  1 root  wheel  17 Oct 28 15:04 
>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h
>>  -> pthread/pthread.h
>> 
>> [~]$ mdfind -name pthread.h
>> /usr/include/pthread/pthread.h
>> /Applications/MAMP/Library/include/my_pthread.h
>> /Applications/Server/mampstack/mysql/include/my_pthread.h
>> /Application Docs/Server/drupal-7.39-0/mysql/include/my_pthread.h
>> 
>> Note no change since El Capitan in the 2nd through 4th items there.
>> 
>> [:~]$ ls -la /usr/include/pthread/pthread.h
>> -rw-r--r--  1 root  wheel  19414 Sep 19 17:53 /usr/include/pthread/pthread.h
>> 
>>> On Nov 2, 2016, at 11:26 PM, Ken Cunningham 
>>> > 
>>> wrote:
>>> 
>>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h:423:25:
>>>  error: expected parameter declarator
>>> So I'd open that file and look at line 423 and see if you can figure out 
>>> what is happening.
>>> 
>>> If this is only you, then it’s something local on your system — who knows 
>>> what - bad file, etc, etc.
>>> 
>>> take a look at it with 
>>> 
>>> ls -la (that long filename).
>>> 
>>> is it a simlink? Is it messed up?
>>> 
>>> find another copy on your computer maybe
>>> 
>>> locate pthread.h
>>> 
>>> and compare them
>>> 
>>> —
>>> ultimately - reinstall it if nothing else works.
>>> 
>>> something is up…
>>> 
>>> 
>>> Ken
>> 
>> ---
>> Murray Eisenberg murrayeisenb...@gmail.com 
>> 
>> 503 King Farm Blvd #101  Home (240)-246-7240
>> Rockville, MD 20850-6667 Mobile (413)-427-5334
>> 
>> 
> 

___
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: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

[Ken Cunningham]

hmmm, So do I

lrwxr-xr-x  1 root  wheel  17 31 Oct 09:43 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h
 -> pthread/pthread.h


feels like we’re finding a bug, maybe.

Where is that symlink pointing, I wonder?

K



> On Nov 2, 2016, at 8:38 PM, Murray Eisenberg  
> wrote:
> 
> I do have a symlink there:
> 
> [~]$ ls -la 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h
> lrwxr-xr-x  1 root  wheel  17 Oct 28 15:04 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h
>  -> pthread/pthread.h
> 
> [~]$ mdfind -name pthread.h
> /usr/include/pthread/pthread.h
> /Applications/MAMP/Library/include/my_pthread.h
> /Applications/Server/mampstack/mysql/include/my_pthread.h
> /Application Docs/Server/drupal-7.39-0/mysql/include/my_pthread.h
> 
> Note no change since El Capitan in the 2nd through 4th items there.
> 
> [:~]$ ls -la /usr/include/pthread/pthread.h
> -rw-r--r--  1 root  wheel  19414 Sep 19 17:53 /usr/include/pthread/pthread.h
> 
>> On Nov 2, 2016, at 11:26 PM, Ken Cunningham > > wrote:
>> 
>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h:423:25:
>>  error: expected parameter declarator
>> So I'd open that file and look at line 423 and see if you can figure out 
>> what is happening.
>> 
>> If this is only you, then it’s something local on your system — who knows 
>> what - bad file, etc, etc.
>> 
>> take a look at it with 
>> 
>> ls -la (that long filename).
>> 
>> is it a simlink? Is it messed up?
>> 
>> find another copy on your computer maybe
>> 
>> locate pthread.h
>> 
>> and compare them
>> 
>> —
>> ultimately - reinstall it if nothing else works.
>> 
>> something is up…
>> 
>> 
>> Ken
> 
> ---
> Murray Eisenberg  murrayeisenb...@gmail.com 
> 
> 503 King Farm Blvd #101   Home (240)-246-7240
> Rockville, MD 20850-6667  Mobile (413)-427-5334
> 
> 

___
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)

[Murray Eisenberg]

I do have a symlink there:

[~]$ ls -la 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h
lrwxr-xr-x  1 root  wheel  17 Oct 28 15:04 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h
 -> pthread/pthread.h

[~]$ mdfind -name pthread.h
/usr/include/pthread/pthread.h
/Applications/MAMP/Library/include/my_pthread.h
/Applications/Server/mampstack/mysql/include/my_pthread.h
/Application Docs/Server/drupal-7.39-0/mysql/include/my_pthread.h

Note no change since El Capitan in the 2nd through 4th items there.

[:~]$ ls -la /usr/include/pthread/pthread.h
-rw-r--r--  1 root  wheel  19414 Sep 19 17:53 /usr/include/pthread/pthread.h

> On Nov 2, 2016, at 11:26 PM, Ken Cunningham  
> wrote:
> 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h:423:25:
>  error: expected parameter declarator
> So I'd open that file and look at line 423 and see if you can figure out what 
> is happening.
> 
> If this is only you, then it’s something local on your system — who knows 
> what - bad file, etc, etc.
> 
> take a look at it with 
> 
> ls -la (that long filename).
> 
> is it a simlink? Is it messed up?
> 
> find another copy on your computer maybe
> 
> locate pthread.h
> 
> and compare them
> 
> —
> ultimately - reinstall it if nothing else works.
> 
> something is up…
> 
> 
> Ken

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334


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

Re: 10.6.8 and ffmpeg

[Brandon Allbery]

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.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: 10.6.8 and ffmpeg

[Al Varnell]

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

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


Sent from Janet's iPad

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

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

[Murray Eisenberg]

Is there a cure (yet)?

> On Nov 2, 2016, at 11:31 PM, Brandon Allbery  wrote:
> 
> 
> On Wed, Nov 2, 2016 at 11:26 PM, Ken Cunningham 
> > 
> wrote:
> So I'd open that file and look at line 423 and see if you can figure out what 
> is happening.
> 
> It showed what was happening, clang is good about that. What was happening 
> was an Apple-defined macro that somehow was not defined, so it was being 
> parsed as a C function call where no such code should be.

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334


___
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)

[Brandon Allbery]

On Wed, Nov 2, 2016 at 11:26 PM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:

> So I'd open that file and look at line 423 and see if you can figure out
> what is happening.


It showed what was happening, clang is good about that. What was happening
was an Apple-defined macro that somehow was not defined, so it was being
parsed as a C function call where no such code should be.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
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)

[Ken Cunningham]

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h:423:25:
 error: expected parameter declarator
So I'd open that file and look at line 423 and see if you can figure out what 
is happening.

If this is only you, then it’s something local on your system — who knows what 
- bad file, etc, etc.

take a look at it with 

ls -la (that long filename).

is it a simlink? Is it messed up?

find another copy on your computer maybe

locate pthread.h

and compare them

—
ultimately - reinstall it if nothing else works.

something is up…


Ken___
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)

[Murray Eisenberg]

Note that lots of ports _have_ installed OK during the process of re-installing 
my ports under Sierra (and after installing tMacPorts-2.3.4-10.12-Sierra 
package) and checking that Xcode 8.1 and 
Command_Line_Tools_macOS_10.12_for_Xcode_8.1 was installed, too):

[~]$ sudo port installed
The following ports are currently installed:
  aspell @0.60.6.1_1 (active)
  aspell-dict-en @7.1_0 (active)
  at-spi2-atk @2.22.0_0 (active)
  at-spi2-core @2.22.0_0 (active)
  atk @2.22.0_0 (active)
  attica @0.4.2_1 (active)
  automoc @0.9.88_8 (active)
  bzip2 @1.0.6_0 (active)
  cairo @1.14.6_0+quartz+x11 (active)
  cctools @886_6+llvm38 (active)
  clang_select @2_0 (active)
  cmake @3.6.2_0 (active)
  curl @7.50.3_0+ssl (active)
  curl-ca-bundle @7.50.3_0 (active)
  db48 @4.8.30_4 (active)
  dbus @1.10.12_0 (active)
  dbus-glib @0.108_0 (active)
  dbus-python27 @1.2.0_2 (active)
  expat @2.2.0_0 (active)
  fftw-3 @3.3.5_0 (active)
  fontconfig @2.12.1_1 (active)
  fop @1.1_0 (active)
  freetype @2.7_0 (active)
  gdbm @1.12_0 (active)
  gdk-pixbuf2 @2.36.0_0+x11 (active)
  gettext @0.19.8.1_0 (active)
  glib2 @2.50.1_0 (active)
  gobject-introspection @1.50.0_0 (active)
  graphite2 @1.3.8_0 (active)
  gtk2 @2.24.31_0+x11 (active)
  gtk3 @3.22.2_0+x11 (active)
  harfbuzz @1.3.3_0 (active)
  hicolor-icon-theme @0.15_0 (active)
  jasper @1.900.16_1 (active)
  jpeg @9b_0 (active)
  lcms2 @2.8_0 (active)
  ld64 @2_0 (active)
  ld64-latest @264.3.102_3+llvm38 (active)
  libarchive @3.2.1_0 (active)
  libcxx @3.9.0_0+universal (active)
  libdaemon @0.14_0 (active)
  libedit @20160618-3.1_1 (active)
  libepoxy @1.3.1_3+python34 (active)
  libffi @3.2.1_0 (active)
  libglade2 @2.6.4_8 (active)
  libiconv @1.14_0 (active)
  libmng @2.0.3_0 (active)
  libpixman @0.34.0_0 (active)
  libpng @1.6.26_0 (active)
  libtool @2.4.6_2 (active)
  libxml2 @2.9.4_0 (active)
  llvm-3.8 @3.8.1_0 (active)
  llvm_select @2_0 (active)
  lzo2 @2.09_0 (active)
  mesa @12.0.1_1+osmesa+python27 (active)
  ncurses @6.0_0 (active)
  openssl @1.0.2j_0 (active)
  pango @1.40.3_1+quartz+x11 (active)
  pcre @8.39_0 (active)
  perl5 @5.24.0_0+perl5_24 (active)
  perl5.24 @5.24.0_0 (active)
  phonon @4.8.3_2 (active)
  py27-beaker @1.7.0_0 (active)
  py27-cairo @1.10.0_3 (active)
  py27-gdbm @2.7.12_0 (active)
  py27-gobject @2.28.6_3 (active)
  py27-mako @1.0.4_0 (active)
  py27-markupsafe @0.23_0 (active)
  py27-setuptools @28.7.0_0 (active)
  python2_select @0.0_2 (active)
  python3_select @0.0_1 (active)
  python27 @2.7.12_2 (active)
  python34 @3.4.5_1 (active)
  python_select @0.3_7 (active)
  qt4-mac @4.8.7_4 (active)
  shared-mime-info @1.7_0 (active)
  sqlite3 @3.15.0_0 (active)
  symlinks @1.4_0 (active)
  texinfo @6.3_0 (active)
  tiff @4.0.6_1 (active)
  Xft2 @2.3.2_0 (active)
  xorg-compositeproto @0.4.2_0 (active)
  xorg-damageproto @1.2.1_0 (active)
  xorg-dri2proto @2.8_0 (active)
  xorg-fixesproto @5.0_0 (active)
  xorg-glproto @1.4.17_0 (active)
  xorg-inputproto @2.3.2_0 (active)
  xorg-kbproto @1.0.7_0 (active)
  xorg-libice @1.0.9_0 (active)
  xorg-libpthread-stubs @0.3_0 (active)
  xorg-libsm @1.2.1_0 (active)
  xorg-libX11 @1.6.4_0 (active)
  xorg-libXau @1.0.8_0 (active)
  xorg-libxcb @1.12_2+python27 (active)
  xorg-libXcomposite @0.4.4_0 (active)
  xorg-libXcursor @1.1.14_0 (active)
  xorg-libXdamage @1.1.4_0 (active)
  xorg-libXdmcp @1.1.2_0 (active)
  xorg-libXext @1.3.3_0 (active)
  xorg-libXfixes @5.0.3_0 (active)
  xorg-libXi @1.7.8_0 (active)
  xorg-libXinerama @1.1.3_0 (active)
  xorg-libXmu @1.1.2_0 (active)
  xorg-libXrandr @1.5.1_0 (active)
  xorg-libXt @1.1.5_1 (active)
  xorg-libXtst @1.2.3_0 (active)
  xorg-libXxf86vm @1.1.4_0 (active)
  xorg-randrproto @1.5.0_0 (active)
  xorg-recordproto @1.14.2_0 (active)
  xorg-renderproto @0.11.1_0 (active)
  xorg-xcb-proto @1.12_1+python27 (active)
  xorg-xcb-util @0.4.0_0 (active)
  xorg-xextproto @7.3.0_0 (active)
  xorg-xf86vidmodeproto @2.3.1_0 (active)
  xorg-xineramaproto @1.2.1_0 (active)
  xorg-xproto @7.0.31_0 (active)
  xrender @0.9.10_0 (active)
  xz @5.2.2_0 (active)
  zlib @1.2.8_0 (active)
 
> On Nov 2, 2016, at 9:28 PM, Ken Cunningham  
> wrote:
> 
> here’s what I do when stuff like this happens
> 
> check your path `printenv` and see if it’s set correctly
> 
> cat ~/.profile
> 
> try “which clang” and “clang —version” 
> 
> try writing up a very simple “hello.c” source file and see if it compiles 
> (with the -v option to see what happens) and whether the executable runs
> 
> install some really really simple ports, like symlinks
> 
> …
> at least make sure the basics work
> …
> if all that works correctly, then … gotta dig deeper
> 
> Ken
> 
> 
> 
> 
>> On Nov 2, 2016, at 6:20 PM, Murray Eisenberg > > wrote:
>> 
>> I did install both Xcode 8.1 and the corresponding Xcode 8.1 tools for 
>> Sierra.  (not sure how to verify the version of command-line tools there.)
>> 
>> 

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

[Murray Eisenberg]

Yep, just noticed that when I was about to install clang-3.8 and remembered 
that didn’t update for me under OS X El Capitan and I saw that ticket.


> On Nov 2, 2016, at 11:17 PM, Ken Cunningham  
> wrote:
> 
> Murray, I note the error in your log looks somewhat like this error in trac:
> 
>  >
> 
> __SWIFT_UNAVAILABLE_MSG
> …
> 
> Ken

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334


___
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)

[Ken Cunningham]

Murray, I note the error in your log looks somewhat like this error in trac:



__SWIFT_UNAVAILABLE_MSG
…

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

Re: 10.6.8 and ffmpeg

[Ken Cunningham]

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

Well, everyone seems to feel it’s way to difficult to expect a user to do that, 
so I’m trying to help you come up with an easier way.

Of course, I just downloaded the darned thing myself, and I don’t see why that 
is too much to expect everyone else to do… but I don’t have 14 years of 
fielding tickets to put me off, I guess :>

K___
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: 10.6.8 and ffmpeg

[Ken Cunningham]

> 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? I suppose I'd get a call from 
Apple Legal if I did that ..?



K___
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)

[Murray Eisenberg]

Port symlinks does install OK. Environment look OK to me — see below.

I didn’t show my whole .profile here, but the only actual change to it since 
worked OK with OS X El Capitan & macports is the date in the comment line “# 
MacPorts Installer addition on …: adding an appropriate PATH variable for use 
with MacPorts.

[~]$ which clang
/usr/bin/clang
[~]$ clang --version
Apple LLVM version 8.0.0 (clang-800.0.42.1)
Target: x86_64-apple-darwin16.1.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

[~]$ printenv
MANPATH=/Applications/Math/Macaulay2/Macaulay2-1.9/share/man:
LDFLAGS=-L/opt/local/lib 
TERM_PROGRAM=Apple_Terminal
SHELL=/bin/bash
TERM=xterm-256color
CPPFLAGS=-I/opt/local/include 
TMPDIR=/var/folders/sv/1n3g81qj2bs90bfrvxr1pg78gn/T/
Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.1o6rfG1s0b/Render
TERM_PROGRAM_VERSION=387
TERM_SESSION_ID=13F982A2-7E7C-4D94-A24D-580AD0E5AB95
USER=me
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.1OSonPyIcF/Listeners
__CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0
PATH=/opt/local/lib/mysql56/bin:/Applications/Math/Macaulay2/Macaulay2-1.9/bin:/Library/TeX/texbin:/opt/local/bin:/opt/local/sbin:/opt/local/apache2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/MacGPG2/bin:/Library/TeX/texbin:/usr/local/sbin:/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib:/Library/Frameworks/Python.framework/Versions/3.5/bin:/Library/Frameworks/Python.framework/Versions/3.4/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/Applications/Programming/Python/anaconda/bin:/Users/me/Library/Application
 
Support/GoodSync:/Users/me/bin:/Applications/Math/Singular/3-1-6/ix86Mac-darwin:/Applications/Postgres.app/Contents/Versions/9.4/bin
PWD=/Users/me
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_111.jdk/Contents/Home
DBUS_LAUNCHD_SESSION_BUS_SOCKET=/private/tmp/com.apple.launchd.Y3hQQRkvmb/unix_domain_listener
LANG=en_US.UTF-8
XPC_FLAGS=0x0
PS1=[\u@\h:\w]$ 
XPC_SERVICE_NAME=0
SHLVL=1
HOME=/Users/me
LOGNAME=me
CLASSPATH=:/Library/Java/Extensions/mysql-connector-java-bin.jar:/Users/me/Library/texmf/texhyphj
INFOPATH=/Applications/Math/Macaulay2/Macaulay2-1.9/share/info
DISPLAY=/private/tmp/com.apple.launchd.KahliQQZCD/org.macosforge.xquartz:0
_=/usr/bin/printenv


> On Nov 2, 2016, at 9:28 PM, Ken Cunningham  
> wrote:
> 
> here’s what I do when stuff like this happens
> 
> check your path `printenv` and see if it’s set correctly
> 
> cat ~/.profile
> 
> try “which clang” and “clang —version” 
> 
> try writing up a very simple “hello.c” source file and see if it compiles 
> (with the -v option to see what happens) and whether the executable runs
> 
> install some really really simple ports, like symlinks
> 
> …
> at least make sure the basics work
> …
> if all that works correctly, then … gotta dig deeper
> 
> Ken
> 
> 
> 
> 
>> On Nov 2, 2016, at 6:20 PM, Murray Eisenberg > > wrote:
>> 
>> I did install both Xcode 8.1 and the corresponding Xcode 8.1 tools for 
>> Sierra.  (not sure how to verify the version of command-line tools there.)
>> 
>> [~”]$  xcode-select --install
>> xcode-select: error: command line tools are already installed, use "Software 
>> Update" to install updates
>> [murray@Blackstone:~]$ xcode-select -p
>> /Applications/Xcode.app/Contents/Developer
>> 
>> 
>>> On Nov 2, 2016, at 9:11 PM, Brandon Allbery >> > wrote:
>>> 
>>> 
>>> On Wed, Nov 2, 2016 at 9:08 PM, Murray Eisenberg >> > wrote:
>>> So I started doing a reinstall of ports for migration, and at first got a 
>>> “no C compiler available”
>>> 
>>> Sounds like missing command line tools to me.
>>> 
>>> 
>>> -- 
>>> brandon s allbery kf8nh   sine nomine associates
>>> allber...@gmail.com 
>>>   ballb...@sinenomine.net 
>>> unix, openafs, kerberos, infrastructure, xmonad
>>> http://sinenomine.net 
>> ---
>> Murray Eisenberg murrayeisenb...@gmail.com 
>> 
>> 503 King Farm Blvd #101  Home (240)-246-7240
>> Rockville, MD 20850-6667 Mobile (413)-427-5334
>> 
>> 
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org 
>> 
>> https://lists.macosforge.org/mailman/listinfo/macports-users 
>> 

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334


___

Re: 10.6.8 and ffmpeg

[Jeremy Huddleston Sequoia]

> On Nov 2, 2016, at 09:31, Ken Cunningham  
> wrote:
> 
> 
> On 2016-11-02, at 2:03 AM, Jeremy Huddleston Sequoia wrote:
> 
>> Do you know *why* it is requiring the 10.7 SDK to build?  Why can't libsdl2 
>> use the 10.6 SDK effectively?
>> 
> 
> I took a quick look at the code. It has a lot of AVAILABILITY_ macros in it, 
> a few mentioning 10.7, most of them mentioning IOS / IPHONE things.

I don't see any AVAILABILITY_ macros.  I do see on interesting reference to 
10.7 in src/video/cocoa/SDL_cocoawindow.m:

~/src/macports/dports/devel/libsdl2/work/SDL2-2.0.5 $ ack AVAILABILITY_

~/src/macports/dports/devel/libsdl2/work/SDL2-2.0.5 $ ack 10\\.7
docs/README-macosx.md
19:32-bit and 64-bit Intel architectures), on Mac OS X 10.7 and newer, by using
32:Please note that building SDL requires at least Xcode 4.6 and the 10.7 SDK

include/SDL_hints.h
576: *   the OS isn't at least Mac OS X Lion (10.7). This hint must be set 
before

src/video/cocoa/SDL_cocoamodes.m
47: *  It happens to work, as of 10.7, but we're going to see if

src/video/cocoa/SDL_cocoaopengl.m
178:/* specify a profile if we're on Lion (10.7) or later. */
331: * supported on 10.7+. */

src/video/cocoa/SDL_cocoavideo.m
155:/* The IOPM assertion API can disable the screensaver as of 10.7. */

src/video/cocoa/SDL_cocoawindow.m
26:# error SDL for Mac OS X must be built with a 10.7 SDK or above.

---

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 */

which doesn't indicate what the actual problem is.  What happens if you remove 
that?

> I assume that some of those macros don't work right with the 10.6 SDK, but 
> the details of exactly which ones I didn't look into.
> 
> It seems like a lot of work (too much!) to try to fix that code, and the next 
> version of libsdl2 would just break it all anyway.
> 
> The 10.7 SDK shouldn't be hard to find for anyone motivated to do so, and 
> once it's on the buildbot (and we get that libc++ buildbot naming issue 
> organized) that would make it sorta moot, I would think?
> 
> 
> Thanks,
> 
> Ken



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

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

[Murray Eisenberg]

All sorts of warnings and some errors in:

/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gmp/gmp/work/gmp-6.1.1-x86_64/config.log

Here’s the file:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by GNU MP configure 6.1.1, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure --prefix=/opt/local --enable-cxx

## - ##
## Platform. ##
## - ##

hostname = Blackstone.local
uname -m = x86_64
uname -r = 16.1.0
uname -s = Darwin
uname -v = Darwin Kernel Version 16.1.0: Wed Oct 19 20:31:56 PDT 2016; 
root:xnu-3789.21.4~4/RELEASE_X86_64

/usr/bin/uname -p = i386
/bin/uname -X = unknown

/bin/arch  = unknown
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = Mach kernel version:
 Darwin Kernel Version 16.1.0: Wed Oct 19 20:31:56 PDT 2016; 
root:xnu-3789.21.4~4/RELEASE_X86_64
Kernel configured for up to 8 processors.
4 processors are physically available.
8 processors are logically available.
Processor type: x86_64h (Intel x86-64h Haswell)
Processors active: 0 1 2 3 4 5 6 7
Primary memory available: 32.00 gigabytes
Default processor set: 391 tasks, 1487 threads, 8 processors
Load average: 2.35, Mach factor: 5.64
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /opt/local/bin
PATH: /opt/local/sbin
PATH: /bin
PATH: /sbin
PATH: /usr/bin
PATH: /usr/sbin


## --- ##
## Core tests. ##
## --- ##

configure:3055: checking build system type
configure:3069: result: skylake-apple-darwin16.1.0
configure:3089: checking host system type
configure:3102: result: skylake-apple-darwin16.1.0
configure:3139: checking for a BSD-compatible install
configure:3207: result: /usr/bin/install -c
configure:3218: checking whether build environment is sane
configure:3273: result: yes
configure:3424: checking for a thread-safe mkdir -p
configure:3463: result: ./install-sh -c -d
configure:3470: checking for gawk
configure:3497: result: /usr/bin/awk
configure:3508: checking whether make sets $(MAKE)
configure:3530: result: yes
configure:3559: checking whether make supports nested variables
configure:3576: result: yes
configure:3705: checking whether to enable maintainer-specific portions of 
Makefiles
configure:3714: result: no
User:
ABI=64
CC=/usr/bin/clang
CFLAGS=(unset)
CPPFLAGS=-I/opt/local/include
MPN_PATH=
GMP:
abilist=64 x32 32
cclist=gcc icc cc
configure:5713: /usr/bin/clang -c conftest.c >&5
configure:5716: $? = 0
configure:5719: checking whether /usr/bin/clang is gcc
configure:5721: result: yes
configure:5735: /usr/bin/clang 2>&1 | grep xlc >/dev/null
configure:5738: $? = 1
configure:5792: checking compiler /usr/bin/clang -O2 -pedantic 
-fomit-frame-pointer -m64 -I/opt/local/include
Test compile: 
configure:5806: /usr/bin/clang -O2 -pedantic -fomit-frame-pointer -m64 
-I/opt/local/include conftest.c >&5
configure:5809: $? = 0
configure:5814: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:5817: $? = 0
Test compile: function pointer return
configure:5860: /usr/bin/clang -O2 -pedantic -fomit-frame-pointer -m64 
-I/opt/local/include conftest.c >&5
configure:5863: $? = 0
configure:5868: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:5871: $? = 0
Test compile: cmov instruction
configure:5916: /usr/bin/clang -O2 -pedantic -fomit-frame-pointer -m64 
-I/opt/local/include conftest.c >&5
configure:5919: $? = 0
configure:5924: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:5927: $? = 0
Test compile: double -> ulong conversion
configure:5973: /usr/bin/clang -O2 -pedantic -fomit-frame-pointer -m64 
-I/opt/local/include conftest.c >&5
configure:5976: $? = 0
configure:5981: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:5984: $? = 0
Test compile: double negation
configure:6028: /usr/bin/clang -O2 -pedantic -fomit-frame-pointer -m64 
-I/opt/local/include conftest.c >&5
configure:6031: $? = 0
configure:6036: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:6039: $? = 0
Test compile: double -> float conversion
configure:6084: /usr/bin/clang -O2 -pedantic -fomit-frame-pointer -m64 
-I/opt/local/include conftest.c >&5
configure:6087: $? = 0
configure:6092: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:6095: $? = 0
Test compile: gnupro alpha ev6 char spilling
configure:6169: /usr/bin/clang -O2 -pedantic -fomit-frame-pointer -m64 
-I/opt/local/include conftest.c >&5
configure:6172: $? = 0
configure:6177: ./a.out || ./b.out || ./a.exe || ./a_out.exe || ./conftest
configure:6180: $? = 0
Test compile: __builtin_alloca availability
configure:6220: /usr/bin/clang -O2 -pedantic -fomit-frame-pointer -m64 
-I/opt/local/include conftest.c >&5
conftest.c:1:43: warning: control reaches end of non-void 

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

[Ken Cunningham]

here’s what I do when stuff like this happens

check your path `printenv` and see if it’s set correctly

cat ~/.profile

try “which clang” and “clang —version” 

try writing up a very simple “hello.c” source file and see if it compiles (with 
the -v option to see what happens) and whether the executable runs

install some really really simple ports, like symlinks

…
at least make sure the basics work
…
if all that works correctly, then … gotta dig deeper

Ken




> On Nov 2, 2016, at 6:20 PM, Murray Eisenberg  
> wrote:
> 
> I did install both Xcode 8.1 and the corresponding Xcode 8.1 tools for 
> Sierra.  (not sure how to verify the version of command-line tools there.)
> 
> [~”]$  xcode-select --install
> xcode-select: error: command line tools are already installed, use "Software 
> Update" to install updates
> [murray@Blackstone:~]$ xcode-select -p
> /Applications/Xcode.app/Contents/Developer
> 
> 
>> On Nov 2, 2016, at 9:11 PM, Brandon Allbery > > wrote:
>> 
>> 
>> On Wed, Nov 2, 2016 at 9:08 PM, Murray Eisenberg > > wrote:
>> So I started doing a reinstall of ports for migration, and at first got a 
>> “no C compiler available”
>> 
>> Sounds like missing command line tools to me.
>> 
>> 
>> -- 
>> brandon s allbery kf8nh   sine nomine associates
>> allber...@gmail.com  
>>  ballb...@sinenomine.net 
>> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net 
>> 
> ---
> Murray Eisenberg  murrayeisenb...@gmail.com 
> 
> 503 King Farm Blvd #101   Home (240)-246-7240
> Rockville, MD 20850-6667  Mobile (413)-427-5334
> 
> 
> ___
> 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: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

[Brandon Allbery]

On Wed, Nov 2, 2016 at 9:20 PM, Murray Eisenberg 
wrote:

> I did install both Xcode 8.1 and the corresponding Xcode 8.1 tools for
> Sierra.  (not sure how to verify the version of command-line tools there.)


Then I would want to look at config.log to determine why it doesn't think
you have a compiler.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
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)

[Murray Eisenberg]

I did install both Xcode 8.1 and the corresponding Xcode 8.1 tools for Sierra.  
(not sure how to verify the version of command-line tools there.)

[~”]$  xcode-select --install
xcode-select: error: command line tools are already installed, use "Software 
Update" to install updates
[murray@Blackstone:~]$ xcode-select -p
/Applications/Xcode.app/Contents/Developer


> On Nov 2, 2016, at 9:11 PM, Brandon Allbery  wrote:
> 
> 
> On Wed, Nov 2, 2016 at 9:08 PM, Murray Eisenberg  > wrote:
> So I started doing a reinstall of ports for migration, and at first got a “no 
> C compiler available”
> 
> Sounds like missing command line tools to me.
> 
> 
> -- 
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com   
> ballb...@sinenomine.net 
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net 
> 
---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334


___
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)

[Brandon Allbery]

On Wed, Nov 2, 2016 at 9:08 PM, Murray Eisenberg 
wrote:

> So I started doing a reinstall of ports for migration, and at first got a
> “no C compiler available”


Sounds like missing command line tools to me.


-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
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)

[Murray Eisenberg]

So I started doing a reinstall of ports for migration, and at first got a “no C 
compiler available”. Next I tried installing gcc, but that depends on gmp. But 
even trying 
sudo port install gmp @6.1.1_0+universal
failed. Error in configure, I thing at:

:debug:configure could not read "/opt/local/share/man/man5/stab.5.gz": no such 
file or directory
while executing
And, alas, that prevents reinstalling lots of other ports, since gcc depends on 
gmp, among others.

> On Nov 2, 2016, at 6: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?
> 
> 
> ---
> Murray Eisenberg  murrayeisenb...@gmail.com 
> 
> 503 King Farm Blvd #101   Home (240)-246-7240
> Rockville, MD 20850-6667  Mobile (413)-427-5334
> 
> 

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334


___
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)

[Murray Eisenberg]

Removed those 3 ports from myports.txt, ran the script again. Now another 
infinite loop:

[~:]$ sudo ./restore_ports.tcl myports.txt
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)


> On Nov 2, 2016, at 7:25 PM, Ryan Schmidt  wrote:
> 
>> 
>> 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.

---
Murray Eisenbergmurrayeisenb...@gmail.com
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334


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

Re: New mailing list host: lists.macports.org

[Ralph Seichter]

On 03.11.16 01:06, Rainer Müller wrote:

> For sender domains with a strict DMARC policy (p=reject or
> p=quarantine), the From address will be rewritten to the list
> address and the original sender will be in Reply-To.

This implies that you'll need SPF to pass for the mailing list's domain
if DKIM fails due to message body modifications, in order to achieve an
overall DMARC pass. I am assuming you're aware of this, though.

> To avoid invalidating DKIM at all, we would indeed need to remove the
> footers.

Indeed. Nudge, nudge. ;-)

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

Re: New mailing list host: lists.macports.org

[Rainer Müller]

On 2016-11-03 00:33, Ralph Seichter wrote:
> On 03.11.16 00:23, Ryan Schmidt wrote:
> 
>> The new mailing list server uses an updated version of mailman that is
>> supposed to handle this problem without the need to remove the email
>> footers.
> 
> If the sender signs message bodies and mailman modifies the bodies, DKIM
> signatures should, by design, become invalid. Like I mentioned before, the
> footers only repeat information given in the message headers anyway, so
> I can't see why we would not simply get rid of them.

To be more specific, we will make use of the mailman option
dmarc_moderation_action set to "Munge From". For sender domains with a
strict DMARC policy (p=reject or p=quarantine), the From address will be
rewritten to the list address and the original sender will be in
Reply-To. This will avoid bounces when the receiving mail server follows
DMARC policies.

To avoid invalidating DKIM at all, we would indeed need to remove the
footers.

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

Re: New mailing list host: lists.macports.org

[Ralph Seichter]

On 03.11.16 00:23, Ryan Schmidt wrote:

> The new mailing list server uses an updated version of mailman that is
> supposed to handle this problem without the need to remove the email
> footers.

If the sender signs message bodies and mailman modifies the bodies, DKIM
signatures should, by design, become invalid. Like I mentioned before, the
footers only repeat information given in the message headers anyway, so
I can't see why we would not simply get rid of them.

> Please let us know, after we move to the server, if you are still
> seeing such problems.

I'll be sure to check, it is easy enough to spot. ;-)

-Ralph
___
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: New mailing list host: lists.macports.org

[Ralph Seichter]

On 02.11.16 23:58, Gabriel Rosenkoetter wrote:

> I may be mistaken, but doesn't passing mail through an intermediate
> mailing list (not just normal STMP routing) inherently invalidate your
> source SMTP server's DKIM signature?

No, it does not, if the mailing list is configured correctly. DKIM
signatures are created for a subset of headers and the message body at
the sending MTA. As long as MTAs along the route don't modify the data
but only add headers -- which is the correct behaviour -- signatures
remain valid. That's exactly what DKIM is about.

Modifying content however invalidates the signatures. For mailing lists,
this typically happens when the subject lines are rewritten, or, as in
this particular list, footers are added to the body. The footer is not
only unnecessary because it does not add any information that is not
present in headers anyway, it is actively harmful. DKIM is used in DMARC,
and if domains use specific quarantine/reject policies based on strict
DKIM alignment, the messages will not propagate.

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