caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>,
	Kenichi Asai <asai@is.ocha.ac.jp>
Subject: RE: [Caml-list] ocaml-variants via binary patch?
Date: Wed, 7 Apr 2021 12:15:09 +0000	[thread overview]
Message-ID: <PR0P264MB0700793703AC4B41461168AAC3759@PR0P264MB0700.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <YG2g4x0yfAFgR4Xn@pllab.is.ocha.ac.jp>

[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]

Dear Kenichi,

You should be able to obtain a textual diff by using

    git diff --text boot/menhir/parser.ml

Hope that helps,
Nicolás
________________________________
De : caml-list-request@inria.fr <caml-list-request@inria.fr> de la part de Kenichi Asai <asai@is.ocha.ac.jp>
Envoyé : mercredi 7 avril 2021 14:09
À : caml-list@inria.fr <caml-list@inria.fr>
Objet : [Caml-list] ocaml-variants via binary patch?

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


I am trying to create an ocaml-variant (a type debugger) in which
parser.mly is modified.  Since OCaml uses menhir, I have to run "make
promote-menhir" to obtain "boot/menhir/parser.ml".  After that, I
created a patch against the original OCaml source.  This way, I wanted
to obtain the variant by specifying the patch in the opam file.

However, git diff somehow considers "boot/menhir/parser.ml" as a
binary file.  Now I got stuck.  If I create a patch via:

git diff --binary

the patch program (launched by "opam switch create") says git binary
diff is not supported.  Is there a way to pass "--binary" to patch
launched by opam?  Or, is there a way to obtain non-binary diff for
"boot/menhir/parser.ml"?  (The file appears to be an OCaml file, with
some very long lines.)

I then tried to include "make promote-menhir" into the build process
of opam, but opam says "menhir: command not found".  Sure, menhir will
be built after the switch which I am now trying to create, leading to
circular dependency.

What can I do?

--
Kenichi Asai

[-- Attachment #2: Type: text/html, Size: 3746 bytes --]

  reply	other threads:[~2021-04-07 12:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 12:09 Kenichi Asai
2021-04-07 12:15 ` Nicolás Ojeda Bär [this message]
2021-04-07 13:05   ` Kenichi Asai

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=PR0P264MB0700793703AC4B41461168AAC3759@PR0P264MB0700.FRAP264.PROD.OUTLOOK.COM \
    --to=nicolas.ojeda.bar@lexifi.com \
    --cc=asai@is.ocha.ac.jp \
    --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).