Yes it does. On Mon, Apr 11, 2016 at 7:36 PM Carter Schonwald <[email protected]> wrote:
> George: In the mean time does my build work on your machine? > On Apr 11, 2016 5:57 PM, "George Colpitts" <[email protected]> > wrote: > >> Thanks Ben, none of this is obvious to me :) I just read the doc which >> doesn't mention distclean or rebuild >> which I have never had to do on earlier source distributions >> >> . I did a make distclean, then a configure, then a make -j5 and got the >> same error. by rebuild do you mean do it again starting from scratch? >> >> I did google the error, i.e. 'Haskell "_stg_sel_17_upd_info" ' and found >> that a few people have encountered this this month. Most importantly it led >> me to https://ghc.haskell.org/trac/ghc/ticket/11155#comment:10 : >> >> Changed 2 days ago by wereHamster >> ↳ Reply >> Ran into this trying to build HEAD today on Mac OS X 10.11.3. But a >> slightly different message: >> >> Warning: -rtsopts and -with-rtsopts have no effect with -no-hs-main. >> Call hs_init_ghc() from your main() function to set these options. >> Undefined symbols for architecture x86_64: >> "_stg_sel_17_upd_info", referenced from: >> _s1xPf_info in UI.dyn_o >> _s1xQA_info in UI.dyn_o >> _s1xZU_info in UI.dyn_o >> _s1y0r_info in UI.dyn_o >> ld: symbol(s) not found for architecture x86_64 >> clang: error: linker command failed with exit code 1 (use -v to see >> invocation) >> `gcc' failed in phase `Linker'. (Exit code: 1) >> make[1]: *** [ghc/stage2/build/tmp/ghc-stage2] Error 1 >> make: *** [all] Error 2 >> >> Should I reopen 11155 or open a new ticket? >> >> Thanks >> George >> >> >> >> On Mon, Apr 11, 2016 at 9:33 AM Ben Gamari <[email protected]> wrote: >> >>> George Colpitts <[email protected]> writes: >>> >>> > This fails for me with the following error; I'm using the latest >>> macOS and >>> > Xcode. >>> > >>> Hmm, this is very odd. Unfortunately due to firewall issues I don't have >>> reliable access to our OS X box, so I was unable to test this particular >>> tarball, but a few days ago I was able to build without any trouble. >>> >>> Have you checked the obvious things (e.g. distclean, rebuild, etc.)? >>> >>> Cheers, >>> >>> - Ben >>> >>> >> _______________________________________________ >> ghc-devs mailing list >> [email protected] >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >> >>
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
