Subject: bug#64708: closed (Re: bug#64708: [PATCH 0/8] Fix cross build and native build for the Hurd.)

From: [email-masked] (GNU bug Tracking System)
Date: Wed, 19 Jul 2023 05:54:02 +0000

Your bug report

#64708: [PATCH 0/8] Fix cross build and native build for the Hurd.

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
64708: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64708
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#64708: [PATCH 0/8] Fix cross build and native build for the Hurd.
From: Janneke Nieuwenhuizen <[email-masked]>
To: Ludovic Courtès <[email-masked]>
Cc: [email-masked]
Date: Wed, 19 Jul 2023 07:53:24 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Ludovic Courtès writes:

Hello,

> Janneke Nieuwenhuizen <[email-masked]> skribis:
>
>> The versions of gnumach-headers-boot0, mig-boot0, and hurd-headers-boot0 are
>> updated so that native builds work again.  Because upstream does not produce
>> release tarballs we now also need autoconf and automake in commencement.
>
> I sent minor suggestions, but overall LGTM!
>
> As of 4e11cac6be68a674c16965dc74e7da54cd3168df, we have
> cross-compilation to i586-pc-gnu working again.

That's right, someone beat me to it ;-) (thanks!!)

> After this series, we should still have that + ‘-s i586-gnu’ (native
> compilation) working (modulo test failures fixed by
> <https://issues.guix.gnu.org/64711>, of course).  I haven’t checked
> whether this is the case but that’s the idea, right?  :-)

Certainly!

> Thanks again for this!

That's always good to hear.

Pushed to master as 8831d3ba9f799b7342ab466d625097f1982513a9

Greetings,
Janneke

-- 
Janneke Nieuwenhuizen <[email-masked]>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com

Subject: [PATCH 0/8] Fix cross build and native build for the Hurd.
From: Janneke Nieuwenhuizen <[email-masked]>
To: [email-masked]
Date: Tue, 18 Jul 2023 15:11:52 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Hi!

So...updating mig using git-fetch created a circular dependency because
mig-boot0 re-used mig's source, and we cannot use git in commencement.

This patch series now uses a hack by Ludo (thanks!) as suggested on IRC
<https://logs.guix.gnu.org/guix/2023-07-17.log#233051> to not directly use
generated cgit tarballs from savannah.

The versions of gnumach-headers-boot0, mig-boot0, and hurd-headers-boot0 are
updated so that native builds work again.  Because upstream does not produce
release tarballs we now also need autoconf and automake in commencement.

Note that building natively won't get very far, as for many packages (guile,
coreutils, grep, findutils, diffutils, gettext-minimal, m4, openssl, python,
...) the `check' phase will fail.  See the `hurd-team' branch for updates on
this.

Now that mig-boot0 uses its own source definition, we can safely re-apply the
mig update.

Greetings,
Janneke

Janneke Nieuwenhuizen (6):
  gnu: commencement: Add autoconf-boot0.
  gnu: commencement: Add automake-boot0.
  gnu: commencement: gnumach-headers-boot0: Update to 1.8+git20221224.
  gnu: commencement: mig-boot0: Update to 1.8+git20230520.
  gnu: commencement: hurd-headers-boot0: Update to 0.9.git20230216.
  gnu: commencement: hurd-minimal-boot0: Update to 0.9.git20230216.

Josselin Poiret (1):
  gnu: mig: Update to 1.8+git20230520.

Ludovic Courtès (1):
  gnu: commencement: Add git-fetch-from-tarball utility.

 gnu/packages/commencement.scm | 200 ++++++++++++++++++++++++++--------
 gnu/packages/hurd.scm         |  20 ++--
 2 files changed, 160 insertions(+), 60 deletions(-)

base-commit: 94f83088d237ecd032c411bb94e2d647a2931990
-- 
2.40.1