From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] libiconv-1.16-1, libiconv2-1.16, libcharset1-1.16-1
Date: Sun, 12 Jul 2020 18:16:01 -0400 [thread overview]
Message-ID: <c1bec58fa60a964b6832f32966af462e10a9ca84.camel@cygwin.com> (raw)
In-Reply-To: <f2a20436-3373-d7be-eb6b-41dbae2bcd43@gmail.com>
On Sat, 2020-07-11 at 19:45 +0200, Marco Atzeri via Cygwin-apps wrote:
> On 11.07.2020 04:03, Lemures Lemniscati via Cygwin-apps wrote:
> > Hi!
> >
> > I suggest an update to libiconv 1.16, since the current Cygwin
> > packages of libiconv 1.14 are old (updated 5 years ago).
> >
> > Cygport files are forked
> > to https://github.com/cygwin-lem/libiconv-cygport/tree/w_1.16
> > from http://cygwin.com/git/cygwin-packages/libiconv .
> >
> >
> > New test package files are placed here:
> > https://cygwin-lem.github.io/libiconv-cygport/index.html .
> >
> > Please, check them:
>
> Looks good to me
>
> except the build of static import libraries
>
> usr/lib/libcharset.a
> usr/lib/libiconv.a
>
> I will stick to only:
> usr/lib/libcharset.dll.a
> usr/lib/libiconv.dll.a
Static libiconv is used when building Cygwin dumper.exe (as a
dependency of libbfd.a, which is static only). Therefore it should be
present. Note that my .cygport has an explicit --enable-static, which
should have indicated that this was deliberate.
--
Yaakov
prev parent reply other threads:[~2020-07-12 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 2:03 Lemures Lemniscati
2020-07-11 17:45 ` Marco Atzeri
2020-07-11 22:01 ` Lemures Lemniscati
2020-07-18 8:29 ` Achim Gratz
2020-07-18 10:34 ` Lemures Lemniscati
2020-07-18 10:45 ` Achim Gratz
2020-07-18 11:18 ` Lemures Lemniscati
2020-07-30 19:38 ` Lemures Lemniscati
2020-07-31 4:22 ` Marco Atzeri
2020-08-01 4:18 ` Lemures Lemniscati
2020-07-12 22:16 ` Yaakov Selkowitz [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=c1bec58fa60a964b6832f32966af462e10a9ca84.camel@cygwin.com \
--to=yselkowitz@cygwin.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).