Re: Installation issues
Hi Lawrence, > I've gotten the latest picolisp, 3.1.9, and am trying to install locally. OK > Following the instructions for 64-bit on my linux, I've built the > executable picolisp all right. But the bin directory's pil seems to pick up > the previous version I installed before from Ubuntu: I think I know what the problem is. It may be that the wrong 'pil' is executed, because there is another one in /bin, which is intended for the global installation. You need to install /pil, e.g. $ cd $ ./pil + (the '+' at the end is recommended, to get into debug mode). You can run it from any place, e.g. with an absolute path $ /path/to/my/installation/pil + or with a relative path $ ../../installation/pil + or whatever. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Installation issues
On Fri, Feb 06, 2015 at 05:42:43PM -0500, Lawrence Bottorff wrote: > Why does the pil in .../bin/ behave this way? I'd like both, but I guess I > could uninstall one of them. . . No, keeping both is fine. I do the same. You can have as many installations on the system as you like. You simply select one of they by calling it with either non-specified path (global), or absolute or relative path (locals). ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Installation issues
Hello, I've gotten the latest picolisp, 3.1.9, and am trying to install locally. Following the instructions for 64-bit on my linux, I've built the executable picolisp all right. But the bin directory's pil seems to pick up the previous version I installed before from Ubuntu: ../bin/> ./pil : (version) 3.1.7.3 -> (3 1 7 3) However the pil in the .../picolisp/ main directory does work, giving ../picolisp/> ./pil : (version) 3.1.9.0 -> (3 1 9 0) Why does the pil in .../bin/ behave this way? I'd like both, but I guess I could uninstall one of them. . . LB
Subscribe
Keep me posted! :)