> On Aug 14, 2023, at 15:15, l@tlo wrote:
>
> One year later...
>
> (I don't even remember sending that older mail... 😅)
>
>
> Building on macOS (13) seems to work fine with the following instructions:
>
> https://picolisp.com/wiki/?alternativeMacOSRepository
I just noticed the reply by L
One year later...
(I don't even remember sending that older mail... 😅)
Building on macOS (13) seems to work fine with the following instructions:
https://picolisp.com/wiki/?alternativeMacOSRepository
*and*
Mike's Makefile here:
https://git.envs.net/mpech/pil21-tests/raw/branch/master/Makefil
> On May 30, 2022, at 18:18, Alexander Burger wrote:
>
> Hi Jean-Christophe,
>
>> It looks like I'm slowly getting somewhere...
>> ...
>
> Great! :)
>
>
>> ./pil: line 2: exec:
>> /Users/suzume/Documents/Repositories/pil21+/src/../bin/picolisp: cannot
>> execute: No such file or director
Hi Jean-Christophe,
> It looks like I'm slowly getting somewhere...
> ...
Great! :)
> ./pil: line 2: exec:
> /Users/suzume/Documents/Repositories/pil21+/src/../bin/picolisp: cannot
> execute: No such file or directory
That's an easy one. It tries to bootstrap, but bin/picolisp does not exist
It looks like I'm slowly getting somewhere...
➜ pil21+ git:(master) ✗ which opt
/usr/local/opt/llvm@11/bin/opt
➜ pil21+ git:(master) ✗ which clang
/usr/local/opt/llvm@11/bin/clang
➜ pil21+ git:(master) ✗ which llvm-link
/usr/local/opt/llvm@11/bin/llvm-link
➜ pil21+ git:(master) ✗
> On May 29, 2022, at 23:41, Mike wrote:
>
>>> show output:
>>> ===
>>> $ which opt
>>> $ which clang
>>> $ which llvm-link
>>> ===
>>>
>>
>> ➜ src git:(master) ✗ which opt
>> /opt/local/bin/opt
>> ➜ src git:(master) ✗ which clang
>> /usr/bin/clang
>> ➜ src git:(master) ✗ which llvm-link
>
Thank you.
It looks like it was a clang issue.
I'll check that later next week. And *will* come back here to report :-)
JC
> On May 29, 2022, at 23:23, Frithjof Schulze wrote:
>
> Hi all,
>
> I never used Picolisp on a MacOS system, but tried the Makefile.macos today.
> I needed to do a few
Hi all,
I never used Picolisp on a MacOS system, but tried the Makefile.macos today. I
needed to do a few changes, because my version of Homebrew uses other patches,
but then everything worked fine with the llvm, readline, libffi and openssl
versions from brew.
% make clean
% export PATH="/op
> On May 29, 2022, at 22:12, Mike wrote:
>
>> ➜ pil21+ git:(master) ✗ cd src
>> ➜ src git:(master) ✗ rm *.bc
>> ➜ src git:(master) ✗ make
>> opt -O3 -o base.bc base.ll
>> clang -O3 -w -c -o lib.bc -D_OS='"Darwin"' -D_CPU='"x86_64"' `pkg-config
>> --cflags libffi` -emit-llvm lib.c
>> llvm-link
> On May 29, 2022, at 21:16, Mike wrote:
>
>>
>> Ok. I have readline installed both with brew and port:
>
> why you have both brew and port? You mess it.
Because some utilities are only available in port and some in brew but they
have common dependencies so the dependencies come installed
> On May 29, 2022, at 18:52, Mike wrote:
>
>>
>> I've installed readline from macport as you suggested and I'm using your
>> Makefile.
>>
>> Also I'm not finding any path to brew installs in your Makefile. There is no
>> reference to /usr/local anywhere.
>>
>> Which line in the Makefile w
> On May 29, 2022, at 15:16, Mike wrote:
>
lib.c:119:4: error: use of undeclared identifier 'rl_catch_signals'
rl_catch_signals = 0;
^
lib.c:121:4: error: use of undeclared identifier 'rl_input_available_hook'
rl_input_available_hook = rlAvail;
^
...
>>
On Sun, May 29, 2022 at 01:04:19PM +0900, Jean-Christophe Helary wrote:
> >> lib.c:119:4: error: use of undeclared identifier 'rl_catch_signals'
> >> rl_catch_signals = 0;
> >> ^
> >> lib.c:121:4: error: use of undeclared identifier 'rl_input_available_hook'
> >> rl_input_available_hook = rlA
> On May 29, 2022, at 5:10, Alexander Burger wrote:
>
> Hi Jean-Christophe,
>
>> lib.c:119:4: error: use of undeclared identifier 'rl_catch_signals'
>> rl_catch_signals = 0;
>> ^
>> lib.c:121:4: error: use of undeclared identifier 'rl_input_available_hook'
>> rl_input_available_hook = r
Hi Jean-Christophe,
> lib.c:119:4: error: use of undeclared identifier 'rl_catch_signals'
>rl_catch_signals = 0;
>^
> lib.c:121:4: error: use of undeclared identifier 'rl_input_available_hook'
>rl_input_available_hook = rlAvail;
>^
> ...
They are all from the readline library.
☺/
> On May 29, 2022, at 4:16, Mike wrote:
>
>>
>> ➜ pil21+ git:(master) ✗ (cd src; make)
>> /opt/local/libexec/llvm-10/bin/llvm-link: lib.bc: error: Unknown attribute
>> kind (68) (Producer: 'APPLE_1_1300.0.29.30_0' Reader: 'LLVM 10.0.1')
>> /opt/local/libexec/llvm-10/bin/llvm-link: error: loa
I've just reinstalled my whole macport and I still have the same error.
➜ pil21+ git:(master) ✗ port installed
The following ports are currently installed:
bzip2 @1.0.8_0 (active)
gettext-runtime @0.21_0 (active)
icu @67.1_4 (active)
libcxx @5.0.1_4 (ac
> On May 29, 2022, at 0:16, Mike wrote:
>
>>
>> Probably an incompatibility between Brew and Macport.
>
> Correct, i already wrote about this incompatibility and this is what error
> message says.
I just removed my whole brew install and I get the same error:
➜ pil21+ git:(master) ✗ br
Thank you Andras for the Makefile.
I get the same message as with Mike's Makefile, so I suppose there is an issue
with my system...
Probably an incompatibility between Brew and Macport.
I'm going to thoroughly check that.
JC
> On May 28, 2022, at 22:57, Andras Pahi wrote:
>
> Hi,
>
> I
Hi,
I use the following Makefile to build pil21 on macOS Mojave (10.14.6) x86_64,
libreadline, libffi and OpenSSL 3 is used from MacPorts.
I have checked with picoLisp-22.3.tgz version 22.3.16
and pil21.tgz (the rolling release) version 22.5.26.
Regards,
Andras Pahi
~~ cut here ~~
# 24
> On May 28, 2022, at 19:24, Mike wrote:
>
>
>
>> On May 28, 2022, at 13:13, Jean-Christophe Helary
>> wrote:
>>
>> 
>>
>>> On May 25, 2022, at 18:45, Mike wrote:
>>>
>>> hi all,
>>>
They used to work (I have a working build of pil21 21.9.3), but they don't
anymore.
M
> On May 25, 2022, at 18:45, Mike wrote:
>
> hi all,
>
>> They used to work (I have a working build of pil21 21.9.3), but they don't
>> anymore.
>> Maybe there is something wrong with my system but I have no idea what it is.
>
> Did you built picolisp?
How would I go about building picolis
Hi Mike,
The instructions from the website used to be sufficient to have a working pil
system.
- clone
- patch the Makefile
- make
There was nothing about building picolisp.
That's the reason why I put them on the wiki. If they had not worked for me, I
would not have bothered.
JC
> On May 2
> On May 24, 2022, at 0:03, Mike wrote:
>
>
>
>> On May 23, 2022, at 16:26, Jean-Christophe Helary
>> wrote:
>>
>> 
>>
>>> On May 23, 2022, at 21:23, Mike wrote:
>>>
>>> hi all,
>>>
>>>
➜ src git:(master) ✗ make
make: opt: No such file or directory
make: *** [base.bc
> On May 23, 2022, at 21:23, Mike wrote:
>
> hi all,
>
>
>> ➜ src git:(master) ✗ make
>> make: opt: No such file or directory
>> make: *** [base.bc] Error 1
>
> Right, `opt` optimizer is part of llvm from brew and it is not in the $PATH.
> You must fix it and repeat.
My understanding wa
> On May 23, 2022, at 20:31, Mike wrote:
>
> May 23, 2022, 2:06 PM, "Jean-Christophe Helary"
> mailto:li...@traduction-libre.org?to=%22Jean-Christophe%20Helary%22%20%3Clists%40traduction-libre.org%3E
> > wrote:
>
>>
>>>
>>> On May 23, 2022, at 16:16, Mike wrote:
>>>
>>> May 23, 2022, 7:
> On May 23, 2022, at 16:16, Mike wrote:
>
> May 23, 2022, 7:13 AM, "Jean-Christophe Helary" mailto:li...@traduction-libre.org?to=%22Jean-Christophe%20Helary%22%20%3Clists%40traduction-libre.org%3E
> > wrote:
>
>>
>> I get the exact same result as my previous attempt with the other Makefil
> On May 23, 2022, at 2:54, Mike wrote:
>
> hi all,
>
> https://git.envs.net/mpech/pil21-tests/raw/branch/master/Makefile.macos
>
> This is my Makefile I am using and will maintain for macos port.
> Please try.
Thank you Mike.
I get the exact same result as my previous attempt with the oth
> On May 22, 2022, at 21:44, Mike wrote:
>
> May 22, 2022, 3:00 PM, "Jean-Christophe Helary"
> mailto:li...@traduction-libre.org?to=%22Jean-Christophe%20Helary%22%20%3Clists%40traduction-libre.org%3E
> > wrote:
>
>>
>> I'm following the instructions here:
>> https://picolisp.com/wiki/?alte
29 matches
Mail list logo