[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV Lynx version 2.7 compilation problem (SCO Unix)
From: |
Alan Cox |
Subject: |
Re: LYNX-DEV Lynx version 2.7 compilation problem (SCO Unix) |
Date: |
Mon, 24 Feb 1997 09:08:30 +0000 (GMT) |
> I took the time to address your stated assumption that remove()
> was used "for VMS, which has no unlink()", and to review the design
> principles of the past several years, as general information for future
> developers.
remove() is the correct call. See the ANSI C library specs
> (or new ones which perhaps have old headers unreplaced). Nothing short
> of physically replacing remove() calls with unlink() calls appeared to
> work in that particular case. Otherwise, they still get the error
> message about "__UNLINK", which is an external symbol, not in the
> Lynx code.
On the contrary. Linking the extra module
SCOcrud.c
int remove(const char *path)
{
return unlink(path);
}
with the right includes will do the job nicely
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;