From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: cygport install infinite loop in src_postinstall under __prep_libtool_modules
Date: Sat, 4 Jul 2020 22:06:49 +0200 [thread overview]
Message-ID: <9e5761e2-0488-f83d-a43d-57a6e9a5419f@gmail.com> (raw)
In-Reply-To: <359290a2-b299-ad90-5083-30789099a3eb@SystematicSw.ab.ca>
On 04.07.2020 21:35, Brian Inglis wrote:
> See attached cygport --debug ...cygport install log.
>
> Running cygport ... install, src_postinstall under __prep_libtool_modules after
> "Fixing libtool modules:" does not find dll in:
>
> $ find wget2-1.99.2-1.x86_64/ -name 'cygwget*'
> wget2-1.99.2-1.x86_64/build/libwget/.libs/cygwget-0.dll
> wget2-1.99.2-1.x86_64/inst/usr/bin/cygwget-0.dll
>
> so it loops on /usr/share/cygport/lib/src_postinst.cygpart:1297ff:
>
> while [ $(readlink -f ${ltlibdir}/${dlname%/bin/*}) != ${D}$(__host_prefix) ]
> do
> dlname=../${dlname}
> done
>
> until readlink returns root and just keeps on going, possibly because my Cygwin
> home is a symlink to my Windows home, but this approach would have problems with
> any symlinks along the path to the cygport dir, as $D is not similarly resolved.
>
> I can wrap the other path in the condition in $(readlink -f ...) and it works
> normally but this may not be the best approach here.
> Alternatives, suggestions?
>
> In this pre-package there is a check/test program and a DLL - is there another
> package I could use as a template for how to split this into two packages?
>
I assume you are building under some link structure.
I was hit by long time by it as I was using
/pub -> /cygdrive/d/cyg_pub
and building in it.
Two options:
1) patch cygport
I proposed something for that case
https://sourceware.org/pipermail/cygwin-apps/2020-April/039990.html
2) mount the directory instead of using links.
I put this in my fstab and removed the link
d:\cyg_pub /pub NTFS binary,posix=1,nouser 0 0
Regards
Marco
next prev parent reply other threads:[~2020-07-04 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 19:35 Brian Inglis
2020-07-04 20:06 ` Marco Atzeri [this message]
2020-07-05 19:29 ` Brian Inglis
2020-07-05 5:27 ` ASSI
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=9e5761e2-0488-f83d-a43d-57a6e9a5419f@gmail.com \
--to=marco.atzeri@gmail.com \
--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).