From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: HEADSUP: gdbm ABI on x86
Date: Mon, 10 Oct 2016 19:55:00 -0000 [thread overview]
Message-ID: <b91b5360-3cda-9925-511c-1544d4577091@cygwin.com> (raw)
Some background:
The version of gdbm in the 32-bit distro was actually ABI 3 but carried
a patch from the previous maintainer to artificially bump it to 4 for
extraneous reasons. The current version of gdbm really is ABI 4
however, and not wanting to carry a patch indefinitely, I had not
updated gdbm since I adopted it. (The 64-bit distro had a newer version
from the beginning and so was unburdened by this historical baggage.)
After closely examining the API changes between 1.8.3 (ABI 3) and 1.9+
(ABI 4) as well as how the library is typically used, I believe they are
sufficiently compatible on 32-bit architectures. Therefore, I have
proceeded to update the x86 gdbm to finally match the current upstream
(and our x86_64 package), but strongly recommend that packages which use
gdbm be rebuilt with libgdbm-devel-1.12-1 ASAP to be safe.
Besides my own packages, the following are affected:
clisp Ken Brown
exim Pierre A. Humblet
libaprutil1 David Rothenberger
mutt Marco Atzeri
nmh David Levine
perl Achim Gratz
qsf Jari Aalto
suck Jari Aalto
zsh Peter A. Castro
TIA,
--
Yaakov
next reply other threads:[~2016-10-10 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 19:55 Yaakov Selkowitz [this message]
2016-10-11 15:50 ` HEADSUP: gdbm ABI on x86 (DONE qsf suck - rebuilt and uploaded) Jari Aalto
2016-10-11 19:17 ` HEADSUP: gdbm ABI on x86 Ken Brown
2016-10-11 19:26 ` Achim Gratz
2016-10-15 17:22 ` Achim Gratz
2016-10-15 17:36 ` Ken Brown
2016-10-15 17:37 ` Achim Gratz
2016-10-15 17:40 ` Ken Brown
2016-10-15 17:43 ` Achim Gratz
2016-10-11 19:24 ` Achim Gratz
2017-02-22 19:57 ` Yaakov Selkowitz
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=b91b5360-3cda-9925-511c-1544d4577091@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).