Re: LYNX-DEV Configure patch for SCO

[Bela Lubkin]

Jean-Pierre Radley wrote:

> SCO Unix (both 3.2v4.x and 3.2v5.x) needs to inlude libsocket when compiling.

As Tom said, this should be found by configure (and always has been, for
me, but I'm still on ac.36).  Special cases should be reduced, not
increased.  For which I say:

>   sco3.2v5*)
>       test $ac_cv_prog_gcc != yes && CC="cc -belf"
> +     LIBS="$LIBS -lsocket"
>       ;;
>   sco*)
> !     LIBS="$LIBS -lmalloc -lsocket"

In fact, the "-lmalloc" should also be eliminated as a special case.
configure could check whether a libmalloc exists, and use it if it does
(unless there are known cases of libmalloc being worse than the libc
malloc, on some OS?)

Even the "-belf" could be configured.  The gcc's for OpenServer
variously support either "-belf" or "-melf" for ELF code generation.
ELF is generally preferable.  I'm sure configure could figure out which
of those flags does anything useful...  "-melf" should be more general,
available under gcc on multiple OSes and architectures, so a generic
test for it might be sensible.

>       # It's a little late to do much, but try to warn user if he's using
>       # SCO's cc (which is reported to have broken const/volatile).

If there are problems that affect Lynx, they can be configure-tested...

>Bela<
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;