Re: 10.6.8 and ffmpeg

2016-11-03 Thread 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

Re: 10.6.8 and ffmpeg

2016-11-02 Thread 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

2016-11-02 Thread 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

2016-11-02 Thread 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

2016-11-02 Thread 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

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

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

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

Re: 10.6.8 and ffmpeg

2016-11-02 Thread Ryan Schmidt 

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

This is the first I'm hearing about that. Can you provide further information? 
Citation?

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

Re: 10.6.8 and ffmpeg

2016-11-02 Thread 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

2016-11-02 Thread 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: 10.6.8 and ffmpeg

2016-11-02 Thread 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

2016-11-02 Thread 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

2016-11-02 Thread 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: 10.6.8 and ffmpeg

2016-11-02 Thread 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: 10.6.8 and ffmpeg

2016-11-02 Thread Ken Cunningham 

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 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___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: 10.6.8 and ffmpeg

2016-11-02 Thread Mojca Miklavec 
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 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)?

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

Re: 10.6.8 and ffmpeg

2016-11-02 Thread Mojca Miklavec 
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 you should be be able to download
Xcode for 10.7 from Apple developer site (say version 4.6.3), extract
it from the command-line (hdiutil attach "Xcode 4.6.3.dmg") and copy
the SDK.

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

Re: 10.6.8 and ffmpeg

2016-11-02 Thread Jeremy Huddleston Sequoia 
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 it :>
>> 
>> Get back to you in a day or two with the info.
>> 
> 
> Hello friends,
> 
> ran some tests with a spanking new installation of 10.6.8 and macports 2.3.4 
> with nothing installed
> 
> 
> to build libsdl2 on 10.6.8 requires
> 
> MacOS10.7.sdk in ${developer_dir}/SDKs/MacOSX10.7.sdk
> 
> and 
> 
> PortGroup compiler_blacklist_versions 1.0
> compiler.blacklist *gcc* { clang < 211 }
> 
> 
> I have no clue how to submit a portfile *.diff any longer (is that a sigh of 
> relief I hear?? :> ) , but hopefully this helps.
> 
> 
> Best,
> 
> Ken
> 
> 
> 
> ___
> 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: 10.6.8 and ffmpeg

2016-10-31 Thread Ken Cunningham 

On 2016-10-31, at 2:28 AM, René J. V. Bertin wrote:
> 
> Probably an open door, possibly a forbidden one: it may be relevant here to 
> block concerned ports at the latest supported version for legacy platforms? 

Although I think not needed for libsdl2 (which builds and works without issue 
on 10.6.8), this idea is a good one, needed, and in fact was about the first 
post I ever made on macports.

