caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Alex Romadinoff" <alexeyr@NetCracker.com>
To: "'Simon Kirby'" <simon@ling.ed.ac.uk>, "'Karl Zilles'" <zilles@1969.ws>
Cc: <caml-list@inria.fr>
Subject: RE: [Caml-list] configure failure under cygwin when compiling ocaml
Date: Mon, 10 Feb 2003 15:39:37 +0300	[thread overview]
Message-ID: <000d01c2d101$7b3b6de0$a7fd77d4@ramodinov> (raw)
In-Reply-To: <Pine.LNX.4.44.0302101107470.9204-100000@rye>

It seams that you have broken cygwin\usr\include\sys\param.h

This file should contain lines like this:

/* All known win32 systems are little endian.  */
#define BYTE_ORDER	LITTLE_ENDIAN

I've checked Cygnus CVS
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/s
ys/?cvsroot=src and found that there are no either sys\param.h nor
sys\types.h required to check endianess.  So configure willn't work on
this version.

MinGW doesn't seam to have such a problem.

Alex

-----Original Message-----
From: Simon Kirby [mailto:simon@ling.ed.ac.uk] 
Sent: Monday, February 10, 2003 2:10 PM
To: Karl Zilles
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] configure failure under cygwin when compiling
ocaml

Hmmm... well spotted! There is definitely something going badly wrong 
with the configure script. Not sure quite what to do - I manage to get 
an older install of cygwin off another machine and it compiled OK - but 
got an error on first running about "pervasives.mli". 
Not sure what to do next - at the moment, I'm sticking with the native 
windows port, but since I don't have VC++ I can't compile optimised 
code, which is a pain. 
Has anyone else had configure errors under the latest cygwin? Can anyone

test this? 
Thanks! 
Simon 
On Fri, 7 Feb 2003, Karl Zilles wrote: 
> Simon Kirby wrote: 
> 
>  > I've used Ocaml happily under cygwin before, but just bought a new 
> machine and installed the latest cygwin (1.3.19-1) and latest ocaml 
> sources (3.06). I can't even run ./configure without an error: 
>  > 
>  > Configuring for a i686-pc-cygwin ... 
>  > gcc found 
>  > The C compiler is ANSI-compliant. 
>  > Checking the sizes of integers and pointers... 
>  > OK, this is a regular 32 bit architecture. 
>  > 64-bit "long long" integer type found (printf with "%ll"). 
>  > This is a big-endian architecture. 
> 
> 
> Configure thinks your machine is big-endian?  What exactly do you have

> Cygwin installed on? :)  PCs are little endian. 
> 
> (This is where my configure output begins to differ from yours. 
Perhaps 
> you could look into the big endian/little endian test that configure
is 
> performing to see why it is getting so confused.) 
> 
> Karl 
> 
> 
> 
-- 
Simon Kirby              Language Evolution and Computation Research
Unit 
simon@ling.ed.ac.uk                   Theoretical and Applied
Linguistics 
http://www.ling.ed.ac.uk/~simon/                  University of
Edinburgh 
------------------- 
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 

-------------------
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-02-10 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07  9:40 Simon Kirby
2003-02-08  0:52 ` Karl Zilles
2003-02-10 11:10   ` Simon Kirby
2003-02-10 12:39     ` Alex Romadinoff [this message]
2003-02-11  3:28       ` Karl Zilles

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='000d01c2d101$7b3b6de0$a7fd77d4@ramodinov' \
    --to=alexeyr@netcracker.com \
    --cc=caml-list@inria.fr \
    --cc=simon@ling.ed.ac.uk \
    --cc=zilles@1969.ws \
    /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).