Re: Install help

[Lawrence Bottorff]

I did

~/opt/picoLisp/src64$ ~/opt/picoLisp/pil +

and the REPL came up. No, I don't have the old Ubuntu installed. That might
have been another computer. So now I should do the soft links (mentioned in
the INSTALL) if I want to make it global, correct?


On Sat, Dec 26, 2015 at 4:59 PM, Alexander Burger 
wrote:

> Hi Larry,
>
> > I'm back again after a pause. Anyway, trying to install 15.11 but getting
> > confused. The INSTALL file says to
> >
> > $ (cd src64; make)
> >
> > Good. That worked fine on my Ubuntu 15.10. Now it's in ~/opt/picoLisp/
> and
> > the ~/opt/picoLisp/bin/ has picoLisp, pil, pilIndent, pilPretty, psh,
> > replica, watchdog as executables.
>
> Perfect! This means that you successfully compiled the PicoLisp
> executable.
>
> It must be that you have already installed a global PicoLisp from the
> Ubuntu distribution, so that al that "bootstrapping" stuff is not
> necessary. Once you have a picolisp running, it is used to build the new
> one.
>
>
> > pil doesn't work because it expects a
> > soft link to /usr/bin/picolisp. But ./picolisp works and gives me a REPL.
>
> "./picolisp" is not the recommended way. You should be in the installation
> directory (the one you executed (cd src64; make) from, and then do
>
>$ ./pil +
>
> or call
>
>$ ~/opt/picoLisp/pil +
>
> from any place.
>
> The point is to call 'pil' either with an absolute (like above) or a
> relative path (e.g. ../foo/bar/pil +), or with the default path in which
> case it resolves to /usr/bin/pil typically (i.e. the Ubuntu version in
> your case).
>
>
> > I'm assuming I'm not finished, right?
>
> No, you are :)
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: Install help

[Alexander Burger]

Hi Larry,

> I'm back again after a pause. Anyway, trying to install 15.11 but getting
> confused. The INSTALL file says to
> 
> $ (cd src64; make)
> 
> Good. That worked fine on my Ubuntu 15.10. Now it's in ~/opt/picoLisp/ and
> the ~/opt/picoLisp/bin/ has picoLisp, pil, pilIndent, pilPretty, psh,
> replica, watchdog as executables.

Perfect! This means that you successfully compiled the PicoLisp
executable.

It must be that you have already installed a global PicoLisp from the
Ubuntu distribution, so that al that "bootstrapping" stuff is not
necessary. Once you have a picolisp running, it is used to build the new
one.


> pil doesn't work because it expects a
> soft link to /usr/bin/picolisp. But ./picolisp works and gives me a REPL.

"./picolisp" is not the recommended way. You should be in the installation
directory (the one you executed (cd src64; make) from, and then do

   $ ./pil +

or call

   $ ~/opt/picoLisp/pil +

from any place.

The point is to call 'pil' either with an absolute (like above) or a
relative path (e.g. ../foo/bar/pil +), or with the default path in which
case it resolves to /usr/bin/pil typically (i.e. the Ubuntu version in
your case).


> I'm assuming I'm not finished, right?

No, you are :)
♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Subscribe

[Lawrence Bottorff]

Subscribe

Install help

[Lawrence Bottorff]

Hello,

I'm back again after a pause. Anyway, trying to install 15.11 but getting
confused. The INSTALL file says to

$ (cd src64; make)

Good. That worked fine on my Ubuntu 15.10. Now it's in ~/opt/picoLisp/ and
the ~/opt/picoLisp/bin/ has picoLisp, pil, pilIndent, pilPretty, psh,
replica, watchdog as executables.  pil doesn't work because it expects a
soft link to /usr/bin/picolisp. But ./picolisp works and gives me a REPL.

But then the instructions say

To build the 64-bit version the first time (bootstrapping), you have the
   following three options:

   - If a Java runtime system (version 1.6 or higher) is installed, it will
 build right out of the box.

   - Otherwise, download one of the pre-generated "*.s" file packages

 - http://software-lab.de/arm64.linux.tgz
 - http://software-lab.de/x86-64.linux.tgz
 - http://software-lab.de/ppc64.linux.tgz
 - http://software-lab.de/x86-64.freeBsd.tgz
 - http://software-lab.de/x86-64.sunOs.tgz

   - Else, build a 32-bit version first, and use the resulting bin/picolisp
to
 generate the "*.s" files:

  $ (cd src; make)
  $ (cd src64; make x86-64.linux)

   After that, the 64-bit binary can be used to rebuild itself.


 . . not sure what any of that means or what I'm supposed to do with it.
I'm assuming I'm not finished, right?

Larry Bottorff

wr function in Ersatz

[Christophe Gragnic]

Hi,
This may be more a question for Alex.
Is there a reason why 'wr is not included in Ersatz?
Or am I missing something?

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