Re: pil64emu testing features
Hi Jon, At least something has changed during the make: MacBook-Air:picoLispEmu jkleiser$ (cd src64; make) emu.base.c: In function run: emu.base.c:42115: warning: format not a string literal and no format arguments emu.base.c:42170: warning: format not a string literal and no format arguments No, no change. As I said in the previous mail, this is a warning message which can be ignored (the compiler doesn't know the format string for 'printf', which it _of_course_ can't know because it is passed dynamically at runtime). This warning (-Wformat-security) is enabled on some system, for example also on Ubuntu. It could be switched off. MacBook-Air:picoLispEmu jkleiser$ ./pil + [/Users/jkleiser/.pil/history:1] File lock: Invalid argument This is strange. I expected this error to be gone. Are you sure you used the latest tarball (from yesterday, 02nov12, 18:35)? : (load misc/fibo.l) [misc/fibo.l:40] !? (here /**/) here -- Undefined Again started without the standard libraries? MacBook-Air:picoLispEmu jkleiser$ ./bin/picolisp : (load misc/fibo.l) [lib/native.l:31] !? (** 2 32) ** -- Undefined Yup ;-) MacBook-Air:picoLispEmu jkleiser$ ./bin/picolisp misc/fibo.l [misc/fibo.l:38] !? (load @lib/native.l) @lib/native.l -- Open error: No such file or directory Cheers, - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: pil64emu testing features
Hi Joe joebo@joebo:~/tmp/picolisp$ ./pil + : *CPU - emu : (load misc/fibo.l) /usr/bin/ld: skipping incompatible /usr/lib/gcc/i486-linux-gnu/4.4.5/libgcc.a when searching for -lgcc /usr/bin/ld: skipping incompatible /usr/lib/gcc/i486-linux-gnu/4.4.5/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc collect2: ld returned 1 exit status Strange. A problem of incompatible library installations? Linux 2.6.32-5-686-bigmem #1 SMP Wed Jan 12 04:40:25 UTC 2011 i686 GNU/Linux Nearly the same as I have: Linux lab 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 GNU/Linux I'm running Debian 6.0 I have squeeze with some sprinkles of wheezy and sid. I tried some very basic picolisp operations and they worked fine. So the problem seems mainly with the loading of dynamic libs. I haven't done any native work since I had been running 32bit and so I don't know if there's something broken on my install or if it's an issue with pil64emu. In any case, I wanted to share my findings. Sure. Many thanks! Cheers, - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: pil64emu testing features
Hi Jon, Yes, quite sure, and I have repeated the whole thing just now, with the latest ongoing, and I haven't spotted a single change from what I reported yesterday. That's a pity. Then I have no idea why fcntl() doesn't work :( The function ** is now obviously not defined in pil32 when I start it globally with just picolisp. If I start with ./dbg, then (** 2 32) - 4294967296. Why is that? Because just 'picolisp' is not very useful by itself. It is only the bare interpreter, without any runtime environment, and without the fundamental libraries loaded. Most notably, lib.l should be loaded, and it should be the first argument to bin/picolisp. In short, unless you want to do something special or write scripts, it is always recommended to start PicoLisp as: [./]pil [+] Cheers, - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
