unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Thompson, David" <dthompson2@worcester.edu>,
	guile-devel@gnu.org, "Rob Browning" <rlb@defaultvalue.org>,
	"Aleix Conchillo Flaqué" <aconchillo@gmail.com>,
	"Greg Troxel" <gdt@lexort.com>
Subject: Re: GNU Guile 3.0.9rc1 available for testing!
Date: Mon, 23 Jan 2023 14:23:53 +0100	[thread overview]
Message-ID: <87a629v0ye.fsf@gnu.org> (raw)
In-Reply-To: <87pmb53532.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 23 Jan 2023 11:42:09 +0100")

Ludovic Courtès writes:

Hi Ludo,

> Jan Nieuwenhuizen <janneke@gnu.org> skribis:
>
>> Yeah, you need at least
>>
>>     76950b428 Support for x86_64-w64-mingw32.
>>
>> or something similar, or another approach for addressing the
>> SIZEOF_LONG==4 issue on MinGW.
>
> Oh sorry, I had completely overlooked that patch (and branch).

No problem.  Mike has been looking into this as well.  Also, there are
commits that should probably be squashed into this, such as

    9a29293a8 More long integer fixes for x86_64-w64-mingw32
    46bb667f2 MinGW 64: fixes hash out-of-range error for 64-bit negative numbers

> I’m hesitant about applying it at this late stage, also because I
> haven’t thought about the possible choices and implications.  Maybe this
> will have to wait until the next round (bah!)?

Yeah, that seems wise.

Also there is still an unresolved problem with file-name-convention.

We probably want

    2d82b49cf mingw: canonicalize-path: Also canonicalize drive letter and '/'.

Also, during a (cross)build, file-name-convention from build host is
used/assumed.  I tried to creat a fix

   9bfd0b544 squash! Fix 'absolute-file-name?' and others for cross-build to MinGW.
   96597fa21 Fix 'absolute-file-name?' and others for cross-build to MinGW.

but iirc, Mike found a problem with these.  Hairy stuff.

>> And compile with --disable-jit, AFAIK nobody got that to work just
>> yet.
>
> OK.
>
> Thanks for the heads-up!

You're welcome, it's great that guile at least builds with MintGW now.

Greetings,
Janneke

-- 
Janneke Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com




  reply	other threads:[~2023-01-23 13:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 15:58 GNU Guile 3.0.9rc1 available for testing! Ludovic Courtès
2023-01-20 16:18 ` Thompson, David
2023-01-21 14:58   ` Jan Nieuwenhuizen
2023-01-23 10:42     ` Ludovic Courtès
2023-01-23 13:23       ` Janneke Nieuwenhuizen [this message]
2023-01-20 17:50 ` Aleix Conchillo Flaqué
2023-01-23 10:45   ` Ludovic Courtès
2023-01-23 17:01     ` Aleix Conchillo Flaqué
2023-01-22  2:12 ` Greg Troxel
2023-01-22 14:30   ` lloda
2023-01-22 14:39     ` Greg Troxel
2023-01-23 10:48       ` Ludovic Courtès
2023-01-23 18:04         ` lloda
2023-01-23 21:59           ` bug#60971: build failure of v3.0.9rc1 on mac os 12.6 Ludovic Courtès
2023-01-23 18:47         ` GNU Guile 3.0.9rc1 available for testing! Aleix Conchillo Flaqué
2023-01-25  1:44         ` Greg Troxel
2023-01-25 10:32           ` Ludovic Courtès
2023-01-22 17:41   ` Greg Troxel
2023-01-22 23:10     ` Greg Troxel
2023-01-23 11:02       ` Ludovic Courtès
2023-01-23 11:19     ` Ludovic Courtès
2023-01-24 15:43       ` Greg Troxel

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a629v0ye.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=aconchillo@gmail.com \
    --cc=dthompson2@worcester.edu \
    --cc=gdt@lexort.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=rlb@defaultvalue.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.
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).