From: Adrien Nader <adrien@notk.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] removal of C compiler variables in in 4.06
Date: Tue, 18 Jul 2017 11:23:04 +0200 [thread overview]
Message-ID: <20170718092304.GA26116@notk.org> (raw)
In-Reply-To: <20170718090258.GB2151@aepfle.de>
Hi,
On Tue, Jul 18, 2017, Olaf Hering wrote:
> While wresting with labltk and 4.05 I noticed an backwards incompatible
> change in labltk.git (986e116 "Fix for ocaml 4.06") and in ocaml.git
> (cc7ad5650a "Get rid of BYTECC and NATIVECC"). What is the rationale to
> break external users of BYTECC/NATIVECC? Perhaps labltk shouldnt have
> used these variables in the first place. But if their usage is legitime,
> why the needless breakage?
First of all, I absolutely definitely completely would not call these
"needless" and even less say that breakage was voluntary. I understand
your frustration but the way you communicate about the issue doesn't
come out as nice.
This change was part of a huge set of changes to fix 20 years of
duplication between the Makefile and Makefile.nt files in the build
system.
The commit that did the changes is the following:
https://github.com/ocaml/ocaml/commit/cc7ad5650aac641053178ec1d08789b8e793e87b
I don't think it makes sense to try to give you straight away another
variable to use. Chances are that, in the first place, this variable
wasn't the one that made sense to use. Moreover its content could change
at any time (and did change). If you explain the needs, then it should
be possible to give you better hints to adapt to this change.
Best,
--
Adrien Nader
next prev parent reply other threads:[~2017-07-18 9:23 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 [this message]
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
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=20170718092304.GA26116@notk.org \
--to=adrien@notk.org \
--cc=caml-list@inria.fr \
--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