After applying that, some tests are still failing. In test/lib/misc.l and 
test/src/main.l there are checks for chdir that use /tmp. On Mac, /tmp is a 
symlink to /private/tmp.

I would just change "/tmp" for "/bin".

Also, test/src/ext.l and test/src/ht.l fail quite early:

bash-3.2$ ./pil lib/test.l $(/bin/pwd) -bye +
[test/src/ext.l:5] !? (ext:Snx "PicoLisp is not Common Lisp")
ext:Snx -- Undefined
? 


(commented ext.l loading)

bash-3.2$ ./pil lib/test.l $(/bin/pwd) -bye +
[test/src/ht.l:5] !? (ht:Prin "1<2>3&äöü<i>ÄÖÜß")
ht:Prin -- Undefined
((pipe (ht:Prin "1<2>3&äöü<i>ÄÖÜß") (line T)))
[test/src/ht.l:5] "1&lt;2&gt;3&amp;äöü&lt;i&gt;ÄÖÜß" -- 'test' failed
? 

On Nov 4, 2012, at 3:10 PM, Jorge Acereda wrote:

> I'm not familiar with the syntax, but could this be the problem?
> 
> 
> --- a/src64/io.l        Sat Nov 03 15:07:11 2012 +0100
> +++ b/src64/io.l        Sun Nov 04 15:08:35 2012 +0100
> @@ -26,7 +26,7 @@
> (code 'rdLockFileC)
>    ld A F_RDLCK  # Read lock, length 0
> (code 'lockFileAC)
> -   st2 (Flock)  # 'l_type'
> +   st2 (Flock L_TYPE)  # 'l_type'
>    ld (Flock L_START) 0  # Start position ('l_whence' is SEEK_SET)
>    shr A 16  # Get length
>    ld (Flock L_LEN) A  # Length
> 
> On Nov 4, 2012, at 2:59 PM, Alexander Burger wrote:
> 
>> On Sun, Nov 04, 2012 at 01:07:40PM +0100, Alexander Burger wrote:
>>> If it is 9 according to the include file on the Mac, is this also the
>>> value returned by 'src64/sysdefs', and which thus appears in the above
>>> 'fcntl' line (which is (correctly) 14 for Debian)? I mean, how do these
>>> lines look on your system? Do they show 9 instead of 14?
>> 
>> What I want to say: I don't care what the actual value of F_SETLKW is.
>> It just has to be the _correct_ one on the system where it runs on. If
>> not, then the question is where it goes wrong.
>> -- 
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
> 
> -- 
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to