all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: dftxbs3e <dftxbs3e@free.fr>
Cc: guix-devel@gnu.org
Subject: Re: bootstrap guile version mismatch on core-updates
Date: Mon, 12 Aug 2019 11:19:03 +0300	[thread overview]
Message-ID: <20190812081903.GA8000@E2140> (raw)
In-Reply-To: <2b8438ce-750a-b16e-c197-ced535359a0b@free.fr>

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

On Sat, Aug 10, 2019 at 04:12:00PM +0200, dftxbs3e wrote:
> Hello,
> 
> It seems that guile2.2 is built by make-bootstrap.scm here:
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/make-bootstrap.scm?h=core-updates#n625
> 
> but guile2.0 is expected here:
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/bootstrap.scm?h=core-updates#n373
> 
> For the purpose of my ongoing port to powerpc64le-linux-gnu, I applied
> the attached patch, but obviously that one wont work with the previously
> built tarballs for x86_64 etc. Things would have to be split in parts
> somehow, for old bootstraps with version 2.0 and newer ones with version
> 2.2.
> 
> Thanks
> 

I had a similar issue with grep vs egrep/fgrep when I was porting
aarch64. My suggestion is to "make unilateral changes" to the source
where necessary to make the bootstrap work and then return to it later
and clean it up so it doesn't break all the other architectures.

If you do want to hack at it now, the two things I can think of
immediately are '(version-major+minor (package-version %bootstrap-guile))'
to see if it's 2.0.x or 2.2.x, or %target-system, which I found to be a
bit harder to work with that early in the bootstrap process.

I don't have my 32-bit PPC machine out or I could check to see what I
tried on that machine, but I think I just changed it to 2.2 and figured
I'd come back to it later.


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

  reply	other threads:[~2019-08-12  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-10 14:12 bootstrap guile version mismatch on core-updates dftxbs3e
2019-08-12  8:19 ` Efraim Flashner [this message]
2019-08-26 10:27 ` Ludovic Courtès

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=20190812081903.GA8000@E2140 \
    --to=efraim@flashner.co.il \
    --cc=dftxbs3e@free.fr \
    --cc=guix-devel@gnu.org \
    /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.