unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: pukkamustard <pukkamustard@posteo.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 52729@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#52729] [PATCH v2] gnu: ocaml: Update to 4.13.
Date: Sat, 08 Jan 2022 20:45:45 +0000	[thread overview]
Message-ID: <86czl1garh.fsf@posteo.net> (raw)
In-Reply-To: <20211223140109.7716a446@tachikoma.lepiller.eu>


Hi Julien,

> gnu: ocaml-ppx-tools-versioned: Only build ocaml-4.07 variant.

Any reason for not using the package-with-ocaml4.07 transformation?

> gnu: ocaml: Update to 4.13.

js-of-ocaml and ocaml-dot-merlin-reader are also updated in this
commit. Could they be split to separate commits?

Other than that everything seems to be compiling and working
fine. Thank you very much!

-pukkamustard


Julien Lepiller <julien@lepiller.eu> writes:

> Le Wed, 22 Dec 2021 14:51:49 +0100,
> zimoun <zimon.toutoune@gmail.com> a écrit :
>
>> Hi,
>> 
>> On Wed, 22 Dec 2021 at 14:43, Julien Lepiller <julien@lepiller.eu>
>> wrote:
>> 
>> > >On a side note, have you tried to replace boot/ocamlc (and
>> > >friends) with the bootstrapped ones (camlboot -> ocaml-4.07 -> *).
>> > > Other said, what is the most affordable path to exploit camlboot
>> > > and have a good
>> > >bootstrapping story for OCaml.  
>> >
>> > Currently we can only use camlboot to bootstrap ocaml 4.07, which
>> > is what we do. We plan to improve it so it can build newer versions
>> > though.  
>> 
>> Yes, I remember when discussing the patch adding camlboot and
>> ocaml4.07-boot. :-)  That's what you explained [1].
>> 
>> Well, a direct bootstrap camlboot -> ocaml-4.13 is better for sure,
>> but harder.  Instead, my question is: have you tried a chain of
>> boostrap: camlboot -> ocaml-4.07 -> ? -> ocaml-4.13.  I could be
>> temporary solution waiting camlboot improvements, no?
>> 
>> 1: <https://issues.guix.gnu.org/46806#11>
>> 
>> 
>> Cheers,
>> simon
>
> Here's v2 of the patch series: the first two patches build only the
> 4.07 version for migrate-parsetree@1 and for ppx-tools-versioned. That
> way, they don't fail when updating to ocaml 4.13. I checked that
> everything builds like before. I still have issues with bap because
> llvm@3.8.1 fails.
>
> [2. text/x-patch; 0001-gnu-ocaml-ppx-tools-versioned-Only-build-ocaml-4.07-.patch]...
>
> [3. text/x-patch; 0002-gnu-ocaml-migrate-parstree-1-Only-build-ocaml4.07-va.patch]...
>
> [4. text/x-patch; 0003-gnu-ocaml-Update-to-4.13.patch]...





  reply	other threads:[~2022-01-08 21:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22  3:16 [bug#52729] [PATCH] gnu: ocaml: Update to 4.13 Julien Lepiller
2021-12-22 13:33 ` zimoun
2021-12-22 13:43   ` Julien Lepiller
2021-12-22 13:51     ` zimoun
2021-12-23 13:01       ` [bug#52729] [PATCH v2] " Julien Lepiller
2022-01-08 20:45         ` pukkamustard [this message]
2022-01-09  9:55           ` bug#52729: " Julien Lepiller

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86czl1garh.fsf@posteo.net \
    --to=pukkamustard@posteo.net \
    --cc=52729@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=zimon.toutoune@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).