Re: LYNX-DEV Re: is lynxrp.zip working /slang and color choices

[Foteos Macrides]

Klaus Weide <address@hidden> wrote:
>On Thu, 31 Oct 1996, Nelson Henry Eric wrote:
>
>> > > > > Had trouble compiling because of the `$(STYLE).o' line in
>> [...]
>> > > sunos4.1.3/ncurses-1.9.9e/gcc-2.7.2
>> [...]
>[Rob Partington:]
>> > Are you using GNU make?  If not, that might be the problem.
>> 
>> No, I'm still using Sun's (wherever they ripped it off from).  If it is
>> dependent on what `make' you are using, then I couldn't recommend such
>> syntax in the Makefile because it will narrow the prospective user base.
>
>A specific make shouldn't be required to compile Lynx, unless that change
>would be of tremendous benefits (which I don't see).  But Rob may just
>not be aware of it when he uses GNU-make-only constructs in his code,
>so it would probably help if non-GNU-make folks could point out what
>exactly he should not use.  

        Note, however, that an upgrade to the v5 W3C Reference Library
and it's use, now, of autoconf, in turn makes use of the GNU make a
requirement (or so the v5 Library's docs claim 8-).  The previous
K&Rizing, and use of platform/flavor #ifdef'ing, was geared toward
what we have now in Lynx -- attempted support for every platform/flavor's
native compiler and make (or .com's and/or MMS on VMS).

        The claim that such a change would "narrow the prospective user
base" needs to be understood, thought through, perhaps tested, overtly
(IMHO).  It had been by own assumption the previous time autoconfing
was proposed, but that was before the Reference Library developers
decided that "anybody" could get the GNU make, so the change won't
"narrow the prospective user base".  Which assumption is correct?

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;