Re: CLISP on Haiku
Alexandru Popa <[email protected]> Wed, 20 Nov 2024 13:04:14 +0200
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <CAL2wRjQHybMUsitLN6cwWEYsPKyp6jNOpVWU48wu7r0Pbuka+Q@mail.gmail.com> |
--===============4224910639375831139== Content-Type: multipart/alternative; boundary="000000000000edcd440627561ca2" --000000000000edcd440627561ca2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Bruno, Sorry for late response, just got access to my Haiku box. Problem solved. *./lisp.run -M ../halfcompiled.mem* *./lisp.run -M ../interpretet.mem* *./lisp.run -M lispinit.mem* All these have in **features**: *[1]> *features* (:QUICKLISP :ASDF-PACKAGE-SYSTEM :ASDF3.2 :ASDF3.1 :ASDF3 :ASDF2 :ASDF :OS-UNIX :ASDF-UNICODE :LOOP :COMPILER :CLOS :MOP :CLISP :ANSI-CL :COMMON-LISP :LISP=3DCL :INTERPRETER :LOGICAL-PATHNAMES :SOCKETS :GENERIC-STREAMS :SCREEN :FFI :GETTEXT :UNICODE :BASE-CHAR=3DCHARACTER :WORD-SIZE=3D64 :UNIX)* *./lisp.run -B .* has in **features**: *[1]> *features* (:CLISP :ANSI-CL :COMMON-LISP :LISP=3DCL :INTERPRETER :LOGICAL-PATHNAMES :SOCKETS* * :GENERIC-STREAMS :SCREEN :FFI :GETTEXT :UNICODE :BASE-CHAR=3DCHARACTER* * :WORD-SIZE=3D64 :UNIX :HAIKU)* Evidently, there is a difference with *-M* and without this option. It is important to mention that with *-M* option the following files are also loaded: *~/.clisprc.lisp*, *~/quicklisp/setup.lisp* and *~/quicklisp/asdf.lisp*. These were setup with earlier attempt to build CLISP. If I rename these files to not be loaded, I have yet another version of **features**: *[1]> *features* (:READLINE :REGEXP :WILDCARD :SYSCALLS :I18N :LOOP :COMPILER :CLOS :MOP :CLISP* * :ANSI-CL :COMMON-LISP :LISP=3DCL :INTERPRETER :LOGICAL-PATHNAMES :SOCKETS= * * :GENERIC-STREAMS :SCREEN :FFI :GETTEXT :UNICODE :BASE-CHAR=3DCHARACTER* * :WORD-SIZE=3D64 :UNIX :HAIKU)* So far so good! So, I deleted all QuickLisp related stuff together with *~/.clisprc.lisp* and re-installed QuickLisp. As soon as I installed it, *:HAiKU* (only this feature) disappears again: *[1]> *features* (* *:QUICKLISP :ASDF-PACKAGE-SYSTEM :ASDF3.2 :ASDF3.1 :ASDF3 :ASDF2 :ASDF :OS-UNIX :ASDF-UNICODE **:READLINE :REGEXP :WILDCARD :SYSCALLS :I18N :LOOP :COMPILER* * :CLOS :MOP :CLISP :ANSI-CL :COMMON-LISP :LISP=3DCL :INTERPRETER* * :LOGICAL-PATHNAMES :SOCKETS :GENERIC-STREAMS :SCREEN :FFI :GETTEXT :UNICODE* * :BASE-CHAR=3DCHARACTER :WORD-SIZE=3D64 :UNIX)* So QuickLisp is the guilty party. I will debug it further. It is not fail of CLISP. Thank you for your help, Alexandru =D0=BF=D0=BD, 18 =D0=BD=D0=BE=D1=8F=D0=B1. 2024=E2=80=AF=D0=B3. =D0=B2 10:5= 0, Bruno Haible <[email protected]>: > Alexandru Popa wrote: > > When I run: > > *$ : | gcc -E -dM - | grep -i haiku* > > I get: > > *#define __HAIKU__ 1* > > That's what we expect. > > > But even when I modify *spvw.d* from: > > > > *#ifdef UNIX_HAIKU* > > * " :HAIKU"* > > *#endif* > > > > to: > > > > *#ifdef __HAIKU__* > > * " :HAIKU"* > > *#endif* > > > > I still do not have :HAIKU in **features**. Maybe I do something wrong? > > When you run './lisp.run' without any -M option, does *features* then > contain > :HAIKU? > - If no, then concentrate the search on the C compiler. > - If yes, then it means that this part of *features* got lost in the .m= em > files. Which is the first .mem file that has it lost? > > Bruno > > > > --000000000000edcd440627561ca2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi Bruno,</div><div><br></div><div>Sorry for late res= ponse, just got access to my Haiku box. Problem solved.<br></div><div><br><= /div><div><b>./lisp.run -M ../halfcompiled.mem</b></div><div><b>./lisp.run = -M ../interpretet.mem</b></div><div><b>./lisp.run -M lispinit.mem</b></div>= <div>All these have in <b>*features*</b>:</div><div><b>[1]> *features* <= br>(:QUICKLISP :ASDF-PACKAGE-SYSTEM :ASDF3.2 :ASDF3.1 :ASDF3 :ASDF2 :ASDF := OS-UNIX<br>=C2=A0:ASDF-UNICODE :LOOP :COMPILER :CLOS :MOP :CLISP :ANSI-CL := COMMON-LISP :LISP=3DCL<br>=C2=A0:INTERPRETER :LOGICAL-PATHNAMES :SOCKETS :G= ENERIC-STREAMS :SCREEN :FFI<br>=C2=A0:GETTEXT :UNICODE :BASE-CHAR=3DCHARACT= ER :WORD-SIZE=3D64 :UNIX)</b></div><div><br></div><div><b>./lisp.run -B .</= b></div><div>has in <b>*features*</b>:</div><div><b>[1]> *features* <br>= (:CLISP :ANSI-CL :COMMON-LISP :LISP=3DCL :INTERPRETER :LOGICAL-PATHNAMES :S= OCKETS</b></div><div><b>=C2=A0:GENERIC-STREAMS :SCREEN :FFI :GETTEXT :UNICO= DE :BASE-CHAR=3DCHARACTER</b></div><div><b>=C2=A0:WORD-SIZE=3D64 :UNIX :HAI= KU)</b></div><div><br></div><div>Evidently, there is a difference with <b>-= M</b> and without this option. It is important to mention that with <b>-M</= b> option the following files are also loaded: <b>~/.clisprc.lisp</b>, <b>~= /quicklisp/setup.lisp</b> and <b>~/quicklisp/asdf.lisp</b>. These were setu= p with earlier attempt to build CLISP. If I rename these files to not be lo= aded, I have yet another version of <b>*features*</b>:</div><div><div><b>[1= ]> *features* <br>(:READLINE :REGEXP :WILDCARD :SYSCALLS :I18N :LOOP :CO= MPILER :CLOS :MOP :CLISP</b></div><div><b>=C2=A0:ANSI-CL :COMMON-LISP :LISP= =3DCL=C2=A0:INTERPRETER :LOGICAL-PATHNAMES :SOCKETS</b></div><div><b>=C2=A0= :GENERIC-STREAMS :SCREEN :FFI=C2=A0:GETTEXT :UNICODE :BASE-CHAR=3DCHARACTER= </b></div><div><b>=C2=A0:WORD-SIZE=3D64 :UNIX :HAIKU)</b></div><div>So far = so good!<br></div><div><br></div><div>So, I deleted all QuickLisp related s= tuff together with <b>~/.clisprc.lisp</b> and re-installed QuickLisp. As so= on as I installed it, <b>:HAiKU</b> (only this feature) disappears again:</= div><div><div><b>[1]> *features* <br>(</b><b>:QUICKLISP :ASDF-PACKAGE-SY= STEM :ASDF3.2 :ASDF3.1 :ASDF3 :ASDF2 :ASDF :OS-UNIX<br>=C2=A0:ASDF-UNICODE = </b><b>:READLINE :REGEXP :WILDCARD :SYSCALLS :I18N :LOOP :COMPILER</b></div= ><div><b>=C2=A0:CLOS :MOP :CLISP :ANSI-CL :COMMON-LISP :LISP=3DCL=C2=A0:INT= ERPRETER</b></div><div><b>=C2=A0:LOGICAL-PATHNAMES :SOCKETS :GENERIC-STREAM= S :SCREEN :FFI=C2=A0:GETTEXT :UNICODE</b></div><div><b>=C2=A0:BASE-CHAR=3DC= HARACTER :WORD-SIZE=3D64 :UNIX)</b></div><div><br></div><div>So QuickLisp i= s the guilty party. I will debug it further. It is not fail of CLISP.<br></= div><div><br></div></div><div>Thank you for your help,</div><div>Alexandru<= br></div></div><div><br></div></div><br><div class=3D"gmail_quote"><div dir= =3D"ltr" class=3D"gmail_attr">=D0=BF=D0=BD, 18 =D0=BD=D0=BE=D1=8F=D0=B1. 20= 24=E2=80=AF=D0=B3. =D0=B2 10:50, Bruno Haible <<a href=3D"mailto:bruno@c= lisp.org">[email protected]</a>>:<br></div><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex">Alexandru Popa wrote:<br> > When I run:<br> > *$ : | gcc -E -dM - | grep -i haiku*<br> > I get:<br> > *#define __HAIKU__ 1*<br> <br> That's what we expect.<br> <br> > But even when I modify *spvw.d* from:<br> > <br> > *#ifdef UNIX_HAIKU*<br> > *=C2=A0 " :HAIKU"*<br> > *#endif*<br> > <br> > to:<br> > <br> > *#ifdef __HAIKU__*<br> > *=C2=A0 " :HAIKU"*<br> > *#endif*<br> > <br> > I still do not have :HAIKU in **features**. Maybe I do something wrong= ?<br> <br> When you run './lisp.run' without any -M option, does *features* th= en contain<br> :HAIKU?<br> =C2=A0 - If no, then concentrate the search on the C compiler.<br> =C2=A0 - If yes, then it means that this part of *features* got lost in the= .mem<br> =C2=A0 =C2=A0 files. Which is the first .mem file that has it lost?<br> <br> Bruno<br> <br> <br> <br> </blockquote></div> --000000000000edcd440627561ca2-- --===============4224910639375831139== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============4224910639375831139== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel --===============4224910639375831139==--