Re: [racket-dev] Pre-Release Checklist for v5.2.1
On Tue, Jan 17, 2012 at 6:44 PM, Ryan Culpepper r...@cs.utah.edu wrote: * Carl Eastlund c...@ccs.neu.edu - Dracula Tests (confirm that Dracula runs from PLaneT) Done. _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Strange error with gui and ffi
At Thu, 19 Jan 2012 15:40:07 +0100, Tobias Hammer wrote: Even if libVLCore is statically linked to a libjpeg, I think it could interact with dynamic loading of another libjpeg, depending on the platform and linking options. I digged a bit more and found the following line the rackets libffi: handle = dlopen(name, RTLD_NOW | RTLD_GLOBAL); If i interpret the manpages correct that means that all symbols from the lib are loaded and used to resolve references. That may be convenient for the libraries that the racket core uses but may lead strange behavior like the one i got whenever name clashes happen. Maybe it would be a good idea to make this import all behavior optional. I agree that RTLD_GLOBAL should be removed by default, but it should be made available as an option. Meanwhile, the details of `(ffi-lib #f)' will have to change for backward compatibility. As far as I can tell or remember, RTLD_GLOBAL is mostly there to make `(ffi-lib #f)' work, where the handle produced by `(ffi-lib #f)' finds an export in any previously loaded library. Since Racket keeps a table of all loaded libraries, maybe the right change is to implement `(ffi-lib #f)' by traversing the table in addition to using a global lookup, which means that `(ffi-lib #f)' can work without always loading libraries with RTLD_GLOBAL. Meanwhile, RTLD_GLOBAL could be optional behavior, as you suggest. _ Racket Developers list: http://lists.racket-lang.org/dev
[racket-dev] Pre-Release Checklist for v5.2.1, second call
Checklist items for the v5.2.1 release (using the v5.2.0.900 release candidate build) Search for your name to find relevant items, reply when you finish an item (please indicate which item/s is/are done). Also, if you have any commits that should have been picked, make sure that the changes are in. Important: new builds are created without announcement, usually whenever I pick a few commits. If you need to commit changes, please make sure you tell me to pick it into the release branch. -- Release candidates are at -- http://pre.racket-lang.org/release/installers Please use these installers (or source bundles) -- don't test from your own git clone (don't test v5.2.1.1 by mistake!). To get the tests directory in such a directory, you can do this: cd ...racket-root... git archive --remote=git://git.racket-lang.org/plt.git release \ -- collects/tests | tar x -- * Matthew Flatt mfl...@cs.utah.edu - mzc --exe tests - Create an executable from a BSL program. * John Clements cleme...@brinckerhoff.org - Stepper Tests Updates: - Stepper Updates: update HISTORY (updates should show v5.2.1 as the most current version; email me to pick the changes when they're done, or tell me if there are no such changes.) * Sam Tobin-Hochstadt sa...@ccs.neu.edu, Vincent St-Amour stamo...@ccs.neu.edu - Match Tests - Typed Racket Tests - Typed Racket Updates: update HISTORY (updates should show v5.2.1 as the most current version; email me to pick the changes when they're done, or tell me if there are no such changes.) * Ryan Culpepper ry...@ccs.neu.edu - DB Tests * Kathy Gray kathryn.g...@cl.cam.ac.uk - Test Engine Tests * Noel Welsh noelwe...@gmail.com - Rackunit Tests - SRFI Tests - Ensure that all claimed srfi's are in the installer and they all load into racket or drracket (as appropriate) * Eli Barzilay e...@barzilay.org - Racket Tree: compare new distribution tree to previous one _ Racket Developers list: http://lists.racket-lang.org/dev
