git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] Makefile: fix cygwin build failure
Date: Thu, 10 Nov 2022 20:35:56 +0000	[thread overview]
Message-ID: <CA+kUOan=Dj4T7J57yJSg2Qh4+SQuCV0MOLKxQrZC6s1=ciOdNw@mail.gmail.com> (raw)
In-Reply-To: <0dec6e1e-207c-be13-ae95-294d9b1e8831@ramsayjones.plus.com>

On Wed, 9 Nov 2022 at 22:46, Ramsay Jones wrote:
> <snip>
> [1] After a cygwin update, '/usr/bin/msgfmt.exe' refused to run, saying
> that it could not locate the 'cygunistring-5.dll' file. Using cygcheck,
> I found that this dll is provided by the 'libunistring5 1.1-1' package.
> After installing this package, everything works just fine.
>
> I don't know how package dependencies are specified/updated, but it
> would seem the 'gettext-devel' package has a direct or indirect
> dependency on the 'libunistring5' package. Looking at my setup.log file
> I would guess one-or-more of the following packages needs an update to
> note this dependency: 'gettext-devel 0.21.1-1', 'gettext 0.21.1-1',
> 'libgettextpo0 0.21.1-1', 'libintl-devel 0.21.1-1', 'libintl8 0.21.1-1',
> or 'libasprintf0 0.21.1-1'.
>
> Unfortunately, I am not subscribed to the cygwin mailinglist :(

It looks like this was broken by an update to some of these packages a
couple of weeks ago[0]; I've reproduced the problem and reported it to
the mailing list[1], so the package maintainer should be able to
update the dependency information :)

[0]: https://cygwin.com/pipermail/cygwin-announce/2022-October/010764.html
[1]: https://cygwin.com/pipermail/cygwin/2022-November/252445.html

      parent reply	other threads:[~2022-11-10 20:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 22:46 [PATCH] Makefile: fix cygwin build failure Ramsay Jones
2022-11-09 22:58 ` Taylor Blau
2022-11-09 23:18   ` Ævar Arnfjörð Bjarmason
2022-11-10  2:20     ` Taylor Blau
2022-11-10  2:21       ` Taylor Blau
2022-11-10  2:22         ` Taylor Blau
2022-11-22  1:54           ` Ramsay Jones
2022-11-22  2:02           ` Junio C Hamano
2022-11-10 20:35 ` Adam Dinwoodie [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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CA+kUOan=Dj4T7J57yJSg2Qh4+SQuCV0MOLKxQrZC6s1=ciOdNw@mail.gmail.com' \
    --to=adam@dinwoodie.org \
    --cc=git@vger.kernel.org \
    --cc=ramsay@ramsayjones.plus.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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