unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Adam Faiz <adam.faiz@disroot.org>, 56584@debbugs.gnu.org
Cc: maxim.cournoyer@gmail.com
Subject: bug#56584: vala build uses bundled bootstrap binaries
Date: Wed, 01 Mar 2023 21:59:38 +0100	[thread overview]
Message-ID: <58613c216729af92e868bac39925fe8e01628bf3.camel@gmail.com> (raw)
In-Reply-To: <c2796eee-73ed-bd99-56d2-70e5c8193bc7@disroot.org>

Am Mittwoch, dem 01.03.2023 um 05:00 +0000 schrieb Adam Faiz:
> > Looking at the vala source code, we can bootstrap the current
> > version from 0.39.5.8, which appears to be between release cycles –
> > 0.39.6 already requires it, whereas 0.39.5 bootstraps from 0.25.1. 
> > I'm not sure how to get 0.25.1 to build from source, though.  The
> > code in vala-bootstrap does not appear helpful, it in fact reads
> > exactly like Vala-compiled Vala.
> > 
> > Cheers
> 
> > I've now hosted my own vala-bootstrap [1], which has valacompiler.c
> > and gee translated to more readable C already.  I'd be happy to
> > take in patches or transfer it to the bootstrappable project.
> > 
> > Cheers
> > 
> > [1] https://gitlab.gnome.org/lilyp/vala-bootstrap
> 
> An easier route to bootstrap Vala could be the archeological
> approach:
> 
> Oldest commit(SVN import): 68f95ffe3aef82aac0fb7bbc65d1faab19902e3c
> Last commit with only C code(except for tests written in Vala): 
> c300d9c3d0af08f628b6c260bdd32f431a47e0f2
> 
> Became self-hosting(it still bootstraps with written C code under
> valac/): 
> 29a1dec53a4661779cc819ede69732c6c1118088
> 
> Removed bootstrappability(removed valac/ directory and uses Vala-
> generated C code under ccode/):
> 35bd6909ba2b8467ba95dfe6360e7a7e227115c8
> 
> Oldest release: VALA_0_0_1
> 
> This information should make it possible to bootstrap Vala.
Provided that we find a version of yacc that doesn't choke on the
grammar files.  Also, we got an uncertain road ahead for Valas before
0.35.1, and then vala 0.39.6 did a dirty bump in which they rely on a
practically unreleased version.

So yes, the archeological approach could work, but I wouldn't
necessarily count on it being "easy".

Cheers




      reply	other threads:[~2023-03-01 21:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 21:32 bug#56584: vala build uses bundled bootstrap binaries Maxim Cournoyer
2022-07-16  8:18 ` Liliana Marie Prikler
2023-02-18  7:34   ` Liliana Marie Prikler
2023-02-25 20:12     ` Maxim Cournoyer
2023-03-01  5:00 ` Adam Faiz via Bug reports for GNU Guix
2023-03-01 20:59   ` Liliana Marie Prikler [this message]

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=58613c216729af92e868bac39925fe8e01628bf3.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=56584@debbugs.gnu.org \
    --cc=adam.faiz@disroot.org \
    --cc=maxim.cournoyer@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).