Custom Query (1030 matches)

I am running ccl on an Ubuntu 64 VM and I am having trouble getting lx86cl to run. This is a clean install of ubuntu with nothing installed on it but what comes with it by default, build-essential and subversion. I do not think the fact that I'm working on a virtual machine is causing the issue.

I followed the instructions to install ccl from ​https://ccl.clozure.com/install.html and the associated webpages. I used the command svn co http://svn.clozure.com/publicsvn/openmcl/release/1.11/linuxx86/ccl and this created the directory in /home/username/ccl.

I attempted to run ccl directly from the terminal using the command: ./lx86cl64 and this started the 64 bit ccl just fine. However using the command ./lx86cl returned bash: ./lx86cl: No such file or directory (same goes for trying to set up the ccl script in /usr/local/bin . ccl64 works fine, but not ccl). Which is strange because when I move to the ~/ccl directory the lx86cl binary is included in the folder.

What I haven't done:

• Attempted to try this on a 32 bit version of unbuntu
• Compiled from the source

In the past I just shrugged and moved on using ccl64 only, but now I am at a point where I need to test to make sure my project works in the 32bit version. So, I'm trying to make sure each works before I set up emacs, slime and quicklisp on this clean VM.

Any thoughts on getting the 32 bit version of CCL to work for this setup? Is this a true bug? Am I alone out here with this issue?

I'm not very experienced with linux so please let me know if I'm missing something obvious!

​https://github.com/Clozure/ccldoc/blob/master/source/toplevel.lisp#L40 This is where *nx-source-note-map* is declared to be a map, it is a dynamic binding.

​https://github.com/Clozure/ccldoc/blob/master/source/toplevel.lisp#L46 This is where the map is updated.

Is it just me, or is the hashtable not accessed anywhere else in CCLDOC and therefore wasted?

(There should be a CCLDOC component in here.)

In addition to the other useful Trac plugins recently added, it would be helpful to use the Pygment syntax highlighting so that source code could be displayed with some color. Note specifically the SchemeLexer. I think that adding "*.lisp/*.lsp" to the Filename patterns for this tool would get pretty close.

Link: ​http://www.trac-hacks.org/wiki/TracPygmentsPlugin

See also: ​http://pygments.org/ ​http://pygments.org/docs/lexers/

And an example: ​http://pygments.org/demo/295/