caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "\"Márk S. Zoltán\"" <zoltan.s.mark@dravanet.hu>
To: Francois.Pottier@inria.fr
Cc: Caml Mailing List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] [ANNOUNCE] Alpha release of Menhir,	an LR(1) parser generator for ocaml
Date: Mon, 12 Dec 2005 20:51:11 +0100	[thread overview]
Message-ID: <439DD4AF.7000708@dravanet.hu> (raw)
In-Reply-To: <20051212175838.GA8502@yquem.inria.fr>

I just tried to build menhir and failed at it. Maybe the bug is on my 
side, because I do not exactly do everything by the book. My 
installation is mingw over Win2k, ocaml-3.09-0, however, it is a custom 
build over native msys, no cygwin whatsoever involved. This was not an 
issue for the last few years - I am maintaining an ocaml line for this 
platform just for fun ever since I learned about msys. I would 
understand if you did not consider this issue to be too urgent, 
appearing on an unsupported platform etc. but I thought it may be 
something more generic, so here you go:

The output is the following:

$ ./configure
checking for ocamlc.opt... no
checking for ocamlc... ocamlc
checking the version of the ocaml bytecode compiler.... 3.09.0
checking for ocamlopt.opt... no
checking for ocamlopt... ocamlopt
checking the version of the ocaml native compiler.... 3.09.0
checking for ocamldep.opt... no
checking for ocamldep... ocamldep
checking for ocamlyacc... ocamlyacc
checking for ocamllex... ocamllex
checking for a BSD-compatible install... /bin/install -c
configure: creating ./config.status
config.status: creating Makefile

$ make install
make - --unix -s PGEN="ocamlyacc -v" PARSER=parser EXECUTABLE=stage-one 
executab
les
77 states, 5444 transitions, table size 22238 bytes
18222 additional bytes used for bindings
243 states, 3079 transitions, table size 13774 bytes
10161 additional bytes used for bindings
5 states, 258 transitions, table size 1062 bytes
23 states, 1876 transitions, table size 7642 bytes
1209 additional bytes used for bindings
make - --unix -s PGEN="./stage-one -v -lg 1 -la 1 -lc 1 --comment 
--infer --erro
r-recovery --stdlib ." PARSER=fancy-parser EXECUTABLE=menhir executables
I/O error: Invalid argument
Fatal error: exception Sys_error("Invalid argument")
make[1]: *** [parser.mli] Error 1
make: *** [bootstrap] Error 2

$


Regards

    M- S- Z-



  reply	other threads:[~2005-12-12 19:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12 17:58 Francois Pottier
2005-12-12 19:51 ` "Márk S. Zoltán" [this message]
2005-12-13 21:07 ` [Caml-list] " Nathaniel Gray
2005-12-14  6:08   ` skaller
2005-12-14  9:04     ` Francois Pottier
2005-12-14 10:27       ` Alessandro Baretta
2005-12-14 21:04         ` skaller
2005-12-15  8:46           ` Francois Pottier
2005-12-15 11:03             ` skaller
2005-12-14 20:51       ` skaller
2005-12-14 22:15         ` Joaquin Cuenca Abela
2005-12-15  8:40           ` Francois Pottier
2005-12-15  6:35 ` Stefan Monnier
2005-12-15  8:47   ` [Caml-list] " Francois Pottier
2005-12-15 16:41     ` Stefan Monnier
2005-12-15 16:50       ` Francois Pottier
2005-12-15 18:56         ` Stefan Monnier
2005-12-30 21:57         ` Florian Weimer

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=439DD4AF.7000708@dravanet.hu \
    --to=zoltan.s.mark@dravanet.hu \
    --cc=Francois.Pottier@inria.fr \
    --cc=caml-list@yquem.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).