caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: "Shane Y. Gibson" <shane@tuna.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] building OCaml on SCO UnixWare 7.01 system (problems)
Date: Sun, 1 Jun 2003 18:10:32 +0200	[thread overview]
Message-ID: <20030601181032.B15796@pauillac.inria.fr> (raw)
In-Reply-To: <3ED54407.3080604@tuna.org>; from shane@tuna.org on Wed, May 28, 2003 at 04:19:35PM -0700

> 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.

That's a "namespace pollution" error: the system's include files
define things that they should not according to a number of recent
Unix standards such as SUS and Unix98.  (I must resist making an SCO joke at
that point.)

A trick that may work (it was helpful to work around a similar problem
on AIX) is to specify "-D_XOPEN_SOURCE=500":

        ./configure -cc "cc -D_XOPEN_SOURCE=500"

There might be a manual page explaining those standard conformance
directives; on Solaris and Digital Unix, it's standards(5).

Hope this helps,

- Xavier Leroy

-------------------
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


      parent reply	other threads:[~2003-06-01 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 23:19 Shane Y. Gibson
2003-05-29  6:21 ` Sven Luther
2003-06-01 16:10 ` Xavier Leroy [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=20030601181032.B15796@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=shane@tuna.org \
    /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).