Definitely more complicated than I thought. :) 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.
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. 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. Cheers George On Sat, Apr 23, 2016 at 7:49 PM Ben Gamari <b...@well-typed.com> wrote: > George Colpitts <george.colpi...@gmail.com> writes: > > > The error message should be changed from > > > > Workaround: You may want to pass '--with-nm=nm-classic' to > > 'configure'. > > > > to > > > > Workaround: You may want to pass '--with-nm=$(xcode-select > > -p)/Toolchains/XcodeDefault.xctoolchain/usr/bin/nm-classic' to > 'configure'. > > > > Once I did that (as documented in https://ghc.haskell.org/ticket/11744) > I > > was able to do a build > > > Hmm, although I just checked on our OS X test box (which has the > command-line tools installed, not full XCode) and it seems that the > /Library/Developer/CommandLineTools/Toolchains directory doesn't exist. > Presumably this is a (rather unfortunate) difference between full XCode > and the command-line package. Do you know whether there is some advice > that we might be able to offer that will work in both cases? > > If not I suspect we should just go with your suggestion; the full-XCode > case is the far more likely of the two. > > Cheers, > > - Ben >
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
