[racket-dev] Building HEAD today

From: Greg Hendershott (greghendershott at gmail.com)
Date: Wed Jul 17 16:48:06 EDT 2013

I did my first fetch and build of HEAD today, using the new layout. A
few surprises; I wanted to ask if they're as-expected (at least at
this point in the change to the new approach).

If the short answer is, "Please go away and try again later after
things have settled down" then no worries. :)  OTOH let me know if
there's something I can try on my end that would help.


0. I simply ran `make' from the project's top dir (on OS X in case
that matters).

1. I notice the `racket' command-line binary moved from bin/racket to
racket/bin/racket -- correct?  (Not complaining, don't mind adjusting
my PATH. Just checking it's as-expected.)

2. When I run bin/racket/racket, it says

"Welcome to Racket v5.3.900.7."

Um, aren't we past 5.3.5? Did I do something wrong?

3. During build I got this error:

...
raco setup: 0 running: <pkgs>/redex-doc/redex/redex.scrbl
raco setup: 1 running: <pkgs>/racket-index/scribblings/main/user/release.scrbl
raco setup: error running: (lib scribblings/main/user/release.scrbl)
string<?: contract violation
  expected: string?
  given: 'p
  argument position: 1st
  other arguments...:
   'p
  context...:
   /Users/greg/src/plt/racket/racket/lib/collects/racket/private/sort.rkt:213:0:
sort
   /Users/greg/src/plt/racket/pkgs/racket-pkgs/racket-index/scribblings/main/private/release.rkt:43:0:
release-items
   /Users/greg/src/plt/racket/pkgs/racket-pkgs/racket-index/scribblings/main/user/release.scrbl:
[running body]
   /Users/greg/src/plt/racket/pkgs/racket-pkgs/racket-index/setup/scribble.rkt:766:0:
load-doc/ensure-prefix
   /Users/greg/src/plt/racket/pkgs/racket-pkgs/racket-index/setup/scribble.rkt:999:13
   /Users/greg/src/plt/racket/racket/lib/collects/setup/parallel-do.rkt:420:20:
loop
string<?: contract violation
  expected: string?
  given: 'p
  argument position: 1st
  other arguments...:
   'p
  context...:
   /Users/greg/src/plt/racket/racket/lib/collects/racket/private/sort.rkt:213:0:
sort
   /Users/greg/src/plt/racket/pkgs/racket-pkgs/racket-index/scribblings/main/private/release.rkt:43:0:
release-items
   /Users/greg/src/plt/racket/pkgs/racket-pkgs/racket-index/scribblings/main/user/release.scrbl:
[running body]
   /Users/greg/src/plt/racket/pkgs/racket-pkgs/racket-index/setup/scribble.rkt:766:0:
load-doc/ensure-prefix
   /Users/greg/src/plt/racket/pkgs/racket-pkgs/racket-index/setup/scribble.rkt:999:13
   /Users/greg/src/plt/racket/racket/lib/collects/setup/parallel-do.rkt:420:20:
loop
raco setup: 7 running: <pkgs>/scribble-doc/scribblings/scribble/scribble.scrbl
raco setup: 1 running: <pkgs>/racket-doc/scribblings/scheme/scheme.scrbl
...

4. I got many "re-rendering" lines:

raco setup: 7 rendering: <pkgs>/racket-index/scribblings/main/search.scrbl
raco setup: 7 re-rendering:
<pkgs>/racket-doc/scribblings/reference/reference.scrbl
raco setup: 6 re-rendering: <pkgs>/algol60/algol60.scrbl
raco setup: 5 re-rendering: <pkgs>/games/cards/cards.scrbl
raco setup: 4 re-rendering:
<pkgs>/web-server-doc/web-server/scribblings/tutorial/continue.scrbl
raco setup: 3 re-rendering: <pkgs>/datalog/scribblings/datalog.scrbl
raco setup: 2 re-rendering: <pkgs>/db-doc/db/scribblings/db.scrbl
raco setup: 1 re-rendering: <pkgs>/eopl/eopl.scrbl
raco setup: 0 re-rendering: <pkgs>/racket-doc/scribblings/foreign/foreign.scrbl
raco setup: 6 re-rendering:
<pkgs>/future-visualizer/future-visualizer/scribblings/future-visualizer.scrbl
raco setup: 5 re-rendering: <pkgs>/games/scribblings/games.scrbl
raco setup: 6 re-rendering:
<pkgs>/racket-doc/scribblings/getting-started/getting-started.scrbl
raco setup: 3 re-rendering: <pkgs>/htdp-doc/graphics/scribblings/graphics.scrbl
raco setup: 1 re-rendering: <pkgs>/honu/scribblings/honu.scrbl
raco setup: 6 re-rendering: <pkgs>/htdp-doc/htdp/htdp.scrbl
raco setup: 1 re-rendering: <pkgs>/images/scribblings/images.scrbl
raco setup: 3 re-rendering: <pkgs>/lazy/lazy.scrbl
raco setup: 2 re-rendering:
<pkgs>/racket-index/scribblings/main/user/local-redirect.scrbl
raco setup: 6 re-rendering: <pkgs>/racket-doc/scribblings/more/more.scrbl
raco setup: 5 re-rendering: <pkgs>/pict-doc/pict/scribblings/pict.scrbl
raco setup: 3 re-rendering: <pkgs>/racket-doc/pkg/scribblings/pkg.scrbl
raco setup: 6 re-rendering: <pkgs>/plai/scribblings/plai.scrbl
raco setup: 4 re-rendering: <pkgs>/racket-doc/planet/planet.scrbl
raco setup: 0 re-rendering: <pkgs>/plot/scribblings/plot.scrbl
raco setup: 3 re-rendering: <pkgs>/drracket/setup/plt-installer.scrbl
raco setup: 4 re-rendering: <pkgs>/preprocessor/scribblings/preprocessor.scrbl
raco setup: 6 re-rendering: <pkgs>/slideshow-doc/scribblings/quick/quick.scrbl
raco setup: 3 re-rendering: <pkgs>/r5rs-doc/r5rs/r5rs.scrbl
raco setup: 3 re-rendering: <pkgs>/r6rs-doc/r6rs/scribblings/r6rs.scrbl
raco setup: 4 re-rendering: <pkgs>/racklog/racklog.scrbl
raco setup: 6 re-rendering:
<pkgs>/racket-doc/rackunit/scribblings/rackunit.scrbl
raco setup: 3 re-rendering: <pkgs>/racket-doc/scribblings/raco/raco.scrbl
raco setup: 4 re-rendering: <pkgs>/redex-doc/redex/redex.scrbl
raco setup: 2 re-rendering: <pkgs>/racket-index/scribblings/main/release.scrbl
raco setup: 2 re-rendering: <pkgs>/racket-doc/scribblings/scheme/scheme.scrbl
raco setup: 6 re-rendering:
<pkgs>/scribble-doc/scribblings/scribble/scribble.scrbl
raco setup: 5 re-rendering:
<pkgs>/racket-doc/scriblib/scribblings/scriblib.scrbl
raco setup: 2 re-rendering:
<pkgs>/racket-index/scribblings/main/user/search.scrbl
raco setup: 5 re-rendering: <pkgs>/sgl/scribblings/sgl.scrbl
raco setup: 3 re-rendering:
<pkgs>/slideshow-doc/scribblings/slideshow/slideshow.scrbl
raco setup: 3 re-rendering: <pkgs>/srfi-doc/srfi/scribblings/srfi.scrbl
raco setup: 3 re-rendering: <pkgs>/racket-index/scribblings/main/start.scrbl
raco setup: 3 re-rendering:
<pkgs>/racket-index/scribblings/main/user/start.scrbl
raco setup: 3 re-rendering: <pkgs>/racket-doc/scribblings/style/style.scrbl
raco setup: 5 re-rendering: <pkgs>/swindle/swindle.scrbl
raco setup: 5 re-rendering: <pkgs>/racket-doc/syntax/scribblings/syntax.scrbl
raco setup: 3 re-rendering:
<pkgs>/syntax-color-doc/syntax-color/syntax-color.scrbl
raco setup: 3 re-rendering: <pkgs>/htdp-doc/teachpack/teachpack.scrbl
raco setup: 2 re-rendering: <pkgs>/drracket/scribblings/tools/tools.scrbl
raco setup: 6 re-rendering:
<pkgs>/typed-racket-doc/typed-racket/scribblings/ts-guide.scrbl
raco setup: 6 re-rendering:
<pkgs>/typed-racket-doc/typed-racket/scribblings/ts-reference.scrbl
raco setup: 5 re-rendering: <pkgs>/unstable/scribblings/unstable.scrbl
raco setup: 1 re-rendering: <pkgs>/unstable/scribblings/gui/unstable-gui.scrbl
raco setup: 2 re-rendering:
<pkgs>/web-server-doc/web-server/scribblings/web-server.scrbl
raco setup: 1 re-rendering:
<pkgs>/web-server-doc/web-server/scribblings/web-server-internal.scrbl
raco setup: 6 re-rendering: <pkgs>/xrepl-doc/xrepl/xrepl.scrbl
raco setup: 2 re-rendering:
<pkgs>/racket-index/scribblings/main/local-redirect.scrbl
raco setup: 6 re-rendering: <pkgs>/racket-index/scribblings/main/search.scrbl

Is this normal (or normal for the time being, and OK to ignore)?

5. At the end, I got many, many lines about dependency checking for
packages with dev links:

raco setup: found undeclared dependency:
raco setup:   mode: run
raco setup:   for package: "frog"
raco setup:   on package: core
raco setup:   dependent source: config_rkt.zo
raco setup:   used module: (lib "racket/syntax.rkt")
raco setup: found undeclared dependency:
raco setup:   mode: run
raco setup:   for package: "frog"
raco setup:   on package: core
raco setup:   dependent source: config_rkt.zo
raco setup:   used module: (lib "racket/main.rkt")
raco setup: found undeclared dependency:
raco setup:   mode: run
raco setup:   for package: "frog"
raco setup:   on package: core
raco setup:   dependent source: config_rkt.zo
raco setup:   used module: (lib "racket/runtime-config.rkt")
raco setup: found undeclared dependency:
raco setup:   mode: build
raco setup:   for package: "frog"
raco setup:   on package: core
raco setup:   dependent source: config_rkt.dep
raco setup:   used module: (lib "racket/match/parse.rkt")
... many more like this ...

Is this normal (or normal for the time being, and OK to ignore)?

6. The very end of the build looked like this:

raco setup: found undeclared dependency:
raco setup:   mode: run
raco setup:   for package: "frog"
raco setup:   on package: core
raco setup:   dependent source: frog_rkt.zo
raco setup:   used module: (lib "frog/frog")
combine-relative-elements: relative path escapes collection: (up
#<path:info.rkt>) relative to (lib "frog" "frog")
  context...:
   /Users/greg/src/plt/racket/racket/lib/collects/setup/private/pkg-deps.rkt:292:10:
for-loop
   /Users/greg/src/plt/racket/racket/lib/collects/setup/private/pkg-deps.rkt:292:10:
for-loop
   /Users/greg/src/plt/racket/racket/lib/collects/setup/private/pkg-deps.rkt:287:6:
loop
   /Users/greg/src/plt/racket/racket/lib/collects/racket/private/map.rkt:48:13:
for-each
   /Users/greg/src/plt/racket/racket/lib/collects/setup/private/pkg-deps.rkt:355:8:
for-loop
   /Users/greg/src/plt/racket/racket/lib/collects/setup/private/pkg-deps.rkt:344:2:
for-loop
   /Users/greg/src/plt/racket/racket/lib/collects/setup/private/pkg-deps.rkt:22:0:
check-package-dependencies
   /Users/greg/src/plt/racket/racket/lib/collects/setup/setup-unit.rkt:1599:2:
do-check-package-dependencies
   /Users/greg/src/plt/racket/racket/lib/collects/setup/setup-go.rkt:
[running body]
   /Users/greg/src/plt/racket/racket/lib/collects/setup/main.rkt: [running body]
   /Users/greg/src/plt/racket/racket/lib/collects/raco/main.rkt: [running body]
make[1]: *** [plain-in-place] Error 1
make: *** [in-place] Error 2


7. After the build, Git prompts me about a new untracked file:

git status
# On branch master
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#    pkgs/racket-pkgs/racket-test/tests/racket/benchmarks/places/place-benchmark13740909571374090957150.rkt
nothing added to commit but untracked files present (use "git add" to track)

If I want to stay in clean sync with upstream, should I .gitignore
that or add it?

Thanks.

Posted on the dev mailing list.