Re: CLISP on Haiku
Alexandru Popa <[email protected]> Thu, 14 Nov 2024 17:20:04 +0200
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <CAL2wRjTAWBtqjqssRo7cb-mxktFRBP=_643SbA1p-uMMaUB1Gw@mail.gmail.com> |
--===============2743501042459677755== Content-Type: multipart/alternative; boundary="000000000000cef4840626e0fc1d" --000000000000cef4840626e0fc1d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =D1=87=D1=82, 14 =D0=BD=D0=BE=D1=8F=D0=B1. 2024=E2=80=AF=D0=B3. =D0=B2 15:1= 0, Bruno Haible <[email protected]>: > Alexandru Popa wrote: > > Still in my build of CLISP *features* list :UNIX (last) but not :HAIKU. > > Where the definition "#ifdef UNIX_HAIKU" comes from? > > It comes from lispbibl.d:315. > > > AFAIK, the standard Haiku macro is "#ifdef __HAIKU__". > > What's the result of these commands on your machine? > $ : | gcc -E -dM - | grep -i haiku > $ gcc -v > When I run: *$ : | gcc -E -dM - | grep -i haiku* I get: *#define __HAIKU__ 1* The command: *gcc -v* shows (among other): *Target: x86_64-unknown-haiku* *gcc version 13.3.0 (2023_08_10)* Regarding *lispbibl.d*, I see the origin of *UNIX_HAIKU*. 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? --000000000000cef4840626e0fc1d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail= _attr">=D1=87=D1=82, 14 =D0=BD=D0=BE=D1=8F=D0=B1. 2024=E2=80=AF=D0=B3. =D0= =B2 15:10, Bruno Haible <<a href=3D"mailto:[email protected]">bruno@clisp.= org</a>>:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px= 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Ale= xandru Popa wrote:<br> > Still in my build of CLISP *features* list :UNIX (last) but not :HAIKU= .<br> > Where the definition "#ifdef UNIX_HAIKU" comes from?<br> <br> It comes from lispbibl.d:315.<br> <br> > AFAIK, the standard Haiku macro is "#ifdef __HAIKU__".<br> <br> What's the result of these commands on your machine?<br> $ : | gcc -E -dM - | grep -i haiku<br> $ gcc -v<br></blockquote><div><br></div><div>When I run:</div><div><b>$ : |= gcc -E -dM - | grep -i haiku</b></div><div>I get:</div><div><b>#define __H= AIKU__ 1</b></div><div><br></div><div>The command:</div><div><b>gcc -v</b><= /div><div>shows (among other):</div><div><b>Target: x86_64-unknown-haiku</b= ></div><div><b>gcc version 13.3.0 (2023_08_10)</b></div><div><br></div><div= ><div>Regarding <b>lispbibl.d</b>, I see the origin of <b>UNIX_HAIKU</b>.</= div><div><br></div></div><div>But even when I modify <b>spvw.d</b> from:</d= iv><div><br></div><div><b>#ifdef UNIX_HAIKU</b></div><div><b>=C2=A0 " = :HAIKU"</b></div><div><b>#endif</b></div><div><br></div><div>to:</div>= <div><br></div><div><b>#ifdef __HAIKU__</b></div><div><b>=C2=A0 " :HAI= KU"</b></div><div><b>#endif</b></div><div><br></div><div>I still do no= t have :HAIKU in <b>*features*</b>. Maybe I do something wrong?<br></div></= div></div> --000000000000cef4840626e0fc1d-- --===============2743501042459677755== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============2743501042459677755== 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 --===============2743501042459677755==--