bug#34453: closed ([PATCH] build guile-static with guile-2.0)

[GNU bug Tracking System]

Your message dated Thu, 23 Jun 2022 10:14:42 +0200
with message-id <86wnd794p9.fsf_-_@gmail.com>
and subject line Re: bug#34453: [PATCH] build guile-static with guile-2.0
has caused the debbugs.gnu.org bug report #34453,
regarding [PATCH] build guile-static with guile-2.0
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
34453: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34453
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: [PATCH] build guile-static with guile-2.0 Date: Tue, 12 Feb 2019 11:17:40 +0200 User-agent: Mutt/1.11.2 (2019-01-07)

When experimenting I found that using guile@2.0 as a base for
guile-static, the resulting guile-static didn't segfault on the target
architecture.


-- 
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

0001-gnu-guile-static-Build-for-guile-2.0.patch
Description: Text document

signature.asc
Description: PGP signature

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#34453: [PATCH] build guile-static with guile-2.0
>
>
>
>
> Date: 
>
> Thu, 23 Jun 2022 10:14:42 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
>
>
>
>
> Hi,
>
> On Thu, 14 Apr 2022 at 00:07, Efraim Flashner <efraim@flashner.co.il> wrote:
> > On Tue, Apr 12, 2022 at 12:10:09PM +0200, zimoun wrote:
> >> On Sat, 16 Feb 2019 at 17:06, Ludovic Courtès <ludo@gnu.org> wrote:
> >> > Efraim Flashner <efraim@flashner.co.il> skribis:
>
> >> > As discussed in <https://issues.guix.info/issue/34427>, I would rather
> >> > fix the segfault in 2.2 than move back to 2.0 and effectively delay the
> >> > problem.
> >>
> >> Note that #34427 is still open.
> >
> > We can probably drop it. We'll pick it back up again if/when it comes up
> > again.
>
> Therefore, I am closing.
>
>
> Cheers,
> simon
>
>
> --- End Message ---