GNU bug report logs - #56516
[PATCH] gnu: tcc: Update to a83b28568596afd8792fd58d1a5bd157fc6b6634

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 56516 in the body.
You can then email your comments to 56516 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ekaitz Zarraga <ekaitz <at> elenq.tech>
To: "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>,
 "guix-devel\\@gnu.org" <guix-devel <at> gnu.org>
Subject: [PATCH] gnu: tcc: Update to a83b28568596afd8792fd58d1a5bd157fc6b6634
Date: Tue, 12 Jul 2022 09:39:30 +0000

[Message part 1 (text/plain, inline)]

Hi,

With this patch the tcc build issue is fixed, the downside is that it's
set to an specific commit and not a release.

It also separates tcc-boot from the tcc source, so it does not interfere
in the bootstrapping process (the patch moves the source of tcc to git
and that produces a circular dependency).

I hope this is useful.

Best,
Ekaitz

[0001-gnu-tcc-Update-to-a83b28568596afd8792fd58d1a5bd157fc.patch (text/x-patch, attachment)]

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Ekaitz Zarraga <ekaitz <at> elenq.tech>
Cc: "guix-devel <at> gnu.org" <guix-devel <at> gnu.org>,
 "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>
Subject: Re: [PATCH] gnu: tcc: Update to
 a83b28568596afd8792fd58d1a5bd157fc6b6634
Date: Mon, 18 Jul 2022 13:23:05 +0200

Egun on!

Ekaitz Zarraga <ekaitz <at> elenq.tech> skribis:

> With this patch the tcc build issue is fixed, the downside is that it's
> set to an specific commit and not a release.

Is it because there’s no newer release?  (I can add a comment to that
effect when committing.)

> It also separates tcc-boot from the tcc source, so it does not interfere
> in the bootstrapping process (the patch moves the source of tcc to git
> and that produces a circular dependency).
>
> I hope this is useful.

It is!

Thanks,
Ludo’.

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ekaitz Zarraga <ekaitz <at> elenq.tech>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: "guix-devel\\@gnu.org" <guix-devel <at> gnu.org>,
 "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>
Subject: Re: [PATCH] gnu: tcc: Update to
 a83b28568596afd8792fd58d1a5bd157fc6b6634
Date: Mon, 18 Jul 2022 11:39:16 +0000

Saluton,

> Egun on!
>
> Ekaitz Zarraga ekaitz <at> elenq.tech skribis:
>
> > With this patch the tcc build issue is fixed, the downside is that it's
> > set to an specific commit and not a release.
>
>
> Is it because there’s no newer release? (I can add a comment to that
> effect when committing.)


They are planning a release because they didn't make any in a very, very long time. But they'll need time until everything is set up.

Ekaitz

Message #16 received at 56516-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Ekaitz Zarraga <ekaitz <at> elenq.tech>
Cc: 56516-done <at> debbugs.gnu.org, "guix-devel <at> gnu.org" <guix-devel <at> gnu.org>
Subject: Re: [PATCH] gnu: tcc: Update to
 a83b28568596afd8792fd58d1a5bd157fc6b6634
Date: Mon, 18 Jul 2022 14:21:28 +0200

Hi,

Ekaitz Zarraga <ekaitz <at> elenq.tech> skribis:

> They are planning a release because they didn't make any in a very, very long time. But they'll need time until everything is set up.

Alright.  I split the patch into two commits, added a comment about the
release, passed it through ‘guix style’, and applied.

Thanks!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.