On Thu, Dec 4, 2014 at 12:50 PM, John Clements <johnbcleme...@gmail.com> wrote: > Okay, some teething problems. > > First time around, it finished way too fast. The problem seemed to be that > it had an error in compiling a planet package... ah, I see, there was no > 'at-exp-lib' installed? Presumably this is because planet packages don't > declare pkg dependencies? Anyhow, this aborted the whole compilation. > > I went back to my main installation, removed all planet packages, and > re-ran. > > It was running great, and about 30% done, when I decided that hyperthreading > was not getting me anything, and that I wanted to run with 4 cpus rather > than 8. So I hit Ctrl-C, and re-ran 'make'. > > er... big mistake. > > The next time through, hundreds of packages failed to compile. In general, > the most "popular" error was one about not having the at-exp collection:
Ok, that's good to know. I'll look into what's happening there. > standard-module-name-resolver: collection not found > for module path: (submod at-exp reader) > collection: "at-exp" > in collection directories: > /Users/clements/Library/Racket/development/collects > /Users/clements/plt2/racket/collects > ... [177 additional linked and package directories] > context...: > show-collection-err > standard-module-name-resolver > /Users/clements/plt2/racket/collects/compiler/cm.rkt:353:23 > /Users/clements/plt2/racket/collects/syntax/modcode.rkt:62:2: reader > /Users/clements/plt2/racket/collects/syntax/modcode.rkt:264:5: > compile-one > /Users/clements/plt2/racket/collects/compiler/cm.rkt:315:0: compile-zo* > /Users/clements/plt2/racket/collects/compiler/cm.rkt:519:26 > /Users/clements/plt2/racket/collects/compiler/cm.rkt:511:42 > /Users/clements/plt2/racket/collects/compiler/cm.rkt:476:0: > maybe-compile-zo > /Users/clements/plt2/racket/collects/compiler/cm.rkt:591:2: do-check > /Users/clements/plt2/racket/collects/compiler/cm.rkt:706:4: > compilation-manager-load-handler > standard-module-name-resolver > /Users/clements/plt2/racket/collects/compiler/cm.rkt:315:0: compile-zo* > /Users/clements/plt2/racket/collects/compiler/cm.rkt:519:26 > /Users/clements/plt2/racket/collects/compiler/cm.rkt:511:42 > /Users/clements/plt2/racket/collects/compiler/cm.rkt:476:0: > maybe-compile-zo... > > ... but there were some other problems, too. Like this one: > > raco setup: 3 making: <pkgs>/plot-gui-lib/plot/typed/private > ffi-lib: couldn't open "libintl.8.dylib" (dlopen(libintl.8.dylib, 6): image > not found) > context...: > > /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw/unsafe/glib.rkt: > [running body] > > /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw/unsafe/pango.rkt: > [traversing imports] > > /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw/private/font.rkt: > [traversing imports] > > /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw/private/contract.rkt: > [traversing imports] > /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw.rkt: > [traversing imports] > > /Users/clements/plt2/racket/share/pkgs/plot-lib/plot/private/common/contract.rkt: > [traversing imports] > > /Users/clements/plt2/racket/share/pkgs/typed-racket-lib/typed-racket/tc-setup.rkt:39:0: > tc-setup > > /Users/clements/plt2/racket/share/pkgs/typed-racket-lib/typed-racket/typed-racket.rkt:18:4 > /Users/clements/plt2/racket/collects/compiler/cm.rkt:315:0: compile-zo* > /Users/clements/plt2/racket/collects/compiler/cm.rkt:519:26 > /Users/clements/plt2/racket/collects/compiler/cm.rkt:511:42 > /Users/clements/plt2/racket/collects/compiler/cm.rkt:476:0: > maybe-compile-zo > /Users/clements/plt2/racket/collects/compiler/cm.rkt:591:2: do-check > /Users/clements/plt2/racket/collects/compiler/cm.rkt:706:4: > compilation-manager-load-handler > standard-module-name-resolver > /Users/clements/plt2/racket/collects/racket/require-transform.rkt:266:2: > expand-import... > > I think I may just try a fresh checkout, sigh. > > All of this is probably JFYI ... I know, you shouldn't abort a make. In the > past, though, we've been pretty robust in this department. I think robustness in this area is important, and we'll be back there soon, hopefully. You shouldn't have to worry about aborting make. Sam > > John > > > On Thu, Dec 4, 2014 at 8:32 AM, Sam Tobin-Hochstadt <sa...@cs.indiana.edu> > wrote: >> >> >> >> On Thu Dec 04 2014 at 11:27:45 AM Matthias Felleisen >> <matth...@ccs.neu.edu> wrote: >>> >>> >>> For those of you who have my level of experience with such things, >>> here is what Sam's phrase "I *highly* recommend creating a new clone >>> of the repository, and re-running `make`." means, for your value of >>> the name 'plt2': >>> >>> $ git clone git:plt plt2 >>> $ cd plt2/ >>> $ git submodule init >>> $ git submodule update >>> $ make >> >> >> Exactly. >> >> Note that the `git:plt` repository that Matthias uses here is an alias for >> `git.racket-lang.org:plt`. If you're not a committer, you'll want to use >> `git://git.racket-lang.org/plt.git`. >> >> Also, the submodule steps are needed on Windows and OS X, but not on Linux >> (which is why I forgot to mention them). >> >> Sam >> >> _________________________ >> Racket Developers list: >> http://lists.racket-lang.org/dev >> > _________________________ Racket Developers list: http://lists.racket-lang.org/dev
