From: "Shane Y. Gibson" <shane@tuna.org>
To: caml-list@inria.fr
Subject: [Caml-list] building OCaml on SCO UnixWare 7.01 system (problems)
Date: Wed, 28 May 2003 16:19:35 -0700 [thread overview]
Message-ID: <3ED54407.3080604@tuna.org> (raw)
Hello,
I'm not much of a programmer, but I need to port OCaml to SCO UnixWare
7.01 system, so I can build and run the Unison package, which utilizes
OCaml.
During the compilation process (with both GCC 2.95 and the SCO
Development System CC compiler), I get the following errors:
gcc -I../../byterun -O -fno-defer-pop -Wall -Wno-unused
-D_FILE_OFFSET_BITS=64 -g -c scheduler.c
scheduler.c:97: conflicting types for `thread_t'
/usr/include/sys/types.h:305: previous declaration of `thread_t'
*** Error code 1 (bu21)
UX:make: ERROR: fatal error.
The 'thread_t' declaration in types.h reads:
#ifndef _THREAD_T
#define _THREAD_T
typedef id_t thread_t; /* thread id type */
#endif
I'm not sure what the issue is, but I suspect it's a fairly simple fix
in terms of how the 'thread_t' type is being called, vs. how the include
file is defining how it should be called?
If anyone has any thoughts or ideas, I would greatly appreciate any
input. This is version 3.04 of OCaml that I'm trying to build. Please
respond with me in the TO or CC field, as I'm not a regular subscriber
to the email list. Thank you.
v/r
Shane
--
"Beyond the very extremity of fatigue and distress we may
find amounts of ease and power we never dreamed ourselves
to own, sources of strength never taxed at all because we
never push through the obstruction." -- William James
-------------------
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
next reply other threads:[~2003-05-28 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 23:19 Shane Y. Gibson [this message]
2003-05-29 6:21 ` Sven Luther
2003-06-01 16:10 ` Xavier Leroy
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=3ED54407.3080604@tuna.org \
--to=shane@tuna.org \
--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