Re: 10.6.8 and ffmpeg

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 >

Re: 10.6.8 and ffmpeg

> 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

Re: 10.6.8 and ffmpeg

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,

Re: 10.6.8 and ffmpeg

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

Re: 10.6.8 and ffmpeg

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

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

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 >

Re: 10.6.8 and ffmpeg

> 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

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

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

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

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

Re: 10.6.8 and ffmpeg

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

Re: 10.6.8 and ffmpeg

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

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

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

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

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

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

/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

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

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

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

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

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

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

Re: 10.6.8 and ffmpeg

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

Re: 10.6.8 and ffmpeg

> 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

Re: 10.6.8 and ffmpeg

> 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

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

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

Re: 10.6.8 and ffmpeg

> 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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]"

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

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

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

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

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

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,

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

> 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

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

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

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

On 02 Nov, 2016, at 16:48 CST, Ralph Seichter wrote: > On 02.11.16 23:24, Rainer Müller wrote: >> as part of the move off of macOS forge, we will migrate the mailing >> lists to the new mail server. > While you are working on the ML anyway: can you please change list >

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

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:

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

On 02.11.16 23:24, Rainer Müller wrote: > as part of the move off of macOS forge, we will migrate the mailing > lists to the new mail server. While you are working on the ML anyway: can you please change list settings to *not* add footer information to mail bodies or modify subject lines. These

New mailing list host: lists.macports.org

Hello, as part of the move off of macOS forge, we will migrate the mailing lists to the new mail server. We will migrate all subscriptions and user preferences and postings to the old mailing list addresses will be forwarded. However, the new hostname lists.macports.org implies that addresses and

Re: 10.6.8 and ffmpeg

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

Re: Error in updating macports

what does `host rsync.macports.org` say? what does `traceroute rsync.macports.org` say? what does `route get rsync.macports.org` say? > On Nov 1, 2016, at 11:05 PM, Sumanth wrote: > -- Forwarded message -- > From: "Sumanth"

Re: 10.6.8 and ffmpeg

On 2 November 2016 at 10:03, 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? See my analysis at https://trac.macports.org/ticket/52210#comment:9 I'm pretty sure one can make it build without 10.7

Re: 10.6.8 and ffmpeg

On 2 November 2016 at 09:46, Davide Liessi wrote: > 2016-10-30 15:38 GMT+01:00 Ryan Schmidt: >> copying the 10.7 SDK into /Developer/SDKs is the simplest solution. > > How can I get a copy of the 10.7 SDK? > I have only the 10.5 and 10.6 SDKs on my machine. I didn't test this, but I guess that

Re: 10.6.8 and ffmpeg

Do you know *why* it is requiring the 10.7 SDK to build? Why can't libsdl2 use the 10.6 SDK effectively? > On Oct 31, 2016, at 20:44, Ken Cunningham > wrote: > >> >> I’d be happy to test the minimum requirements to build it, if Richard >> doesn’t beat me to