<div dir="ltr">Definitely more complicated than I thought. :) <div><br></div><div>It also seems as if Xcode has changed in that I used to be able to install command line tools from Xcode and did. However in Xcode 7.3 Preferences-> Components implies I already have it. <div><br></div><div>I guess the best thing would be for configure to figure all this out and do the right thing. I'm guessing that is not easy and I don't believe it is critical for the release of 8.0. The second best thing to do would be to have the error message suggest two possible workaround/fixes with an explanation that one is for people with full Xcode, the other for people with only XCode command line tools. </div><div><br></div><div>In any case I trust in your judgement and that of other ghc developers with more experience than me to do the right thing. I wish I could be more helpful.</div><div><br></div><div>Cheers</div><div>George</div><div><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Sat, Apr 23, 2016 at 7:49 PM Ben Gamari <<a href="mailto:ben@well-typed.com" target="_blank">ben@well-typed.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">George Colpitts <<a href="mailto:george.colpitts@gmail.com" target="_blank">george.colpitts@gmail.com</a>> writes:<br>
<br>
> The error message should be changed from<br>
><br>
> Workaround: You may want to pass '--with-nm=nm-classic' to<br>
> 'configure'.<br>
><br>
> to<br>
><br>
> Workaround: You may want to pass '--with-nm=$(xcode-select<br>
> -p)/Toolchains/XcodeDefault.xctoolchain/usr/bin/nm-classic' to 'configure'.<br>
><br>
> Once I did that (as documented in <a href="https://ghc.haskell.org/ticket/11744" rel="noreferrer" target="_blank">https://ghc.haskell.org/ticket/11744</a>) I<br>
> was able to do a build<br>
><br>
Hmm, although I just checked on our OS X test box (which has the<br>
command-line tools installed, not full XCode) and it seems that the<br>
/Library/Developer/CommandLineTools/Toolchains directory doesn't exist.<br>
Presumably this is a (rather unfortunate) difference between full XCode<br>
and the command-line package. Do you know whether there is some advice<br>
that we might be able to offer that will work in both cases?<br>
<br>
If not I suspect we should just go with your suggestion; the full-XCode<br>
case is the far more likely of the two.<br>
<br>
Cheers,<br>
<br>
- Ben<br>
</blockquote></div></div></div></div></div>