public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin-apps@cygwin.com
Subject: Re: [ATTN MAINTAINER] tig
Date: Fri, 13 Jan 2023 19:40:14 +0000	[thread overview]
Message-ID: <20230113194014.xmulbdfwq7i6ckjt@lucy.dinwoodie.org> (raw)
In-Reply-To: <042b420c-366b-a652-4f20-fcffbacc8bae@seznam.cz>

On Fri, Jan 13, 2023 at 06:06:22PM +0100, Libor Ukropec via Cygwin-apps wrote:
> Dne 13.01.2023 v 17:59 Libor Ukropec via Cygwin-apps napsal(a):
> > Dne 10.01.2023 v 15:04 Jari Aalto via Cygwin-apps napsal(a):
> > 
> > > 
> > > Hi, Thanks for the heads up. I've uploaded new version and added the
> > > *.cygport in my Github repository of tig for possible new maintainer
> > > in the future.
> > > 
> > > The patches deal some fixes in the xmlto(1) of manual pages build.
> > > 
> > > Jari
> > > 
> > Hi Jari,
> > 
> > I updated to the latest tig, but when executing, it complains about
> > missing dependency, but recently I saw many updates to the cygwin
> > packages. Any idea if other package was broken, or tig is missing some
> > dependency in the metadata?
> > 
> > C:/cygwin64/bin/tig.exe: error while loading shared libraries:
> > cygpcreposix-0.dll: cannot open shared object file: No such file or
> > directory
> > 
> > Manual installation of "libpcreposix0 8.45-1" seems resolving the problem.
> > 
> > Libor
> > 
> Problem lies somewhere in the compile process?
> here is my output for tig I compiled few weeks ago:
> 
> $ ldd ./ttiigg/tig-2.5.4-1.x86_64/build/src/tig.exe
>         ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffe86590000)
>         KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ffe85160000)
>         KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ffe839e0000)
>         cygwin1.dll => /usr/bin/cygwin1.dll (0x7ffe416d0000)
>         cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x5461d0000)
>         cygncursesw-10.dll => /usr/bin/cygncursesw-10.dll (0x48ca30000)
> 
> 
> and here is from the installed:
> $ ldd /usr/bin/tig.exe
>         ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffe86590000)
>         KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ffe85160000)
>         KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ffe839e0000)
>         cygwin1.dll => /usr/bin/cygwin1.dll (0x7ffe416d0000)
>         cygncursesw-10.dll => /usr/bin/cygncursesw-10.dll (0x48ca30000)
>         cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x5461d0000)
>         cygpcre-1.dll => /usr/bin/cygpcre-1.dll (0x3fd630000)
>         cygreadline7.dll => /usr/bin/cygreadline7.dll (0x579cd0000)
>         cygpcreposix-0.dll => /usr/bin/cygpcreposix-0.dll (0x520b40000)

I strongly suspect that, like git, tig will use libpcre if it was
present at compile time, and won't if it isn't.  Typically I'd expect
distribution builds to include libpcre support for this sort of thing.
That would mean Jari's compilation was correct, but the .hint files
didn't correctly list the necessary dependencies.

Jari, your email mentioned a possible new maintainer; are you intending
to hand over responsibility, or do you just mean for a hypothetical
future maintainer at some point in the future?

  parent reply	other threads:[~2023-01-13 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11 22:15 Libor Ukropec
2022-12-12 16:32 ` Adam Dinwoodie
2022-12-13 17:14   ` Libor Ukropec
2022-12-13 18:32     ` Adam Dinwoodie
2022-12-13 22:05       ` Libor Ukropec
2023-01-10 14:04     ` Jari Aalto
2023-01-13 16:59       ` Libor Ukropec
2023-01-13 17:06         ` Libor Ukropec
2023-01-13 19:23           ` Brian Inglis
2023-01-13 19:40           ` Adam Dinwoodie [this message]
2023-01-16 12:42         ` Jon Turney
2023-01-25 11:41           ` Jari Aalto

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=20230113194014.xmulbdfwq7i6ckjt@lucy.dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=cygwin-apps@cygwin.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).