public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: Mike Gran <spk121@yahoo.com>
Subject: Re: [ANNOUNCEMENT] Updated: guile-3.0.9-2
Date: Thu, 1 Jun 2023 00:05:39 -0600	[thread overview]
Message-ID: <858b04a8-f344-cafa-c837-4201337d5752@Shaw.ca> (raw)
In-Reply-To: <1655626221.2764790.1685583918500@mail.yahoo.com>

On 2023-05-31 19:45, Mike Gran wrote:
> On Saturday, May 13, 2023 at 11:40:01 PM PDT, Marco Atzeri wrote:
>> Version 3.0.9-2 of
>>     guile3.0
>>     libguile3.0-devel
>>     libguile3.0_1
>> have been uploaded for cygwin.

> Where can I find the source patches that Cygwin uses for guile3.0?

Inside the source package which includes the cygport package build script 
definitions plus any patches or custom files or build scripts if required:
install the source package using the Cygwin Setup program setup-x86_64 or 
download it from your local mirror path as

	https://.../x86_64/release/guile3.0/guile3.0-V-R-src.tar.*z*

e.g.

https://mirrors.kernel.org/sourceware/cygwin/x86_64/release/guile3.0/guile3.0-3.0.9-2-src.tar.xz

Extract it, change to the extracted directory, then run:

	$ cygport guile3.0.cygport get all check

possibly in the background, with redirections to logs, and/or nohup.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

      parent reply	other threads:[~2023-06-01  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-14  6:38 Marco Atzeri via Cygwin-announce
2023-06-01  1:45 ` Mike Gran
2023-06-01  5:51   ` Marco Atzeri
2023-06-01 13:52     ` Mike Gran
2023-06-01  6:05   ` Brian Inglis [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=858b04a8-f344-cafa-c837-4201337d5752@Shaw.ca \
    --to=brian.inglis@shaw.ca \
    --cc=cygwin@cygwin.com \
    --cc=spk121@yahoo.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).