> 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 think we could fix
>>> the problem by hav
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 think we could fix
>> the problem by having the port blacklist the compilers only when libc++ is
>> in
> 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
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:
>
> $ sudo port install -d sox
Note that this "-d" does nothing. Single-let
On Mar 21 17:26:35, dl...@geeklair.net wrote:
> On Mar 21, 2017, at 5:03 PM, Jan Stary wrote:
> > Looking at the output of port -v -d install sox:
> >
> > DEBUG: compiler clang 77 blacklisted because it matches {clang < 503}
> > DEBUG: compiler clang 77 blacklisted because it matches {clang < 500
IIRC there's also an edge case when something tries to check the compiler
in a fetch step or w/e and the information doesn't exist yet, so all
compilers are "blacklisted" because there are no compilers defined yet,
while the code printing that assumes the compiler list is empty because
blacklisting
On Mar 21, 2017, at 5:03 PM, Jan Stary wrote:
> Looking at the output of port -v -d install sox:
>
> DEBUG: compiler clang 77 blacklisted because it matches {clang < 503}
> DEBUG: compiler clang 77 blacklisted because it matches {clang < 500}
> DEBUG: compiler clang 77 blacklisted because it matc
On Mar 21 14:43:12, allber...@gmail.com wrote:
> On Tue, Mar 21, 2017 at 4:37 AM, Jan Stary wrote:
>
> > Why are they unavailable? The gcc and clang from Xcode work just fine.
>
>
> "Works for random stuff I tried it on" does not guarantee it doesn't throw
> spurious errors or even produce brok
On Tue, Mar 21, 2017 at 4:37 AM, Jan Stary wrote:
> Why are they unavailable? The gcc and clang from Xcode work just fine.
"Works for random stuff I tried it on" does not guarantee it doesn't throw
spurious errors or even produce broken programs in specific cases (which is
to say, most compiler
