Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!snorkelwacker!mit-eddie!mit-amt!dlleigh
From: dlleigh@mit-amt.MEDIA.MIT.EDU (Darren Leigh)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Lattice C Header ERROR!
Summary: same here
Message-ID: <1431@mit-amt.MEDIA.MIT.EDU>
Date: 18 Jan 90 01:55:28 GMT
References: <1990Jan15.020327.13614@athena.mit.edu> <9553@batcomputer.tn.cornell.edu>
Reply-To: dlleigh@media-lab.media.mit.edu (Darren Leigh)
Organization: MIT Media Lab, Cambridge MA
Lines: 24

In article <9553@batcomputer.tn.cornell.edu> riley@tcgould.tn.cornell.edu
(Daniel S. Riley) writes:
>In article <1990Jan15.020327.13614@athena.mit.edu>
rlcarr@space.mit.edu (the Wizard of Speed and Time) writes about the
Lattice 5.04 stdlib.h and string.h discrepancy.

>Something must have gone wrong when you installed one of the patches.  I
>have 5.04 installed, and memcpy (and the rest of the memory functions) are
>defined as void * in both string.h and stdlib.h.  No conflicting
>declarations.  If you started out with 5.02 or 5.00, go back and check the 
>dates and make sure both were updated correctly.  If you had modified one of
>them, you may have to go back to the originals and reapply the patches.
>(Ok, actually I have 5.04a, but the 5.04a patch doesn't touch the headers,
>it's just library module fixes.)
>
>Of course, if this is a Lattice supplied 5.04 disk (no user applied
>patches), then go on flaming.

I just installed the Lattice given patch and I had the exact same
problem.  It looks like the Lattice distribution is at fault.

Darren Leigh
dlleigh@media-lab.media.mit.edu
mit-amt!dlleigh