fixed up the sphinx confusion... seems we need the python 2.7 sphinx installed? (or at least, it wasn't checking sphinx correctly to handle the version supported in the python 3 series?!)
On Sat, Apr 23, 2016 at 12:23 PM, Carter Schonwald < [email protected]> wrote: > err, i mean, sphinx was giving > checking for version of sphinx-build... Sphinx (sphinx-build) 1.4.1 > ./configure: line 9698: test: Sphinx (sphinx-build) 1: integer expression > expected > > which version of sphinx for which python are we supposed to use? > > On Sat, Apr 23, 2016 at 12:18 PM, Carter Schonwald < > [email protected]> wrote: > >> looks like i dont have dblatex setup on that build machine, fixing that >> now! (slightly trick on mac) >> >> On Sat, Apr 23, 2016 at 11:51 AM, Carter Schonwald < >> [email protected]> wrote: >> >>> i'm running into some confusions with getting docs built correclty / not >>> generating the pdfs and html assets i expect, i'll share an updated sha etc >>> when i track that down >>> >>> On Sat, Apr 23, 2016 at 9:52 AM, George Colpitts < >>> [email protected]> wrote: >>> >>>> retrying with >>>> >>>> ./configure --with-nm=$(xcode-select >>>> -p)/Toolchains/XcodeDefault.xctoolchain/usr/bin/nm-classic >>>> >>>> On Sat, Apr 23, 2016 at 10:49 AM George Colpitts < >>>> [email protected]> wrote: >>>> >>>>> Thanks Carter. I'm not so concerned with obtaining a working build. >>>>> I'd like to be able to build with the Apple toolchain. I assume there are >>>>> other developers who feel the same. >>>>> >>>>> Can you elaborate on the "path to nm classic is wrong" ? >>>>> >>>>> Cheers >>>>> George >>>>> >>>>> On Sat, Apr 23, 2016 at 10:42 AM Carter Schonwald < >>>>> [email protected]> wrote: >>>>> >>>>>> I've a working build I'll circulate >>>>>> Also that path to nm classic is wrong. >>>>>> >>>>>> >>>>>> On Saturday, April 23, 2016, George Colpitts < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> I'm having problems using the Apple toolchain to build this on Mac >>>>>>> OS. Has anybody succeeded with the Apple toolchain? >>>>>>> >>>>>>> First I get the error: >>>>>>> >>>>>>> broken 'nm' detected, see https://ghc.haskell.org/ticket/11744. >>>>>>> Workaround: You may want to pass '--with-nm=nm-classic' to >>>>>>> 'configure'. >>>>>>> >>>>>>> but after I try that workaround I get: >>>>>>> >>>>>>> inplace/bin/deriveConstants --gen-header -o >>>>>>> includes/dist-derivedconstants/header/DerivedConstants.h --tmpdir >>>>>>> includes/dist-derivedconstants/header/ --gcc-program "/usr/bin/gcc" >>>>>>> --gcc-flag -Wall --gcc-flag -Wno-unknown-pragmas --gcc-flag -m64 >>>>>>> --gcc-flag >>>>>>> -fno-stack-protector --gcc-flag -Iincludes --gcc-flag -Iincludes/dist >>>>>>> --gcc-flag -Iincludes/dist-derivedconstants/header --gcc-flag >>>>>>> -Iincludes/dist-ghcconstants/header --gcc-flag -Irts --gcc-flag -fcommon >>>>>>> --nm-program "nm-classic" --target-os "darwin" >>>>>>> deriveConstants: nm-classic: readCreateProcess: >>>>>>> runInteractiveProcess: exec: does not exist (No such file or directory) >>>>>>> make[1]: *** >>>>>>> [includes/dist-derivedconstants/header/DerivedConstants.h] Error 1 >>>>>>> make[1]: *** Waiting for unfinished jobs.... >>>>>>> make: *** [all] Error 2 >>>>>>> >>>>>>> Thanks >>>>>>> George >>>>>>> >>>>>>> On Fri, Apr 22, 2016 at 11:27 AM Ben Gamari <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> tl;dr: If you would like to produce a binary distribution for GHC >>>>>>>> 8.0.1-rc4 then let us know, grab the source distribution and >>>>>>>> start building. The binary distributions will be all >>>>>>>> released one >>>>>>>> week from today. >>>>>>>> >>>>>>>> Hello GHC packagers, >>>>>>>> >>>>>>>> I am happy to announce the release of the 8.0.1-rc4 source >>>>>>>> distribution >>>>>>>> to binary packagers. This release should resolve all of the issues >>>>>>>> noted >>>>>>>> in the release candidate 3 announcement. You will find the usual >>>>>>>> artifacts at >>>>>>>> >>>>>>>> http://downloads.haskell.org/~ghc/8.0.1-rc4/ >>>>>>>> >>>>>>>> For this candidate we are again following our new release policy >>>>>>>> [1], >>>>>>>> with a one-week delay between the release of the source and binary >>>>>>>> distributions. The goal of this policy is to give all platforms the >>>>>>>> opportunity for support from the first day of a release. >>>>>>>> >>>>>>>> If all of the expected binary releases are submitted before the >>>>>>>> week-long delay has elapsed, we will move forward with the release >>>>>>>> of >>>>>>>> the binaries on an accelerated schedule. It would be appreciated if >>>>>>>> you >>>>>>>> could reply to this message confirming that you intend to offer a >>>>>>>> binary >>>>>>>> distribution this release. >>>>>>>> >>>>>>>> Otherwise, let either Austin or I know if you have any trouble >>>>>>>> building >>>>>>>> your distribution. I have yet to push the ghc-8.0.1-rc4 tag in case >>>>>>>> we >>>>>>>> encounter unexpected issues but all of my builds with this tarball >>>>>>>> thusfar have gone quite well. >>>>>>>> >>>>>>>> Good luck and thanks for all of your work! >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> - Ben >>>>>>>> >>>>>>>> >>>>>>>> [1] >>>>>>>> https://mail.haskell.org/pipermail/ghc-devs/2016-March/011546.html >>>>>>>> _______________________________________________ >>>>>>>> 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
