From: Damien Doligez <damien.doligez@inria.fr>
To: Pierre Habraken <Pierre.Habraken@imag.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Caml build on Linux
Date: Wed, 14 Jan 2004 13:32:20 +0100 [thread overview]
Message-ID: <B246AEB0-468D-11D8-ABCD-00039310CAE8@inria.fr> (raw)
In-Reply-To: <400514FA.604F008@imag.fr>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
On Wednesday, January 14, 2004, at 11:07 AM, Pierre Habraken wrote:
> /usr/include/string.h:242: parse error before `('
> /usr/include/string.h:242: conflicting types for `memmove'
> /usr/include/string.h:42: previous declaration of `memmove'
> /usr/include/string.h:242: parse error before `__const'
This one is a known bug. The enclosed patch should fix it.
-- Damien
[-- Attachment #2: camllight-0.75-bcopy-patch.txt --]
[-- Type: text/plain, Size: 889 bytes --]
Index: config.h
===================================================================
RCS file: /net/pauillac/caml/repository/camllight/sources/src/runtime/config.h,v
retrieving revision 1.6
retrieving revision 1.7
diff -c -r1.6 -r1.7
*** sources/src/runtime/config.h 1995/10/03 13:55:32 1.6
--- sources/src/runtime/config.h 2002/02/11 08:42:25 1.7
***************
*** 12,22 ****
/* Library dependencies */
- #ifdef HAS_MEMMOVE
- #define bcopy(src,dst,len) memmove((dst), (src), (len))
- #else
#ifdef HAS_BCOPY
/* Nothing to do */
#else
#ifdef HAS_MEMCPY
#define bcopy(src,dst,len) memcpy((dst), (src), (len))
--- 12,22 ----
/* Library dependencies */
#ifdef HAS_BCOPY
/* Nothing to do */
+ #else
+ #ifdef HAS_MEMMOVE
+ #define bcopy(src,dst,len) memmove((dst), (src), (len))
#else
#ifdef HAS_MEMCPY
#define bcopy(src,dst,len) memcpy((dst), (src), (len))
[-- Attachment #3: Type: text/plain, Size: 1 bytes --]
prev parent reply other threads:[~2004-01-14 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 6:30 Pierre Habraken
2004-01-14 9:11 ` Sven Luther
2004-01-14 10:07 ` Pierre Habraken
2004-01-14 12:32 ` Damien Doligez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B246AEB0-468D-11D8-ABCD-00039310CAE8@inria.fr \
--to=damien.doligez@inria.fr \
--cc=Pierre.Habraken@imag.fr \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox