Re: How's it coming ?

From: Kent Landfield <>
Date: Tue, 26 Oct 1999 08:54:25 -0500 (CDT)
Message-Id: <>

# Well, that's brilliant, at least. BUT. SCO people will use SCO C
# compilers, which behave differently from GNU/Cygnus compilers and want
# different header files and do other strange things. Hope that they also
# configure for GCC 2.8 and higher, since that's what I use on OS 5.0; on
# UnixWare I use the native SCO compiler.

They are testing it on both SCO C compilers and GNU on both systems.

# | # Ermmm ... don't want to spoil the party, but how about the
# src/mail.c
# | # code? As I wrote earlier, the code you suggested, Kent, failed at
# line
# | # 145 and attempts on my part to rectify things only resulted in more
# | # complaints further up.


Earlier you wrote:
# 1: The default now is to compile src/mail as standard. This compile
# needed adding /usr/lib/libsocket.a to MAILOBS in src/Makefile by hand,
# in order to compile mail (the configure script omits this);

Configure now checks for libsocket.a.

# 2: mail is still unusable when used by MS Internet Explorer 5 and
# Netscape Communicator 4.61. In IE 5.0 it still produces the same rubbish
# characters in the text and with Communicator it will not even send text.

I just tested it here and it works fine. Compiled it directly from a CVS copy.

# Of course, if it were to quote original body as well in the reply, it'd
# be the bee's knees :-)

Such as putting it in <EM>original body</EM> ?

Are there other problems I'm not aware of ?

Kent Landfield                        Phone: 1-817-545-2502             
Search the Usenet FAQ Archive at
Search the RFC/FYI/STD/BCP Archive at
Received on Tue 26 Oct 1999 03:55:45 PM GMT

This archive was generated by hypermail 2.3.0 : Sat 13 Mar 2010 03:46:11 AM GMT GMT