<div dir="ltr"><div>Okay, some teething problems.<br><br>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.<br><br></div><div>I went back to my main installation, removed all planet packages, and re-ran. <br><br></div><div>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'. <br><br></div><div>er... big mistake.<br><br></div><div>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:<br><br>standard-module-name-resolver: collection not found<br> for module path: (submod at-exp reader)<br> collection: "at-exp"<br> in collection directories:<br> /Users/clements/Library/Racket/development/collects<br> /Users/clements/plt2/racket/collects<br> ... [177 additional linked and package directories]<br> context...:<br> show-collection-err<br> standard-module-name-resolver<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:353:23<br> /Users/clements/plt2/racket/collects/syntax/modcode.rkt:62:2: reader<br> /Users/clements/plt2/racket/collects/syntax/modcode.rkt:264:5: compile-one<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:315:0: compile-zo*<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:519:26<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:511:42<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:476:0: maybe-compile-zo<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:591:2: do-check<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:706:4: compilation-manager-load-handler<br> standard-module-name-resolver<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:315:0: compile-zo*<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:519:26<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:511:42<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:476:0: maybe-compile-zo...<br><br></div><div>... but there were some other problems, too. Like this one:<br><br>raco setup: 3 making: <pkgs>/plot-gui-lib/plot/typed/private<br>ffi-lib: couldn't open "libintl.8.dylib" (dlopen(libintl.8.dylib, 6): image not found)<br> context...:<br> /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw/unsafe/glib.rkt: [running body]<br> /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw/unsafe/pango.rkt: [traversing imports]<br> /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw/private/font.rkt: [traversing imports]<br> /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw/private/contract.rkt: [traversing imports]<br> /Users/clements/plt2/racket/share/pkgs/draw-lib/racket/draw.rkt: [traversing imports]<br> /Users/clements/plt2/racket/share/pkgs/plot-lib/plot/private/common/contract.rkt: [traversing imports]<br> /Users/clements/plt2/racket/share/pkgs/typed-racket-lib/typed-racket/tc-setup.rkt:39:0: tc-setup<br> /Users/clements/plt2/racket/share/pkgs/typed-racket-lib/typed-racket/typed-racket.rkt:18:4<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:315:0: compile-zo*<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:519:26<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:511:42<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:476:0: maybe-compile-zo<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:591:2: do-check<br> /Users/clements/plt2/racket/collects/compiler/cm.rkt:706:4: compilation-manager-load-handler<br> standard-module-name-resolver<br> /Users/clements/plt2/racket/collects/racket/require-transform.rkt:266:2: expand-import...<br><br></div>I think I may just try a fresh checkout, sigh.<br><div><br></div>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.<br><br>John<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 4, 2014 at 8:32 AM, Sam Tobin-Hochstadt <span dir="ltr"><<a href="mailto:samth@cs.indiana.edu" target="_blank">samth@cs.indiana.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><br><div class="gmail_quote"><span class="">On Thu Dec 04 2014 at 11:27:45 AM Matthias Felleisen <<a href="mailto:matthias@ccs.neu.edu" target="_blank">matthias@ccs.neu.edu</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br> For those of you who have my level of experience with such things,<br> here is what Sam's phrase "I *highly* recommend creating a new clone<br> of the repository, and re-running `make`." means, for your value of<br> the name 'plt2':<br> <br> $ git clone git:plt plt2<br> $ cd plt2/<br> $ git submodule init<br> $ git submodule update<br> $ make<br></blockquote><div><br></div></span><div>Exactly.</div><div><br></div><div>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://<a href="http://git.racket-lang.org/plt.git" target="_blank">git.racket-lang.org/plt.git`</a>. </div><div><br></div><div>Also, the submodule steps are needed on Windows and OS X, but not on Linux (which is why I forgot to mention them). </div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Sam</div></font></span></div> <br>_________________________<br> Racket Developers list:<br> <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br> <br></blockquote></div><br></div>