caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Adrien Nader <adrien@notk.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] removal of C compiler variables in in 4.06
Date: Tue, 18 Jul 2017 15:31:03 +0200	[thread overview]
Message-ID: <20170718133103.GC2151@aepfle.de> (raw)
In-Reply-To: <20170718092304.GA26116@notk.org>

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

On Tue, Jul 18, Adrien Nader wrote:

> 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.

It was not meant to be rude or demanding. Sorry for that.

> 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.

It seems labltk is the only package which makes use of BYTECC/NATIVECC.
So in this context cc7ad5650a is correct.

I was hoping labltk.git#master would just work with "every" ocaml
version. But now #master works with none.

As noted in other replies, there is an issue open at github. Hopefully
it gets sorted out at some point.


Olaf

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-07-18 13:31 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 [this message]
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=20170718133103.GC2151@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=adrien@notk.org \
    --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).