Re: portindex fails due to portfile parsing

> On Mar 19, 2018, at 4:34 PM, Ryan Schmidt wrote: > > Ok, I've figured out that the reason why I'm not seeing the "Unable to > determine location of a macOS SDK" message is that I was running MacPorts > 2.4.2 and the message is new for MacPorts 2.5. MacPorts 2.5

Re: drop opencore-amr

On the ffmpeg side, see https://trac.macports.org/ticket/33503. If you want to obsolete the port and drop support for it from the dependents, I think that would be fine. > On Dec 31, 2017, at 8:58 AM, Jan Stary wrote: > > https://github.com/macports/macports-ports/pull/1182 >

Re: building from source with libc++

libX11 has no C++ code, so the error probably has nothing to do with the C++ library chosen. Please do open a ticket with whatever relevant data you can provide. > On Mar 24, 2017, at 14:24, Ryan Schmidt wrote: > > > On Mar 24, 2017, at 14:48, db

Re: all compilers blacklisted or unavailable

> On Mar 22, 2017, at 09:51, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Mar 22, 2017, at 10:27, Jeremy Huddleston Sequoia wrote: > >>> This is clever, but I don't like that it causes MacPorts to print an >>> inaccurate warning that clearly

Re: Using an older port to make another port

You could just locally revert the offensive change to libarchive until your issue is addressed. --Jeremy > On Mar 4, 2017, at 13:18, Michael wrote: > > How do I use an older port when making another one? > > I followed the instructions for working with an older version