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 removed all of them? And I think another if something tries to
look up Xcode-specific information but the xcode portgroup hasn't been
initialized?
On Tue, Mar 21, 2017 at 5:26 PM, Daniel J. Luke <dl...@geeklair.net> wrote:
> On Mar 21, 2017, at 5:03 PM, Jan Stary <h...@stare.cz> 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 matches {clang < 500}
> > Warning: All compilers are either blacklisted or unavailable; defaulting
> to first fallback option
> > Warning: All compilers are either blacklisted or unavailable; defaulting
> to first fallback option
> >
> > That does not look like a specific reason why clang fails to build sox
> properly.
>
> you trimmed the relevant information - that's almost certainly coming from
> a port that sox requires and not sox itself.
>
> Most of the ports that use compiler blacklist have a comment in the
> portfile explaining why (most people don't care, though ;-) ).
>
> --
> Daniel J. Luke
>
>
>
>
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
