> 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 considers it an
> error when
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
> Is anyone using o
> On Sep 14, 2017, at 01:48, Chris Jones wrote:
>
> Hi,
>
> On 14/09/17 09:34, Mojca Miklavec wrote:
>> On 14 September 2017 at 10:10, Chris Jones wrote:
>>>
>>> Update to Sierra, it will save you most trouble in the long run.
>>> No need at all to go to a store to get it done though, just do
+mcalhoun
Marcus maintains that variant since I don't have the bandwidth to give it the
requisite testing.
Marcus, you might also consider installing the stdc++ headers with the libgcc
port and updating the dependency here to libgcc/libgcc-devel.
> On Sep 6, 2017, at 09:52, Ken Cunningham
>
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 wrote:
>
>> On 24 Mar 2017, at 19:23, Ryan S
> On Mar 22, 2017, at 09:51, Ryan Schmidt 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 causes user confusion. I
> On Mar 22, 2017, at 03:51, Ryan Schmidt wrote:
>
> Jeremy, I'm Cc'ing you for input on wavpack; see the last few paragraphs.
>
>
> On Mar 21, 2017, at 03:37, Jan Stary wrote:
>
>> This is MacPorts 2.4.1 on MacOSX 10.6.8.
>> A build of audio/sox starts with the following warning:
>>
>> $ su
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 of libarchive.
> Going
I'd expect that to have worked. Are you sure your $PATH is configured
correctly after the reinstall. You can check /var/log/install.log to see if
anything was skipped (and why). If it is indeed an issue with the previous
install still being registered, you can use `pkgutil --packages` to show
What version of ibtool?
Can you please take a sysdiagnose focused on ibtool while it's compiling and
file a radar?
> On Nov 22, 2016, at 07:56, Rainer Müller wrote:
>
> On 2016-11-22 16:20, Eric A. Borisch wrote:
>> Trying to upgrade MacVim on my 10.10.5 box hangs on this command:
>>
>> syste
10 matches
Mail list logo
