Am Donnerstag, dem 14.04.2022 um 14:07 +0200 schrieb Andreas Enge:
> > > I have installed libtool@2.4.7 into my profile
> > That is a mistake.
> >
> > > as well as a number of other development tools
> > Probably also a mistake.
>
> Could you elaborate why? If you work on a project, it seems
Am Thu, Apr 14, 2022 at 02:07:02PM +0200 schrieb Andreas Enge:
> I had already removed it, and the problem persisted. I suppose that
> autoreconf or configure created it again in version 2.4.6, and during
> make my version 2.4.7 was used instead.
Actually it is "configure", in my case by calling
Am Thu, Apr 14, 2022 at 01:29:46PM +0200 schrieb Liliana Marie Prikler:
> libtool causes at least 13802 (mere two thirds of all our packages), so
> one might want to ensure that there are no gratuitous bumps when making
> new versions of it available :)
Quite understandable, but if then the new
Am Donnerstag, dem 14.04.2022 um 11:53 +0200 schrieb Andreas Enge:
> Hello,
>
> is there a good reason to have added libtool-2.4.7 without it
> replacing the libtool variable (at version 2.4.6)?
libtool causes at least 13802 (mere two thirds of all our packages), so
one might want to ensure that
Hello,
is there a good reason to have added libtool-2.4.7 without it replacing
the libtool variable (at version 2.4.6)? I have installed libtool@2.4.7
into my profile, as well as a number of other development tools, and
apparently both libtool versions are now used and are colliding when doing
