From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: "Stéphane Glondu" <steph@glondu.net>, "caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] removal of C compiler variables in in 4.06
Date: Tue, 18 Jul 2017 09:49:59 -0400 [thread overview]
Message-ID: <CAPFanBEKUz+_SDbEZS_7v5=Q=LAZcqiSAk3uQXN5UaY2m7hB3A@mail.gmail.com> (raw)
In-Reply-To: <20170718134143.GD2151@aepfle.de>
I think that it should not be too hard to use a bash sleight-of-hand
to define a variable as BYTECC if it is defined and CC otherwise (or
the other way around), to get a labltk makefile that works with both.
(The Texp_function change is harder and you may need
version-conditional preprocessing, typically using cppo, to handle
them; this is the price to pay for accessing unstable
compiler-internal definitions.)
Note that labltk is currently hosted on the OCaml Forge, which is due
to be closed soon, so moving to a different place would be required. If
you are interested in labltk and helping its maintenance, you should
contact the current maintainers, who may welcome help for the migration
and the kind of maintenance work this thread is about.
On Tue, Jul 18, 2017 at 9:41 AM, Olaf Hering <olaf@aepfle.de> wrote:
> On Tue, Jul 18, Stéphane Glondu wrote:
>
>> FYI, I've fixed labltk with 4.05 in the Debian package (not yet uploaded):
>> https://anonscm.debian.org/cgit/pkg-ocaml-maint/packages/labltk.git/tree/debian/patches
>
> Thanks, I came up with the same changes, execpt the one for
> "Texp_function".
>
> Olaf
next prev parent reply other threads:[~2017-07-18 13:50 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
2017-07-18 13:41 ` Olaf Hering
2017-07-18 13:49 ` Gabriel Scherer [this message]
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='CAPFanBEKUz+_SDbEZS_7v5=Q=LAZcqiSAk3uQXN5UaY2m7hB3A@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=olaf@aepfle.de \
--cc=steph@glondu.net \
/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