From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] libexif-0.6.22-1
Date: Thu, 31 Dec 2020 18:32:37 +0900 [thread overview]
Message-ID: <20201231183235.4EB9.50F79699@gmail.com> (raw)
In-Reply-To: <87a6tupdgi.fsf@Rainer.invalid>
On Thu, 31 Dec 2020 09:49:33 +0100, Achim Gratz
> Achim Gratz writes:
> > # Work around a libpopt-devel-1.16-2 packaging issue that causes the error:
> > # libtool: error: cannot find the library '/usr/lib/libintl.la' or unhandled argument '/usr/lib/libintl.la'
> > # See http://www.cygwin.com/ml/cygwin-apps/2017-07/msg00005.html
> > - cmd: if [%CONFIG%]==[cygwin] (
> > C:\%CONFIG%\bin\bash -e -l -c "rm /usr/lib/libpopt.la" )
> >
> > …and indeed that makes things work. :-)
>
> This is the reason it works on the CI:
>
> curl -fsSL https://gist.githubusercontent.com/jon-turney/0338af595313f598bfab15a0ac0df847/raw/bd0eeca6be899e7846aa988fbcf15e4e12f5f842/zp_libtool_cleanlafiles.sh -o %CYGWIN_ROOT%\etc\postinstall\zp_libtool_cleanlafiles.sh
>
> --8<---------------cut here---------------start------------->8---
> rmla=()
> for la in $(find /usr/lib/ -maxdepth 1 -name '*.la')
> do
> # modules in /usr/lib (e.g. aRts, guile) are generally libltdl-based
> if grep -q '^shouldnotlink=yes$' $la
> then
> continue
> fi
> case ${la##*/} in
> # ltdl.m4 requires this to be present
> libltdl.la) continue ;;
> # gnucash relies on .la loading due to the 'cyg' prefix
> libgnc-*.la) continue ;;
> esac
>
> rmla+=($la)
> done
>
> rm -f ${rmla[*]}
> --8<---------------cut here---------------end--------------->8---
>
>
>
> Regards,
> Achim.
Thank you very much!
It works like a magic.
libpopt-devel-1.16-2 for x86 has /usr/lib/libpopt.la
$ uname -srm; cygcheck -c libpopt-devel; cygcheck -l libpopt-devel
CYGWIN_NT-10.0-WOW 3.1.7(0.340/5/3) i686
Cygwin Package Information
Package Version Status
libpopt-devel 1.16-2 Incomplete
/usr/include/popt.h
/usr/lib/libpopt.dll.a
/usr/lib/libpopt.la
/usr/lib/pkgconfig/popt.pc
/usr/share/man/man3/popt.3.gz
Regards,
Lem
P.S. By the way, I'm also planning to package popt :)
next prev parent reply other threads:[~2020-12-31 9:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 23:33 Lemures Lemniscati
2020-12-31 2:07 ` Lemures Lemniscati
2020-12-31 8:04 ` Lemures Lemniscati
2020-12-31 8:44 ` Achim Gratz
2020-12-31 8:49 ` Achim Gratz
2020-12-31 9:32 ` Lemures Lemniscati [this message]
2020-12-31 10:54 ` Lemures Lemniscati
2020-12-31 15:44 ` Marco Atzeri
2020-12-31 22:22 ` Lemures Lemniscati
2021-01-02 22:13 ` Achim Gratz
2021-01-03 2:46 ` Lemures Lemniscati
2021-01-03 3:22 ` Marco Atzeri
2021-01-03 9:51 ` Achim Gratz
2021-01-04 13:58 ` Lemures Lemniscati
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=20201231183235.4EB9.50F79699@gmail.com \
--to=lemures.lemniscati@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).