No, it's the reverse, it is gnu gcc that fails and Apple gcc that works Attached is the config.log for the failing case of gnu gcc
On Sat, Nov 21, 2015 at 12:05 PM, Ben Gamari <[email protected]> wrote: > George Colpitts <[email protected]> writes: > > > The hq rc3 mac binary build is where I am reporting the problem. > > I also reproduced it on a mac just now on the hq rc3 src build which I > > guess is not surprising. > > > > I believe I encountered this in previous 7.10.3 builds but failed to > report > > it. > > > > Sorry > > > > On Sat, Nov 21, 2015 at 12:07 AM, Carter Schonwald < > > [email protected]> wrote: > > > >> Was this my build or the hq build? > >> On Nov 20, 2015 6:55 PM, "George Colpitts" <[email protected]> > >> wrote: > >> > >>> On MacOS if your path is such that gcc is the gnu gcc rather than > Apple's > >>> gcc then ./configure gives > >>> > >>> checking whether we are cross compiling... configure: error: in > >>> `/Users/gcolpitts/downloads/ghc-7.10.2.20151114': > >>> configure: error: cannot run C compiled programs. > >>> If you meant to cross compile, use `--host'. > >>> See `config.log' for more details > >>> > It's not clear to me why Apple's "GCC" (actually clang, if I'm not > mistaken) doesn't work here. Could you paste config.log somewhere? > > Cheers, > > - Ben > >
config.log
Description: Binary data
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
