From: Chris Vine <vine35792468@gmail.com>
To: guile-devel@gnu.org
Subject: Re: shlib major change from 3.0.3 to 3.0.4
Date: Sun, 13 Dec 2020 19:56:46 +0000 [thread overview]
Message-ID: <20201213195646.56d37f3e62222bfb82be04ed@gmail.com> (raw)
In-Reply-To: <rmi7dplyde6.fsf@s1.lexort.com>
On Sun, 13 Dec 2020 09:44:01 -0500
Greg Troxel <gdt@lexort.com> wrote:
>
> I am packaging guile 3 in pkgsrc-wip. (It's not promoted to pkgsrc
> proper because I am still having some issues.)
>
> Doing the update from 3.0.3 to 3.0.4 I found this change in install
> files:
>
> -guile/3.0/lib/libguile-3.0.so.3.0.0-gdb.scm
> +guile/3.0/lib/libguile-3.0.so.1.2.0-gdb.scm
>
> and that strikes me as likely a bug. Are others seeing this? Is it
> supposed to be 3.1.0 or 3.0.1, to reflect a micro change? Having the
> major version go backwards is baffling to me.
More to the point, you will have seen guile-3.0.2's libguile-3.0.so.1
move to guile-3.0.3's libguile-3.0.so.3 and then move back to
guile-3.0.4's libguile-3.0.so.1
guile-3.0.3 was released with an accidental SO version bump: micro
versions of guile are supposed to retain and not break ABI/SO-version
compatibility. guile-3.0.4 was released shortly thereafter correcting
the problem. It looks as if you were unfortunate enough to have
installed guile during the hiatus period.
The best thing is to install guile-3.0.4 and recompile anything which
links to libguile-3.0.so.
prev parent reply other threads:[~2020-12-13 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 14:44 shlib major change from 3.0.3 to 3.0.4 Greg Troxel
2020-12-13 19:56 ` Chris Vine [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201213195646.56d37f3e62222bfb82be04ed@gmail.com \
--to=vine35792468@gmail.com \
--cc=guile-devel@gnu.org \
/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).