all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 46806@debbugs.gnu.org
Subject: [bug#46806] [PATCH] gnu: ocaml-4.07: Bootstrap.
Date: Wed, 3 Mar 2021 15:05:18 +0100	[thread overview]
Message-ID: <CAJ3okZ1baW4HhinhSK9PhGgkpSeeqv-a2g2h_aONqddDUbjikA@mail.gmail.com> (raw)
In-Reply-To: <5366012A-8041-4277-B6B4-C6709EB2787B@lepiller.eu>

On Wed, 3 Mar 2021 at 14:46, Julien Lepiller <julien@lepiller.eu> wrote:
>
> We'd have to check we actually can build them. The plan was to build menhir with this ocaml4.07, since it's required to generate the parser for ocaml >= 4.08, and improve camlboot to support more recent versions. We would prevent the need for a chain of bootstraps that way.

Thanks for the explanations.
I have tried to replace gcc by clang for camlboot but it fails.
And also tried other Scheme than Guile, obviously fails. :-)


> I don't think ocaml has so many dependants that it requires core-updates. Not even sure it needs staging.

Oh right, I thought that more OCaml packages were in Guix. :-)

Cheers,
simon




  reply	other threads:[~2021-03-03 14:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 23:13 [bug#46806] [PATCH] gnu: ocaml-4.07: Bootstrap Julien Lepiller
2021-02-28  2:09 ` Julien Lepiller
2021-02-28  2:29   ` Julien Lepiller
2021-03-03  0:22     ` zimoun
2021-03-03 12:54     ` zimoun
2021-02-28  9:19 ` pukkamustard
2021-02-28 10:57   ` Julien Lepiller
2021-03-01  9:16     ` pukkamustard
2021-03-01 11:44       ` Julien Lepiller
2021-03-01 12:04         ` pukkamustard
2021-03-03 13:27 ` zimoun
2021-03-03 13:46   ` Julien Lepiller
2021-03-03 14:05     ` zimoun [this message]
2021-03-03 16:14       ` bug#46806: " 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

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

  git send-email \
    --in-reply-to=CAJ3okZ1baW4HhinhSK9PhGgkpSeeqv-a2g2h_aONqddDUbjikA@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=46806@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.