From: "Stéphane Glondu" <steph@glondu.net>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Olaf Hering <olaf@aepfle.de>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] removal of C compiler variables in in 4.06
Date: Tue, 18 Jul 2017 14:59:35 +0200 [thread overview]
Message-ID: <39097b87-8489-d5f4-c766-11766ac70bee@glondu.net> (raw)
In-Reply-To: <CAPFanBGM-O9qdyxg1kT5JSA_+sC2A+p3m+OXwZ0WGJbTgcv=hw@mail.gmail.com>
On 18/07/2017 14:24, Gabriel Scherer wrote:
> Stéphane, in your patches, it looks to me like you apply the
> 4.06-required change in 0001-Fix-for-ocaml-4.06.patch,
That patch is not mine. It is taken from upstream git repository. My
patches are 0002- to 0004- and (should) apply to the master branch of
upstream repository.
> and then you
> cancel them in 0003-CC-variable-does-not-exist-in-4.05.0-s-Makefile.conf.patch
> to go back to the unchanged state. Could you apply none of them
> instead? (It does not help that there is an unrelated change in
> 0001-..-4.06.patch, it would be nicer to have two separate patches.)
I agree. I kept 0001- as is because the unrelated change is also needed
to compile with 4.05.0
> Note that your patch 0002-Fix-calls-to-caml_-functions.patch is very
> nice (use of the caml_ prefix for C runtime functions, the unprefixed
> functions being deprecated and disabled by default), you should
> definitely submit it upstream.
https://github.com/garrigue/labltk/issues/4
Cheers,
--
Stéphane
next prev parent reply other threads:[~2017-07-18 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 9:02 Olaf Hering
2017-07-18 9:23 ` Adrien Nader
2017-07-18 13:31 ` Olaf Hering
2017-07-18 11:37 ` Stéphane Glondu
2017-07-18 12:24 ` Gabriel Scherer
2017-07-18 12:59 ` Stéphane Glondu [this message]
2017-07-18 13:41 ` Olaf Hering
2017-07-18 13:49 ` Gabriel Scherer
2017-07-18 18:04 ` Olaf Hering
2017-07-18 13:28 ` Jesper Louis Andersen
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=39097b87-8489-d5f4-c766-11766ac70bee@glondu.net \
--to=steph@glondu.net \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=olaf@aepfle.de \
/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).