Re: CLISP on Haiku

[Bruno H. <br...@cl...>]

Alexandru Popa wrote:
> I don't know where you got this information from. Socket behaviour is
> > generally specified by POSIX, and the Haiku bug tracker has a category
> > "System/POSIX".
> >
> I understand this from the following response of Haiku OS developer:
> https://discuss.haiku-os.org/t/make-ansi-common-lisp-available-on-haiku-again/15780/135

That was the answer from someone who had not looked at what POSIX says.

> > This is likely a bug w.r.t. POSIX as well: POSIX specifes which error code
> > is used in which case. Search for ESOCKTNOSUPPORT in
> > https://pubs.opengroup.org/onlinepubs/9799919799/functions/V2_chap02.html
> > https://pubs.opengroup.org/onlinepubs/9799919799/functions/socket.html
> > If you find that Haiku does not behave like this (it most likely doesn't,
> > since it does not even have the definition of ESOCKTNOSUPPORT), please
> > report
> > a bug.
> >
> Added this information to your ticket.

Different issues should be stated in separate tickets. When a ticket (like
this one) is already closed, waddlesplash will not keep it on his TODO list.

> For now, I want to concentrate on failing tests:
> -rw-r--r-- 1 user root  769 окт.  22 19:02 streams.erg
> -rw-r--r-- 1 user root  528 окт.  22 19:02 streamslong.erg

I think I fixed these already on 2024-11-03, no?

> -rw-r--r-- 1 user root 4444 окт.  22 19:02 socket.erg

For these test failures, only socket.d is relevant; the module 'rawsock'
is irrelevant. 

Bruno