Hi Jorge,
Ok, if that's the problem this is nicer… Does it compile without
warnings on your 32-bit system?
Yes. Great! That's better. I didn't know about 'uintptr_t', that's
exactly what we need here. Thanks!
So let's stay with this :)
♪♫ Alex
--
UNSUBSCRIBE:
Hi Oskar,
This is strange. 'ht:Pack' (in the 'ht' library) is part of the PicoLisp
core. How did you install it? Along the lines of the INSTALL file, or
from a Debian-Derivate?
I build the emu version along the lines of your INSTALL file.
With local installation mode on a 32-bit ubuntu
Hi Alex,
OK. So if 'ht:Pack' is undefined, then either the 'ht' library is not
found, or it somehow has the wrong contents.
What does
$ file picoLispDir/lib/ht
say? Is it perhaps incompatible to your 'picolisp' executable (e.g.
remained from some other build)?
/lib/ht: ELF 32-bit LSB
Hi Oskar,
I builded the 64-bit version again, got a new ht file and 'ht:Pack'
is defined. (The timestamp on the files showed me I builded the
32-bit on top of the 64-bit)
Fine. That explains it.
And now the 32-bit version is showing 'ht:Pack' undefined :)
Better not run them in one
Hi Alex,
It turns out that my default script was producing the same HTML code
when I run it on c9.io (64-bit) as when I run it on localhost:8080/
(32-bit). E.g. the HTML on demo-project.jkleiser.c9.io/doc/ for the
ref.html link was a href=doc/ref.htmlref.html/a, but in the
browser that was
Hi Jon,
href=doc/ref.htmlref.html/a, but in the browser that was
expanded to the double-doc
http://demo-project.jkleiser.c9.io/doc/doc/ref.html;. On c9.io I
...
sure. Can you suggest a fix for my default script that will make
it work in both contexts?
Hm, this sounds as if the browser is
Hi Jon,
of doc/). Is it possible for my default script to access any info
about the HTTP request from my web server (web.l)?
There are some globals which are set by the server, like
*Url The requested URL
*Adr The client's address
*Post Boolean GET/POST
Hi,
Here is my improved 'default' script. It now works both on c9.io and on
localhost, and it handles both doc and doc/. The logic that takes
care of all this, may not be rock solid and very clean, but at the
moment it's the best I can do. Here it is:
# This 'default' will be executed as a
Hi,
A quick question, what's the status of the *FPic variant on Linux? Is it
working?
If it works properly, I guess I could get it running on OSX as well when I find
some spare time...--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
