From: Mark Kettenis <kettenis@wins.uva.nl>
To: libc-hacker@sourceware.cygnus.com
Subject: DB 2.7.x is not binary compatible with DB 2.4.x
Date: Wed, 21 Jul 1999 03:10:00 -0000 [thread overview]
Message-ID: <199907211010.MAA21097@landau.wins.uva.nl> (raw)
I've verified that DB 2.7.5 (the version on the main branch) is not
binary compatible with DB 2.4.14 (the version included with 2.1.x).
Sendmail cannot create the aliases database (/etc/aliases.db)
anymore. If you compare db.h between those versions (using the CVS
web browser on sourceware) you'll see that a lot of flags have been
renumbered. In particular the DB_TRUNCATE flag, which is causing my
sendmail troubles.
This means that we should either bump the libdb soname, or use
versioning to create functions that map the old flags onto the new
ones. I think the latter involves quite some work, and is not
guaranteed to result in total binary compatibility. So personally, I'm
in favour of bumping the soname.
Mark
next reply other threads:[~1999-07-21 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-21 3:10 Mark Kettenis [this message]
1999-07-21 5:50 ` Ulrich Drepper
1999-07-21 8:08 ` Mark Kettenis
1999-07-21 8:59 ` Ulrich Drepper
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=199907211010.MAA21097@landau.wins.uva.nl \
--to=kettenis@wins.uva.nl \
--cc=libc-hacker@sourceware.cygnus.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).