Re: [racket-dev] segfault during make
Do you have the latest images-doc and/or gui-lib packages? Recently, there was a problem with the images documentation where it tried to use `racket/gui` at document-build time. At the same time, there was also a problem in `racket/gui` that could cause a crash (mainly on Mac OS X) after `racket/gui` was used during documentation-build time. Both of those problems have been fixed. At Tue, 06 Jan 2015 22:14:53 +, Spencer Florence wrote: Hey all, When I try to run `make` on the current head the build segfaults while making the documentation. The last few lines of the output are: raco setup: 2 rendering: pkgs/pfds/pfds/scribblings/functional-data-structures.scrbl raco setup: 1 rendering: pkgs/future-visualizer/future-visualizer/scribblings/future-visualizer.scrbl raco setup: 1 rendering: pkgs/games/scribblings/games.scrbl raco setup: 1 rendering: pkgs/racket-doc/scribblings/getting-started/getting-started.scrbl raco setup: 1 rendering: pkgs/games/gl-board-game/gl-board-game.scrbl raco setup: 1 rendering: pkgs/htdp-doc/graphics/scribblings/graphics.scrbl raco setup: 1 rendering: pkgs/gui-doc/scribblings/gui/gui.scrbl raco setup: 0 rendering: pkgs/racket-doc/help/help.scrbl raco setup: 0 rendering: pkgs/htdp-doc/htdp/htdp.scrbl raco setup: 0 rendering: pkgs/htdp-doc/scribblings/htdp-langs/htdp-langs.scrbl raco setup: 3 rendering: pkgs/html-doc/html/html.scrbl raco setup: 3 rendering: pkgs/images-doc/images/scribblings/images.scrbl raco setup: 1 rendering: pkgs/racket-doc/scribblings/inside/inside.scrbl raco setup: 1 rendering: pkgs/racket-doc/json/json.scrbl raco setup: 1 rendering: pkgs/lazy/lazy.scrbl raco setup: 1 rendering: pkgs/macro-debugger/macro-debugger/macro-debugger.scrbl raco setup: 0 rendering: pkgs/make/make.scrbl raco setup: 0 rendering: pkgs/math-doc/math/scribblings/math.scrbl raco setup: 1 rendering: pkgs/racket-doc/scribblings/more/more.scrbl raco setup: 1 rendering: pkgs/gui-doc/mrlib/scribblings/mrlib.scrbl raco setup: 1 rendering: pkgs/mysterx/scribblings/mysterx.scrbl raco setup: 1 rendering: pkgs/mzcom/mzcom.scrbl raco setup: 1 rendering: pkgs/compatibility-doc/mzlib/scribblings/mzlib.scrbl raco setup: 1 rendering: pkgs/mzscheme-doc/mzscheme/mzscheme.scrbl raco setup: 1 rendering: pkgs/net-doc/net/scribblings/net.scrbl raco setup: 1 rendering: pkgs/racket-doc/openssl/openssl.scrbl raco setup: 1 rendering: pkgs/optimization-coach/optimization-coach/scribblings/optimization-coach.scrb l raco setup: 1 rendering: pkgs/parser-tools-doc/parser-tools/parser-tools.scrbl raco setup: 1 rendering: pkgs/pict-doc/pict/scribblings/pict.scrbl raco setup: 3 rendering: pkgs/pict-snip-doc/scribblings/pict-snip/pict-snip.scrbl make[1]: *** [plain-in-place] Segmentation fault: 11 I'm on OSX 10.10.1. Anyone know whats going on/how to debug this? --spencer _ Racket Developers list: http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
[racket-dev] segfault during make
Hey all, When I try to run `make` on the current head the build segfaults while making the documentation. The last few lines of the output are: raco setup: 2 rendering: pkgs/pfds/pfds/scribblings/functional-data-structures.scrbl raco setup: 1 rendering: pkgs/future-visualizer/future-visualizer/scribblings/future-visualizer.scrbl raco setup: 1 rendering: pkgs/games/scribblings/games.scrbl raco setup: 1 rendering: pkgs/racket-doc/scribblings/getting-started/getting-started.scrbl raco setup: 1 rendering: pkgs/games/gl-board-game/gl-board-game.scrbl raco setup: 1 rendering: pkgs/htdp-doc/graphics/scribblings/graphics.scrbl raco setup: 1 rendering: pkgs/gui-doc/scribblings/gui/gui.scrbl raco setup: 0 rendering: pkgs/racket-doc/help/help.scrbl raco setup: 0 rendering: pkgs/htdp-doc/htdp/htdp.scrbl raco setup: 0 rendering: pkgs/htdp-doc/scribblings/htdp-langs/htdp-langs.scrbl raco setup: 3 rendering: pkgs/html-doc/html/html.scrbl raco setup: 3 rendering: pkgs/images-doc/images/scribblings/images.scrbl raco setup: 1 rendering: pkgs/racket-doc/scribblings/inside/inside.scrbl raco setup: 1 rendering: pkgs/racket-doc/json/json.scrbl raco setup: 1 rendering: pkgs/lazy/lazy.scrbl raco setup: 1 rendering: pkgs/macro-debugger/macro-debugger/macro-debugger.scrbl raco setup: 0 rendering: pkgs/make/make.scrbl raco setup: 0 rendering: pkgs/math-doc/math/scribblings/math.scrbl raco setup: 1 rendering: pkgs/racket-doc/scribblings/more/more.scrbl raco setup: 1 rendering: pkgs/gui-doc/mrlib/scribblings/mrlib.scrbl raco setup: 1 rendering: pkgs/mysterx/scribblings/mysterx.scrbl raco setup: 1 rendering: pkgs/mzcom/mzcom.scrbl raco setup: 1 rendering: pkgs/compatibility-doc/mzlib/scribblings/mzlib.scrbl raco setup: 1 rendering: pkgs/mzscheme-doc/mzscheme/mzscheme.scrbl raco setup: 1 rendering: pkgs/net-doc/net/scribblings/net.scrbl raco setup: 1 rendering: pkgs/racket-doc/openssl/openssl.scrbl raco setup: 1 rendering: pkgs/optimization-coach/optimization-coach/scribblings/optimization-coach.scrbl raco setup: 1 rendering: pkgs/parser-tools-doc/parser-tools/parser-tools.scrbl raco setup: 1 rendering: pkgs/pict-doc/pict/scribblings/pict.scrbl raco setup: 3 rendering: pkgs/pict-snip-doc/scribblings/pict-snip/pict-snip.scrbl make[1]: *** [plain-in-place] Segmentation fault: 11 I'm on OSX 10.10.1. Anyone know whats going on/how to debug this? --spencer _ Racket Developers list: http://lists.racket-lang.org/dev
[racket-dev] Racket Winter Release
Dear Racket users, Happy New Year. As you may know, we split the Git repo for the core last year. We have been working on re-creating the release process for this new organization. Our plan is to (1) skip our normal Jan/Feb release cycle (2) test-run the release process during this cycle instead (3) resume our regular release rhythm this spring. Thanks for your patience. Matthew, Robby, Sam, Ryan, Jay, and Matthias _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] segfault during make
aha! That fixed it. Thanks. On Thu Jan 08 2015 at 6:18:12 AM Matthew Flatt mfl...@cs.utah.edu wrote: Do you have the latest images-doc and/or gui-lib packages? Recently, there was a problem with the images documentation where it tried to use `racket/gui` at document-build time. At the same time, there was also a problem in `racket/gui` that could cause a crash (mainly on Mac OS X) after `racket/gui` was used during documentation-build time. Both of those problems have been fixed. At Tue, 06 Jan 2015 22:14:53 +, Spencer Florence wrote: Hey all, When I try to run `make` on the current head the build segfaults while making the documentation. The last few lines of the output are: raco setup: 2 rendering: pkgs/pfds/pfds/scribblings/functional-data-structures.scrbl raco setup: 1 rendering: pkgs/future-visualizer/future-visualizer/scribblings/ future-visualizer.scrbl raco setup: 1 rendering: pkgs/games/scribblings/games.scrbl raco setup: 1 rendering: pkgs/racket-doc/scribblings/getting-started/getting-started.scrbl raco setup: 1 rendering: pkgs/games/gl-board-game/gl-board-game.scrbl raco setup: 1 rendering: pkgs/htdp-doc/graphics/ scribblings/graphics.scrbl raco setup: 1 rendering: pkgs/gui-doc/scribblings/gui/gui.scrbl raco setup: 0 rendering: pkgs/racket-doc/help/help.scrbl raco setup: 0 rendering: pkgs/htdp-doc/htdp/htdp.scrbl raco setup: 0 rendering: pkgs/htdp-doc/scribblings/htdp-langs/htdp-langs.scrbl raco setup: 3 rendering: pkgs/html-doc/html/html.scrbl raco setup: 3 rendering: pkgs/images-doc/images/ scribblings/images.scrbl raco setup: 1 rendering: pkgs/racket-doc/scribblings/ inside/inside.scrbl raco setup: 1 rendering: pkgs/racket-doc/json/json.scrbl raco setup: 1 rendering: pkgs/lazy/lazy.scrbl raco setup: 1 rendering: pkgs/macro-debugger/macro-debugger/macro-debugger.scrbl raco setup: 0 rendering: pkgs/make/make.scrbl raco setup: 0 rendering: pkgs/math-doc/math/scribblings/math.scrbl raco setup: 1 rendering: pkgs/racket-doc/scribblings/more/more.scrbl raco setup: 1 rendering: pkgs/gui-doc/mrlib/scribblings/mrlib.scrbl raco setup: 1 rendering: pkgs/mysterx/scribblings/mysterx.scrbl raco setup: 1 rendering: pkgs/mzcom/mzcom.scrbl raco setup: 1 rendering: pkgs/compatibility-doc/mzlib/scribblings/mzlib.scrbl raco setup: 1 rendering: pkgs/mzscheme-doc/mzscheme/mzscheme.scrbl raco setup: 1 rendering: pkgs/net-doc/net/scribblings/net.scrbl raco setup: 1 rendering: pkgs/racket-doc/openssl/openssl.scrbl raco setup: 1 rendering: pkgs/optimization-coach/optimization-coach/scribblings/optimization- coach.scrb l raco setup: 1 rendering: pkgs/parser-tools-doc/parser-tools/parser-tools.scrbl raco setup: 1 rendering: pkgs/pict-doc/pict/scribblings/pict.scrbl raco setup: 3 rendering: pkgs/pict-snip-doc/scribblings/pict-snip/pict-snip.scrbl make[1]: *** [plain-in-place] Segmentation fault: 11 I'm on OSX 10.10.1. Anyone know whats going on/how to debug this? --spencer _ Racket Developers list: http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] having zo files from two versions
I see. If you compile with v5.2.1 first, then it puts files immediately in compiled, and those will be found by v6.1. If you compile v6.1 first, then the files go in a subdirectory of compiled, and they won't interfere with v5.2.1, while v6.1 will continue to find the files in the subdirectory. That's what I tried, so I didn't think of the problem with the other order. Were you able to solve this by compiling with v6.1 first? Or some other approach? At Tue, 6 Jan 2015 15:04:40 -0800, Dan Liebgold wrote: Ok, that seems to be exactly what I'm looking for -- however I tried it and it eventually seems to wind up using just the compiled path during raco setup. Example output is here (I've echoed PLTCOMPILEDROOTS at the top, and note this is under windows): http://pasterack.org/pastes/45913 Is that enough context to see the issue? On Tue, Jan 6, 2015 at 11:58 AM, Matthew Flatt mfl...@cs.utah.edu wrote: At Tue, 06 Jan 2015 14:14:22 -0500, Neil Van Dyke wrote: Dan Liebgold wrote on 01/06/2015 02:00 PM: What is a straightforward way to designate the compiled directory to look for zo files in that can be based on the Racket version? I'd like to have Racket 5.2.1 and 6.1 running in parallel to aid in upgrading our version. Thanks! I'd like for this to be the default behavior for Racket. One possible way: Insert a directory level between the `compiled` directory and its contents, with the directory named with the Racket version number with which the code is compiled. Only that Racket version will run that compiled code. Although it's not the default, you can get that behavior by setting the `PLTCOMPILEDROOTS` environment variable to compiled/@(version): The trailing : allows compiled files to be found in compiled in the installation, while newly generated .zo files are put in a version-specific subdirectory. See also http://lists.racket-lang.org/dev/archive/2012-September/010386.html -- Dan Liebgold[dan.liebg...@gmail.com] _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] having zo files from two versions
Actually specifying two different compile root directories seem to work for most things. The exception is my json lib. I have it for 5.2.1 (since it wasn't included in the standard dist). I'd prefer 6.1 to find the standard one, but it's ok if it uses mine instead. The problem is that maybe it gets confused between the two and give me this error: link: module mismatch; possibly, bytecode file needs re-compile because dependencies changed importing module: /tmp/src-copy/danl/main/shared/src/plt/collects/dc2/target.rkt exporting module: /tmp/src-copy/danl/main/shared/src/plt/collects/json/main.rkt exporting phase level: 0 internal explanation: variable not provided (directly or indirectly and at the expected position) in: jsexpr-string31.12 context...: /tmp/src-copy/danl/main/shared/src/plt/collects/dc2/target.rkt: [running body] /tmp/src-copy/danl/main/shared/src/plt/collects/dc2/debug.rkt: [traversing imports] /tmp/src-copy/danl/main/shared/src/plt/collects/dc2/listener.rkt: [traversing imports] /tmp/src-copy/danl/main/shared/src/plt/collects/dc2/main.rkt: [traversing imports] On Thu, Jan 8, 2015 at 8:09 AM, Matthew Flatt mfl...@cs.utah.edu wrote: I see. If you compile with v5.2.1 first, then it puts files immediately in compiled, and those will be found by v6.1. If you compile v6.1 first, then the files go in a subdirectory of compiled, and they won't interfere with v5.2.1, while v6.1 will continue to find the files in the subdirectory. That's what I tried, so I didn't think of the problem with the other order. Were you able to solve this by compiling with v6.1 first? Or some other approach? At Tue, 6 Jan 2015 15:04:40 -0800, Dan Liebgold wrote: Ok, that seems to be exactly what I'm looking for -- however I tried it and it eventually seems to wind up using just the compiled path during raco setup. Example output is here (I've echoed PLTCOMPILEDROOTS at the top, and note this is under windows): http://pasterack.org/pastes/45913 Is that enough context to see the issue? On Tue, Jan 6, 2015 at 11:58 AM, Matthew Flatt mfl...@cs.utah.edu wrote: At Tue, 06 Jan 2015 14:14:22 -0500, Neil Van Dyke wrote: Dan Liebgold wrote on 01/06/2015 02:00 PM: What is a straightforward way to designate the compiled directory to look for zo files in that can be based on the Racket version? I'd like to have Racket 5.2.1 and 6.1 running in parallel to aid in upgrading our version. Thanks! I'd like for this to be the default behavior for Racket. One possible way: Insert a directory level between the `compiled` directory and its contents, with the directory named with the Racket version number with which the code is compiled. Only that Racket version will run that compiled code. Although it's not the default, you can get that behavior by setting the `PLTCOMPILEDROOTS` environment variable to compiled/@(version): The trailing : allows compiled files to be found in compiled in the installation, while newly generated .zo files are put in a version-specific subdirectory. See also http://lists.racket-lang.org/dev/archive/2012-September/010386.html -- Dan Liebgold[dan.liebg...@gmail.com] -- Dan Liebgold[dan.liebg...@gmail.com] _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] lib changes between versions
Ah, these look like good approaches. First, I think I'll have to shore up my usage of raco setup now to be sure I'm generating zos correctly for the two different versions. On Wed, Jan 7, 2015 at 10:19 PM, Tobias Hammer tobias.ham...@dlr.de wrote: I usually use this macro in a wrapper that require/provides the libs and provides compatibility wrappers when needed ;; compile time version switch (define-syntax (version=? stx) (syntax-case stx () [(_ min-version body body-else) (if (string=? (version) (syntax-e #'min-version)) #'body #'body-else)])) On Thu, 08 Jan 2015 02:56:16 +0100, Dan Liebgold dan.liebg...@gmail.com wrote: Actually this issue is still perplexing me. In 5.2.1 I have my own json lib which provides jsexpr-string. In 6.1 it's part of the distribution's collects directory. Is there a command line for racket that'll cause it to find mine under 5.2.1 and the standard lib in 6.1 (skipping mine)? Dan On Wed, Jan 7, 2015 at 4:51 PM, Dan Liebgold dan.liebg...@gmail.com wrote: Ugh. Never mind... the old json lib is mine. Carry on :) On Wed, Jan 7, 2015 at 4:45 PM, Dan Liebgold dan.liebg...@gmail.com wrote: I'm maintaining the same racket code between Racket version 5.2.1 and 6.1. One thing that changed between those version was the json to string (and vice versa) lib functions. Is there a straightforward way to define those functions so they'll work with both lib versions? Thanks, -- Dan Liebgold[dan.liebg...@gmail.com] -- Dan Liebgold[dan.liebg...@gmail.com] _ Racket Developers list: http://lists.racket-lang.org/dev -- Dan Liebgold[dan.liebg...@gmail.com] _ Racket Developers list: http://lists.racket-lang.org/dev
