[plt-scheme] schemeql installation question

From: John Clements (clements at brinckerhoff.org)
Date: Fri Dec 5 10:06:56 EST 2003

On Dec 5, 2003, at 9:34 AM, Jose Pena wrote:

>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>
> Got a little further, but not all the way...
>
> Versions were:
> DrScheme 205
> SrPersist 204
> Schemeql 0.05
> Win2K
>
> Installation error messages: (suspect related to
> SrPersist)
> ******************************************
> setup-plt:   in C:\Documents and
> Settings\jpena1\Application Data\PLT
> Scheme\205\collects\srpersist\
> load-extension: bad version 204 (not 205) from
> "C:\Documents and Settings\jpena1\Application Data\PLT
> Scheme\205\collects\srpersist\private/ 
> compiled\native\win32\i386\srpmain.dll"
> setup-plt: Done setting up
> setup-plt:
> setup-plt: Error during Compiling .zos for SchemeQL
> (C:\Documents and Settings\jpena1\Application Data\PLT
> Scheme\205\collects\schemeql)
> setup-plt:   load-extension: bad version 204 (not 205)
> from "C:\Documents and Settings\jpena1\Application
> Data\PLT
> Scheme\205\collects\srpersist\private/ 
> compiled\native\win32\i386\srpmain.dll"
> **************************************
>
> Thanks for the help.
> J.

As I mentioned before, the forward slash looks very suspicious.  In  
fact, I grepped for / in the srpersist collection, and discovered these  
two malformed require specs in srpersist.ss:

...
   (require (lib "private/sigs.ss" "srpersist"))
   (require (lib "private/srpmain.ss" "srpersist"))
...

The forward slash is treated specially in non-lib requires, but not in  
collection requires.  I've committed and tagged a fix, but if you want  
to try the fix yourself, replace srpersist.ss with this text:

(module srpersist mzscheme
   (require (lib "unitsig.ss"))
   (require (lib "sigs.ss" "srpersist" "private"))
   (require (lib "srpmain.ss" "srpersist" "private"))
   (provide-signature-elements srpersist:odbc^))


Since I don't have the shared libraries installed, I can't test it.   
This would certainly appear to fix the problem, though.

In the larger scheme of things, it would seem to be sensible to  
prohibit slashes in the components of 'lib' specifications.

john clements



Posted on the users mailing list.