caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: wang yin <shredder@sohu.com>
To: caml-list@inria.fr
Subject: [Caml-list] problem compiling libunix on Linux
Date: Sat, 2 Aug 2003 22:41:12 +0800	[thread overview]
Message-ID: <259834198.03985@mails.tsinghua.edu.cn> (raw)
Message-ID: <20030802144112.GA1541@wangyin.com> (raw)

Hi,

I'm trying to compile libunix in contrib directory for my
Linux machine, because HOL-light uses libunix.

But it seem that libunix uses BSD style headers. And I get
the following compiler error from GCC:

gcc -I../../src/runtime -O    -c -o accept.o accept.c
In file included from /usr/include/sys/un.h:38,
                 from socketaddr.h:4,
                 from accept.c:8:
/usr/include/string.h:257: parse error before '(' token
/usr/include/string.h:257: conflicting types for `memmove'
/usr/include/string.h:43: previous declaration of `memmove'
/usr/include/string.h:257: parse error before "const"
make: *** [accept.o] Error 1

Stracing into string.h, I found that problem emerges from
the BSD prototype:

#ifdef __USE_BSD
/* Copy N bytes of SRC to DEST (like memmove, but args
reversed).  */
extern void bcopy (__const void *__src, void *__dest, size_t
__n) __THROW;

....

Why is __USE_BSD defined? I can't find it anywhere in my
distribution. How can I solve this problem? HOL Light can be
used without libunix, but it requires libnum, and libnum
depends on libunix. And many other contrib libraries depends
on it. So I must get libunix compiled!

Can any one give some hints?


-- 
Wang Yin
Deparment of Computer Science and Technology,
Tsinghua University,
100084
Beijing China

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


                 reply	other threads:[~2003-08-02 14:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=259834198.03985@mails.tsinghua.edu.cn \
    --to=shredder@sohu.com \
    --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;
as well as URLs for NNTP newsgroup(s).