public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Marco Atzeri <marco.atzeri@gmail.com>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: guile-3.0.9-1
Date: Wed, 17 May 2023 21:30:34 +0100	[thread overview]
Message-ID: <3238bd8e-9af3-acf5-91ea-e479534984ee@dronecode.org.uk> (raw)
In-Reply-To: <c7fac207-fa19-f07d-e2ad-03203b1bfe8d@gmail.com>

On 13/05/2023 20:55, Marco Atzeri via Cygwin wrote:
> On 09.05.2023 22:26, marco atzeri wrote:
>> On Tue, May 9, 2023 at 7:25 PM Achim Gratz via Cygwin wrote:
>>>
>>> Jon Turney via Cygwin writes:
>>>> This update seems to break guile-config somehow:
>>>>
>>>>> $ guile-config --version
>>>>> error: ("/usr/bin/pkg-config" "--modversion" "guile-3.0") exited 
>>>>> with non-zero error code 127
>>>
>>> Confirmed.
>>>
>>> That would be ENOEXEC, so it looks like the quotes shown in the rerror
>>> message are somehow actually going into the exec call.  Since one of the
>>> changes in this version is to use spawn_posix instead of execle, I'd
>>> start to look there.
>>>
>>>
>>> Regards,
>>> Achim.
>>
>> Noted. I can look on it during weekend
> 
> 3.0.9-2 is on the way.
> 
>    $ guile-config --version
>    guile-config - Guile version 3.0.9
> 
> it was a upstream bug that impacted also other not-Linux platform
> 

Great! Works fine now. Thanks very much.


      reply	other threads:[~2023-05-17 20:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18 14:12 Marco Atzeri via Cygwin-announce
2023-05-08 19:16 ` Jon Turney
2023-05-09 17:24   ` Achim Gratz
2023-05-09 20:26     ` marco atzeri
2023-05-13 19:55       ` Marco Atzeri
2023-05-17 20:30         ` Jon Turney [this message]

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=3238bd8e-9af3-acf5-91ea-e479534984ee@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    /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).