caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Hallvard Ystad <hallvard.ystad@helpinhand.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] beginner's questions
Date: Mon, 07 Oct 2002 20:26:46 +0200	[thread overview]
Message-ID: <5.1.1.6.2.20021007202630.025db710@helpinhand.com> (raw)

So what does all this mean? May I avoid the whole problem by downloading version 3.05, or do I have to wait for 3.07?

I made the changes you mentioned below, but I still get this:
C:\ocaml>make -f Makefile.nt world
cd byterun ; make -f Makefile.nt all
gcc -mno-cygwin -DIN_OCAMLRUN -DOCAML_STDLIB_DIR='"C:/ocamlmgw/lib"' -O -Wall -W
interp.c
interp.c(215): jumptbl.h: No such file or directory
make[1]: *** [interp.d.o] Error 1
make: *** [coldstart] Error 2

So the file jumptbl.h is still missing. What should I do?

~HY
(sorry if this is out of this list's scope. If so, please tell me where to look for this kind of help.)

Dixit dmitry grebeniuk (10.19 02.10.2002):
>On Tue, 1 Oct 2002, Xavier Leroy wrote:
>
>> Probably the file bytecomp/runtimedef.ml was generated incorrectly,
>> maybe because you didn't use the correct version of "sed".  The
>> Win32 Makefiles are known to work with GNU sed as found in Cygwin, but
>> one user reported problems with another version of sed coming from
>> another Windows port of Unix tools.
>
>  Thank you for help.  Yes, you are right - problem with "sed" and
>end-of-lines.  I get sources from cvs using cvsnt, which writes CRLF
>instead of LF.  And there's an easy way to fix this problem - you can
>change
> sed -n -e 's|.*/\* \("[A-Za-z_]*"\) \*/$$|  \1;|p' byterun/fail.h | \
>to
> sed -n -e 's|.*/\* \("[A-Za-z_]*"\) \*/|  \1;|p' byterun/fail.h | \
>in Makefile.nt (thus not matching end-of-line) - the result will be the
>same, but it will work with CRLFs (matching ".?$" or "\r?$" or "\x0D?$"
>instead of "$" won't work).
>
>
>bye
>
>-------------------
>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 

Prætera censeo Carthaginem esse delendam

-------------------
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:[~2002-10-07 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07 18:26 Hallvard Ystad [this message]
     [not found] <5.1.1.6.2.20021007202649.025dba60@helpinhand.com>
     [not found] ` <Pine.LNX.4.21.0210091011210.13779-100000@vestra.bendery.md >
2002-10-09  9:13   ` Hallvard Ystad
  -- strict thread matches above, loose matches on Subject: below --
2002-09-21 11:35 Hallvard Ystad
2002-09-21 12:17 ` Dmitry Bely
2002-09-29 11:37   ` Hallvard Ystad
2002-09-30 13:16     ` dmitry grebeniuk
2002-10-01  9:20       ` Xavier Leroy
2002-10-02  8:19         ` dmitry grebeniuk

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=5.1.1.6.2.20021007202630.025db710@helpinhand.com \
    --to=hallvard.ystad@helpinhand.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).