(trac is down again, or I'd reference the post from about June).

A collection of ports pegged to the 'last working' version is absolutely needed 
to make macports work on 10.4, 10.5, and 10.6. 

One Raimue explained how to do this, I set this up for my own use a while back, 
and shared it on github for others to use:

https://github.com/ken-cunningham-webuse/TigerPorts
https://github.com/ken-cunningham-webuse/LeopardPorts
https://github.com/ken-cunningham-webuse/SnowLeopardPorts

These are three shadow repos for such 'last known working' ports for these 
systems (and also a few fixes to allow some ports to work on these os versions 
that were never accepted into svn for one reason or another).



Ken



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

Re: 10.6.8 and ffmpeg

2016-10-31 Thread René J . V . Bertin 
David Evans wrote:


> However, sdl/sdl2 provides the only audio/video outdev that we support in
> MacPorts which means that if you have to have one or the other. Without an
> outdev, ffplay will not be configured/built and you'll have no direct way to
> play audio/video with ffmpeg.

It's been too long since I configured and built ffmpeg for my own purposes, but 
is SDL really the only outdev that's feasible to support on 10.6 ? I would have 
assumed that there was a "more native" option, based on OpenGL for instance, 
but 
I can be wrong.

That said, if ffplay is the only casualty when SDL is lacking, then maybe 
that's 
a reasonable concession to make in order to keep supporting other unsupported 
OS 
versions (and platforms)? I know, it's a useful little tool for taking a quick 
look at or listen to content that cannot be opened by QuickTime, but I don't 
think that's a huge collection given Perian still works perfectly on 10.6 .

Probably an open door, possibly a forbidden one: it may be relevant here to 
block concerned ports at the latest supported version for legacy platforms? 
That's the formal implementation of the advice given above (for port:ffmpeg) 
not 
to update the port, but has the advantage that users will still be able to use 
`port selfupdate && port upgrade outdated` without manual intervention. It'd 
also give dependents more of an incentive to print a proper error - they can 
then check on a known OS version or platform type instead of having to figure 
out 
the installed version.

R.

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

Re: 10.6.8 and ffmpeg

2016-10-30 Thread Ken Cunningham 
Oh — I see that there’s a lot of build info in

docs/ README-macosx.md

in there it says you need minimum Xcode 4.6 and the 10.7 SDK (maybe that’s why 
macports-clang-3.7 worked for me?)

and a lot more info that I didn’t read fully through.

Ken








> On Oct 30, 2016, at 2:28 PM, Ken Cunningham  
> wrote:
> 
>> 
>> Agreed, the problem here is with libsdl2.  We need to understand what the 
>> problem is on
>> 10.6 at least and either help upstream to fix it or fix it ourselves. 
> 
> 
> Dave,
> 
> I may not be seeing the entire picture (often happens!), but I don’t think 
> there is actually a problem on 10.6. It uses the more recent SDKs mostly for 
> the iPhone IOS stuff, I think, and maybe for a few other features.
> 
> It’s just written in that Availability.h Apple-sanctioned way that enables 
> certain features on higher OS versions, but works on lower OS versions as 
> well. 
> 
> 
> For example, in MacOSX 10.7 there is a show and hide menu bar feature that is 
> enabled if you are on 10.7, but worked around on 10.6.
> 
> #if (MAC_OS_X_VERSION_MIN_REQUIRED < 1070) && !defined(__LP64__)
> if (show) {
> ShowMenuBar();
> } else {
> HideMenuBar();
> }
> #endif
> 
> 
> one thing — in the code of libsdl 2.05 it has this:
> 
> #if MAC_OS_X_VERSION_MIN_REQUIRED < 1060
> # error SDL for Mac OS X only supports deploying on 10.6 and above.
> 
> 
> so I think 10.5 is out of luck. libSDL 2.02 or 2.03 was still OK on 10.5 I 
> think. I couldn’t get 2.04 to work, and gave up trying as life is too short.
> 
> 
> 
> Ken
> 
> 
> 

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

Re: 10.6.8 and ffmpeg

2016-10-30 Thread Ken Cunningham 
> 
> Agreed, the problem here is with libsdl2.  We need to understand what the 
> problem is on
> 10.6 at least and either help upstream to fix it or fix it ourselves. 


Dave,

I may not be seeing the entire picture (often happens!), but I don’t think 
there is actually a problem on 10.6. It uses the more recent SDKs mostly for 
the iPhone IOS stuff, I think, and maybe for a few other features.

It’s just written in that Availability.h Apple-sanctioned way that enables 
certain features on higher OS versions, but works on lower OS versions as well. 


For example, in MacOSX 10.7 there is a show and hide menu bar feature that is 
enabled if you are on 10.7, but worked around on 10.6.

#if (MAC_OS_X_VERSION_MIN_REQUIRED < 1070) && !defined(__LP64__)
if (show) {
ShowMenuBar();
} else {
HideMenuBar();
}
#endif


one thing — in the code of libsdl 2.05 it has this:

#if MAC_OS_X_VERSION_MIN_REQUIRED < 1060
# error SDL for Mac OS X only supports deploying on 10.6 and above.


so I think 10.5 is out of luck. libSDL 2.02 or 2.03 was still OK on 10.5 I 
think. I couldn’t get 2.04 to work, and gave up trying as life is too short.



Ken



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

Re: 10.6.8 and ffmpeg

2016-10-30 Thread David Evans 
On 10/30/16 1:13 AM, Davide Liessi wrote:
> 2016-10-30 1:23 GMT+02:00 Ryan Schmidt :
>> If sdl2 can be built on Snow Leopard using a copy of the 10.7 SDK obtained 
>> from a later Xcode, and that sdl2 then works ok on Snow Leopard, then I'd be 
>> happy if we could come up with an official way to support that, and then we 
>> could do that on the buildbot, which would cover a lot of users' needs.
> 
>>From libsdl's wiki (http://wiki.libsdl.org/Installation#Mac_OS_X):
> "SDL2 has dropped support for PowerPC Macs and OS X versions older
> than 10.5 (SDL 1.2 still supports PPC and 10.0, though)."
> Which implies that 10.5 is still supported, and indeed they describe
> the Mac binary download as "Intel 10.5+"
> (https://www.libsdl.org/download-2.0.php).
> Libsdl2 not building on 10.6 is either a bug in MacPorts, a bug in
> libsdl2 or a bug in libsdl's documentation.
> 
> Best wishes.
> Davide
> .
> 

Agreed, the problem here is with libsdl2.  We need to understand what the 
problem is on
10.6 at least and either help upstream to fix it or fix it ourselves.  If all 
that fails
then maybe upstream needs to revise they're thinking on macOS compatibility.

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

Re: 10.6.8 and ffmpeg

2016-10-30 Thread Ken Cunningham 
>  I can do that on the buildbot machines, and we can write the libsdl2 
> portfile so that it uses that SDK if available and instructs the user how to 
> download and install it if it's not yet there.


The portfile is already written like that.

Also, see:





Ken

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

Re: 10.6.8 and ffmpeg

2016-10-29 Thread David Evans 
On 10/29/16 4:23 PM, Ryan Schmidt wrote:
> 
>> On Oct 29, 2016, at 5:32 PM, David Evans  wrote:
>>
>> On 10/28/16 9:58 PM, Richard L. Hamilton wrote:
>>> Am I right in thinking that  ffmpeg now requires libsdl2 while it 
>>> previously required libsdl?  That causes ffmpeg to fail on 10.6.x, because 
>>> libsdl2 fails:
>>>
>>> Error: org.macports.fetch for port libsdl2 returned: Building libsdl2 
>>> requires OS X 10.7 SDK or later
>>> Error: Failed to install libsdl2
>>> Please see the log file for port libsdl2 for details:
>>>
>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/main.log
>>> Error: The following dependencies were not installed: libsdl2
>>> Error: Unable to upgrade port: 1
>>> To report a bug, follow the instructions in the guide:
>>>http://guide.macports.org/#project.tickets
>>>
>>
>> Yep, it was a recent upstream decision to remove support for sdl1 and 
>> replace it with sdl2.  Their rationale is that
>> sdl2 is the mainstream version of the library and sdl has not been 
>> maintained since about 2012. With the 3.2 release
>> this effects both ffmpeg and ffmpeg-devel.  See 
>> http://ffmpeg.org/index.html#news for the announcement.
>>
>> Our choice then is to upgrade the port and go with sdl2 or stick with sdl 
>> and never upgrade the port again.  We chose
>> follow ffmpeg's update path.  But you could choose not to update locally and 
>> stay with the ffmpeg <= 3.1.5 which only
>> supports sdl (not sdl2).  This is probably a better way to go than trying to 
>> shoehorn the 10.7 SDK into a 10.6
>> environment.  Or if you're going to do that why not update to 10.7 or better.
> 
> There are Macs that cannot update to 10.7 or later, but which might still be 
> viable as audio/video playing machines.
I knew this.  As I was typing it, I was thinking maybe I should add, if you 
can.  But if you can, it seems a safer bet
to me.
> 
> Requiring sdl2 in ffmpeg kinda sucks because now a lot of ports that use 
> ffmpeg that worked fine on Snow Leopard don't anymore, including pianobar. I 
> just finally convinced the pianobar developers to add a compatibility getline 
> function so that it can build on Snow Leopard again, and now ffmpeg's sdl2 
> requirement makes it not work on Snow Leopard again.

I hear what you're saying but the way they did it upstream there's not much 
choice with ffmpeg.  Frankly, I think
they've probably been taking a lot of flack for keeping sdl1 so long.  But one 
might petition them to add back
sdl1 support as an option.  Note that ffplay and the relevant outdevs have had 
sdl2 version dependent changes
with this release so it may not be as easy as it sounds. So it would be a 
moderate pain for them to support.
Probably why they decided to do it "cold turkey."



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

Re: 10.6.8 and ffmpeg

2016-10-29 Thread Richard L. Hamilton 

> On Oct 29, 2016, at 16:23, Ryan Schmidt  wrote:
> 
> 
>> On Oct 29, 2016, at 5:32 PM, David Evans  wrote:
>> 
>> On 10/28/16 9:58 PM, Richard L. Hamilton wrote:
>>> Am I right in thinking that  ffmpeg now requires libsdl2 while it 
>>> previously required libsdl?  That causes ffmpeg to fail on 10.6.x, because 
>>> libsdl2 fails:
>>> 
>>> Error: org.macports.fetch for port libsdl2 returned: Building libsdl2 
>>> requires OS X 10.7 SDK or later
>>> Error: Failed to install libsdl2
>>> Please see the log file for port libsdl2 for details:
>>>   
>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/main.log
>>> Error: The following dependencies were not installed: libsdl2
>>> Error: Unable to upgrade port: 1
>>> To report a bug, follow the instructions in the guide:
>>>   http://guide.macports.org/#project.tickets
>>> 
>> 
>> Yep, it was a recent upstream decision to remove support for sdl1 and 
>> replace it with sdl2.  Their rationale is that
>> sdl2 is the mainstream version of the library and sdl has not been 
>> maintained since about 2012. With the 3.2 release
>> this effects both ffmpeg and ffmpeg-devel.  See 
>> http://ffmpeg.org/index.html#news for the announcement.
>> 
>> Our choice then is to upgrade the port and go with sdl2 or stick with sdl 
>> and never upgrade the port again.  We chose
>> follow ffmpeg's update path.  But you could choose not to update locally and 
>> stay with the ffmpeg <= 3.1.5 which only
>> supports sdl (not sdl2).  This is probably a better way to go than trying to 
>> shoehorn the 10.7 SDK into a 10.6
>> environment.  Or if you're going to do that why not update to 10.7 or better.
> 
> There are Macs that cannot update to 10.7 or later, but which might still be 
> viable as audio/video playing machines.
> 
> Requiring sdl2 in ffmpeg kinda sucks because now a lot of ports that use 
> ffmpeg that worked fine on Snow Leopard don't anymore, including pianobar. I 
> just finally convinced the pianobar developers to add a compatibility getline 
> function so that it can build on Snow Leopard again, and now ffmpeg's sdl2 
> requirement makes it not work on Snow Leopard again.
> 
> If sdl2 can be built on Snow Leopard using a copy of the 10.7 SDK obtained 
> from a later Xcode, and that sdl2 then works ok on Snow Leopard, then I'd be 
> happy if we could come up with an official way to support that, and then we 
> could do that on the buildbot, which would cover a lot of users' needs.
> 

I think my 2007 Mac Mini could go up to Lion...but I'm sticking with Snow 
Leopard on it because it still has Rosetta, for compatibility with the few 
PowerPC binaries (not MacPorts!) that were never ported.  My other Mac Mini is 
finally on El Capitan as is my early 2015 MacBook Pro 13" (Retina).  Not ready 
to deal with Sierra quite yet...and the Mac Mini already being cranky sometimes 
after the last upgrade, I suppose I'd end up refreshing my rsync image of it 
(nfs'd from another box with LOTS of disk space) and doing a clean install of 
Sierra on it if I were to update it again.


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

Re: 10.6.8 and ffmpeg

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

As you wish. 

Personally I agree with you, but then I don’t field the tickets that might 
follow...

I can attest to the fact it builds and works well enough on the configuration I 
mentioned. The macpro I use it on has a pretty good video card for the day. 
Once it’s built, there is no further need for the 10.7 sdk, so someone getting 
it from a buildbot would not need to know any of this unless they wanted to 
rebuild it from source (libc++ , basically).

I’d be happy to test the minimum requirements to build it, if Richard doesn’t 
beat me to it :>

Get back to you in a day or two with the info.

Ken


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

Re: 10.6.8 and ffmpeg

2016-10-29 Thread Ryan Schmidt 

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

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

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

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

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

Re: 10.6.8 and ffmpeg

2016-10-29 Thread David Evans 
On 10/28/16 9:58 PM, Richard L. Hamilton wrote:
> Am I right in thinking that  ffmpeg now requires libsdl2 while it previously 
> required libsdl?  That causes ffmpeg to fail on 10.6.x, because libsdl2 fails:
> 
> Error: org.macports.fetch for port libsdl2 returned: Building libsdl2 
> requires OS X 10.7 SDK or later
> Error: Failed to install libsdl2
> Please see the log file for port libsdl2 for details:
> 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/main.log
> Error: The following dependencies were not installed: libsdl2
> Error: Unable to upgrade port: 1
> To report a bug, follow the instructions in the guide:
> http://guide.macports.org/#project.tickets
> 

Yep, it was a recent upstream decision to remove support for sdl1 and replace 
it with sdl2.  Their rationale is that
sdl2 is the mainstream version of the library and sdl has not been maintained 
since about 2012. With the 3.2 release
this effects both ffmpeg and ffmpeg-devel.  See 
http://ffmpeg.org/index.html#news for the announcement.

Our choice then is to upgrade the port and go with sdl2 or stick with sdl and 
never upgrade the port again.  We chose
follow ffmpeg's update path.  But you could choose not to update locally and 
stay with the ffmpeg <= 3.1.5 which only
supports sdl (not sdl2).  This is probably a better way to go than trying to 
shoehorn the 10.7 SDK into a 10.6
environment.  Or if you're going to do that why not update to 10.7 or better.

However, sdl/sdl2 provides the only audio/video outdev that we support in 
MacPorts which means that if you have to
have one or the other. Without an outdev, ffplay will not be configured/built 
and you'll have no direct way to play
audio/video with ffmpeg.

Dave



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

Re: 10.6.8 and ffmpeg

2016-10-29 Thread Ken Cunningham 
Hi Richard

You have a lot of Xcode versions installed! Keeping them all straight must be a 
bit of a mind-bender.
perhaps select the most modern one (Xcode 4.2) and put the macOSX10.7.sdk in 
there?

> ld: library not found for -lcrt1.10.6.o
that's a bit weird. that's a basic library.



In the 'full disclosure' category, my day-to-day 10.6.8 setup is as follows:

Xcode 4.2 is installed in /Developer and usually selected unless I'm testing 
something for Xcode 3.2.6, which I have installed in /Xcode3 but usually not 
selected
MacOSX10.7.sdk added to  /Developer/SDKs/MacOSX10.7.sdk (only used by libsdl2 
that I know of)
LibcxxOnOlderSystems installed
default compiler set to macports-clang-3.7 (as per the libcxx instructions)


Best,

Ken





On 2016-10-29, at 7:02 AM, Richard L. Hamilton wrote:

> Thanks - closer, but must be more to it than that:
> 
> h-3.2# ls -ld /Dev*
> lrwxr-xr-x   1 root  admin   16 Aug 23 20:42 /Developer -> /Developer-3.2.6
> drwxrwxr-x@ 20 root  admin  680 Nov 16  2010 /Developer-3.2.2
> drwxrwxr-x@ 16 root  admin  544 Aug 23 19:50 /Developer-3.2.6
> drwxrwxr-x  14 root  admin  476 Jun  4  2011 /Developer-4.0.2
> drwxrwxr-x  14 root  admin  476 Mar 26  2015 /Developer-4.2
> 
> sh-3.2# ls /Developer?*/SDKs
> /Developer-3.2.2/SDKs:
> MacOSX10.4u.sdk   MacOSX10.5.sdk  MacOSX10.6.sdk
> 
> /Developer-3.2.6/SDKs:
> MacOSX10.5.sdkMacOSX10.6.sdk  MacOSX10.7.sdk
> 
> /Developer-4.0.2/SDKs:
> MacOSX10.6.sdk
> 
> /Developer-4.2/SDKs:
> MacOSX10.6.sdk
> 
> sh-3.2# xcode-select --print-path
> /Developer-3.2.6
> 
> 
> --->  Configuring libsdl2
> Error: Failed to configure libsdl2, consult 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/work/SDL2-2.0.5/config.log
> 
> 
> Lines of likely interest from config.log:
> 
> configure:2919: checking for gcc
> configure:2946: result: /usr/bin/gcc-4.2
> configure:3175: checking for C compiler version
> configure:3184: /usr/bin/gcc-4.2 --version >&5
> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> configure:3195: $? = 0
> configure:3184: /usr/bin/gcc-4.2 -v >&5
> Using built-in specs.
> Target: i686-apple-darwin10
> Configured with: /var/tmp/gcc/gcc-5666.3~6/src/configure --disable-checking 
> --enable-werror --prefix=/usr --mandir=/share/man 
> --enable-languages=c,objc,c++,obj-c++ 
> --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib 
> --build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- 
> --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 
> --with-gxx-include-dir=/include/c++/4.2.1
> Thread model: posix
> gcc version 4.2.1 (Apple Inc. build 5666) (dot 3)
> configure:3195: $? = 0
> configure:3184: /usr/bin/gcc-4.2 -V >&5
> gcc-4.2: argument to `-V' is missing
> configure:3195: $? = 1
> configure:3184: /usr/bin/gcc-4.2 -qversion >&5
> i686-apple-darwin10-gcc-4.2.1: no input files
> configure:3195: $? = 1
> configure:3215: checking whether the C compiler works
> configure:3237: /usr/bin/gcc-4.2 -pipe -Os 
> -isysroot/Developer-3.2.6/SDKs/MacOSX10.7.sdk -arch x86_64 -arch i386 
> -I/opt/local/include -isysroot/Developer-3.2.6/SDKs/MacOSX10.7.sdk 
> -L/opt/local/lib -Wl,-headerpad_max_install_names 
> -Wl,-syslibroot,/Developer-3.2.6/SDKs/MacOSX10.7.sdk -arch x86_64 -arch i386 
> conftest.c  >&5
> ld: library not found for -lcrt1.10.6.o
> collect2: ld returned 1 exit status
> ld: library not found for -lcrt1.10.6.o
> collect2: ld returned 1 exit status
> fatal error: lipo: can't open input file: 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/work/.tmp/ccWPQ19t.out
>  (No such file or directory)
> configure:3241: $? = 1
> configure:3279: result: no
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE_URL ""
> | /* end confdefs.h.  */
> | 
> | int
> | main ()
> | {
> | 
> |   ;
> |   return 0;
> | }
> configure:3284: error: in 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/work/SDL2-2.0.5':
> configure:3286: error: C compiler cannot create executables
> See `config.log' for more details
> 
> 
> sh-3.2# /Users/rlhamil/bin/vers  # a script of mine that outputs the versions 
> of various interesting things that might be relevant
> Hardware Version: Mac mini (Mid 2007)
> Model Identifier: Macmini2,1
> Mac OS X 10.6.8 10K549 (Snow Leopard)
> Xcode 3.2.6 DevToolsSupport-1806.0
> MacPorts Version: 2.3.4
> 
> 
>> On Oct 28, 2016, at 22:05, Ken Cunningham

Re: 10.6.8 and ffmpeg

2016-10-29 Thread Ken Cunningham 
I know -- I'm sorry for stepping out there and just blurting it like that. I'm 
just trying to help Richard 'get it done'.

Also - I upgraded libsdl to the new 2.0.5 version here -- perhaps i should put 
up a diff for JMR to use?

Best,

Ken


$ port -v installed | grep ffmpeg
  ffmpeg @3.1.4_0+gpl2+x11 platform='darwin 10' archs='x86_64'
  ffmpeg @3.1.5_0+gpl2+x11 (active) platform='darwin 10' archs='x86_64'


$ port -v installed | grep libsdl
  libsdl @1.2.15_3+universal+x11 (active) platform='darwin 10' archs='i386 
x86_64'
  libsdl2 @2.0.4_0+universal platform='darwin 10' archs='i386 x86_64'
  libsdl2 @2.0.5_0 platform='darwin 10' archs='x86_64'
  libsdl2 @2.0.5_0+universal (active) platform='darwin 10' archs='i386 x86_64'
  libsdl2_image @2.0.1_0+universal (active) platform='darwin 10' archs='i386 
x86_64'
  libsdl2_mixer @2.0.1_0 (active) platform='darwin 10' archs='x86_64'
  libsdl2_net @2.0.1_0+universal (active) platform='darwin 10' archs='i386 
x86_64'
  libsdl2_ttf @2.0.14_0 (active) platform='darwin 10' archs='x86_64'
  libsdl_gfx @2.0.24_1 (active) platform='darwin 10' archs='x86_64'
  libsdl_image @1.2.12_5 (active) platform='darwin 10' archs='x86_64'
  libsdl_mixer @1.2.12_0 (active) platform='darwin 10' archs='x86_64'
  libsdl_net @1.2.8_0 (active) platform='darwin 10' archs='x86_64'
  libsdl_ttf @2.0.11_0 (active) platform='darwin 10' archs='x86_64'




On 2016-10-29, at 7:17 AM, Ryan Schmidt wrote:

> 
>> On Oct 29, 2016, at 12:05 AM, Ken Cunningham 
>>  wrote:
>> 
>> libsdl2 will build without trouble on 10.6.8 if you find a copy of the 10.7 
>> SDK and put it like so in /Developer/SDKs/MacOSX10.7.sdk
> 
> That is not a procedure we have ever recommended users do before. I know that 
> using the 10.12 SDK on 10.11 will work. If using the 10.7 SDK on 10.6 will 
> work, and we want to help users do that, maybe we should have a documented 
> way for the user to do that. And maybe we should install the 10.7 SDK on the 
> 10.6 buildbot machines so that these ports can be built automatically.
> 

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

Re: 10.6.8 and ffmpeg

2016-10-29 Thread Ryan Schmidt 

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

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

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

Re: 10.6.8 and ffmpeg

2016-10-29 Thread Richard L. Hamilton 
Thanks - closer, but must be more to it than that:

h-3.2# ls -ld /Dev*
lrwxr-xr-x   1 root  admin   16 Aug 23 20:42 /Developer -> /Developer-3.2.6
drwxrwxr-x@ 20 root  admin  680 Nov 16  2010 /Developer-3.2.2
drwxrwxr-x@ 16 root  admin  544 Aug 23 19:50 /Developer-3.2.6
drwxrwxr-x  14 root  admin  476 Jun  4  2011 /Developer-4.0.2
drwxrwxr-x  14 root  admin  476 Mar 26  2015 /Developer-4.2

sh-3.2# ls /Developer?*/SDKs
/Developer-3.2.2/SDKs:
MacOSX10.4u.sdk MacOSX10.5.sdk  MacOSX10.6.sdk

/Developer-3.2.6/SDKs:
MacOSX10.5.sdk  MacOSX10.6.sdk  MacOSX10.7.sdk

/Developer-4.0.2/SDKs:
MacOSX10.6.sdk

/Developer-4.2/SDKs:
MacOSX10.6.sdk

sh-3.2# xcode-select --print-path
/Developer-3.2.6


--->  Configuring libsdl2
Error: Failed to configure libsdl2, consult 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/work/SDL2-2.0.5/config.log


Lines of likely interest from config.log:

configure:2919: checking for gcc
configure:2946: result: /usr/bin/gcc-4.2
configure:3175: checking for C compiler version
configure:3184: /usr/bin/gcc-4.2 --version >&5
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:3195: $? = 0
configure:3184: /usr/bin/gcc-4.2 -v >&5
Using built-in specs.
Target: i686-apple-darwin10
Configured with: /var/tmp/gcc/gcc-5666.3~6/src/configure --disable-checking 
--enable-werror --prefix=/usr --mandir=/share/man 
--enable-languages=c,objc,c++,obj-c++ 
--program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib 
--build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- 
--host=x86_64-apple-darwin10 --target=i686-apple-darwin10 
--with-gxx-include-dir=/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Apple Inc. build 5666) (dot 3)
configure:3195: $? = 0
configure:3184: /usr/bin/gcc-4.2 -V >&5
gcc-4.2: argument to `-V' is missing
configure:3195: $? = 1
configure:3184: /usr/bin/gcc-4.2 -qversion >&5
i686-apple-darwin10-gcc-4.2.1: no input files
configure:3195: $? = 1
configure:3215: checking whether the C compiler works
configure:3237: /usr/bin/gcc-4.2 -pipe -Os 
-isysroot/Developer-3.2.6/SDKs/MacOSX10.7.sdk -arch x86_64 -arch i386 
-I/opt/local/include -isysroot/Developer-3.2.6/SDKs/MacOSX10.7.sdk 
-L/opt/local/lib -Wl,-headerpad_max_install_names 
-Wl,-syslibroot,/Developer-3.2.6/SDKs/MacOSX10.7.sdk -arch x86_64 -arch i386 
conftest.c  >&5
ld: library not found for -lcrt1.10.6.o
collect2: ld returned 1 exit status
ld: library not found for -lcrt1.10.6.o
collect2: ld returned 1 exit status
fatal error: lipo: can't open input file: 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/work/.tmp/ccWPQ19t.out
 (No such file or directory)
configure:3241: $? = 1
configure:3279: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:3284: error: in 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/work/SDL2-2.0.5':
configure:3286: error: C compiler cannot create executables
See `config.log' for more details


sh-3.2# /Users/rlhamil/bin/vers  # a script of mine that outputs the versions 
of various interesting things that might be relevant
Hardware Version: Mac mini (Mid 2007)
Model Identifier: Macmini2,1
Mac OS X 10.6.8 10K549 (Snow Leopard)
Xcode 3.2.6 DevToolsSupport-1806.0
MacPorts Version: 2.3.4


> On Oct 28, 2016, at 22:05, Ken Cunningham  
> wrote:
> 
> libsdl2 will build without trouble on 10.6.8 if you find a copy of the 10.7 
> SDK and put it like so in /Developer/SDKs/MacOSX10.7.sdk
> 
> Ken
> 
> 
> On 2016-10-28, at 9:58 PM, Richard L. Hamilton wrote:
> 
>> Am I right in thinking that  ffmpeg now requires libsdl2 while it previously 
>> required libsdl?  That causes ffmpeg to fail on 10.6.x, because libsdl2 
>> fails:
>> 
>> Error: org.macports.fetch for port libsdl2 returned: Building libsdl2 
>> requires OS X 10.7 SDK or later
>> Error: Failed to install libsdl2
>> Please see the log file for port libsdl2 for details:
>>   
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libsdl2/libsdl2/main.log
>> Error: The following dependencies were not installed: libsdl2
>> Error: Unable to upgrade port: 1
>> To report a bug, follow the instructions in the guide:
>>   http://guide.macports.org/#project.tickets
>> 
>> ___
>>