public inbox for
 help / color / mirror / Atom feed
From: Anthony Green <>
To: Matthias Klose <>
Cc: libffi-discuss <>
Subject: Re: Fwd: Announcing libffi 3.4.2
Date: Fri, 2 Jul 2021 08:25:51 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Jul 1, 2021 at 6:01 AM Matthias Klose <> wrote:
> maybe there is some room for improvement in the release process?

Yes, there definitely is!

> When looking at 3.4.2 (after announcing 3.4),
>  - libtool-version says the abi version is 9, but that seems
>    to be ignored. Where is the definition of the ABI version
>    coming from?

libtool-version is not being ignored.   libtool computes the so number
to be CURRENT - AGE, and 9 - 1 = 8.
I don't pretend to understand the details of libtool and abi
versioning.  I'm just trusting that libtool is doing the right thing.

>  - talks about 3.4.1, not 3.4.2.

Whoops.  That was a miss.  I suspect that there will be a 3.4.3 soon
enough where we can correct it.

> I packaged 3.4.2 for Debian (the only way I can test it on the Debian
> infrastructure), it needs manual approval for the renamed library package, so I
> can't give feedback on test results yet, and have to wait until its built.
> Tests for the Ubuntu architectures pass.

That's great.  Note that some packages that depend on libffi are
broken with the new static trampoline code.  See for details.
You might want to compile with --disable-exec-static-tramp until they
get sorted out.   This will not change the ABI.

> Do you plan to update the libffi copy within GCC to this release?   If not,
> could you give instructions, how the two copies are managed in your VCS, and
> what is the best way to merge those?

I have not been involved in gcc's libffi copy for many many years
(since well before gcj was removed).  In the past, I've promoted the
idea that it be removed from GCC, and that people who need it just
build it separately, like other external dependencies.    The main
challenge will be that the configury has diverged somewhat over the

> I just saw your ping on #libffi on Freenode on Monday, however you are seldom be
> present on this channel.  Is this channel still somewhat official, Is it moved
> to Libera.Net as everything else?  If yes, maybe mention the channel on the
> libffi home page as well.

Yes, let's make a new channel elsewhere. is as good a place as any.

Thank you for the feedback, Matthias.  I'm sorry if this release has
caused you trouble, especially on account of all of the great help
you've provided over the years.

BTW, this year marks the 25th year since the first release.... wow.


      reply	other threads:[~2021-07-02 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-06-29 21:17 ` Anthony Green
2021-07-01 10:01   ` Matthias Klose
2021-07-02 12:25     ` Anthony Green [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).