Bug 668736

Summary:	[TRACKER] package requires m4/* directory update, libtool has become obsolete
Product:	Gentoo Linux	Reporter:	Jonas Stein <jstein>
Component:	Current packages	Assignee:	Jonas Stein <jstein>
Status:	CONFIRMED ---
Severity:	normal	CC:	jstein, pacho, sam
Priority:	Normal	Keywords:	Tracker
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	https://wiki.gentoo.org/wiki/Outdated_libtool
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:	668404, 668406, 668408, 668650, 668652, 668656, 668666
Bug Blocks:

Description Jonas Stein gentoo-dev

2018-10-15 17:39:59 UTC

Detailed explanation about the bug and how to fix it is in the URL.
This is a tracker, please do not discuss here.

Comment 1 Denis Pronin 2018-10-15 18:57:38 UTC

I updated details in the wikipage

Comment 2 Denis Pronin 2018-10-15 19:11:41 UTC

Should I open new issues if any new findings take place?
I learnt many packages that have this issue, I can supply the bugtracker with more packages

Comment 3 Pacho Ramos gentoo-dev

2018-10-20 18:46:38 UTC

should we use plain autoreconf or eautoreconf?

Comment 4 Sam James archtester

2021-03-20 03:43:21 UTC

(In reply to Pacho Ramos from comment #3)
> should we use plain autoreconf or eautoreconf?

Bit late, but always eautoreconf AFAIK.

(In reply to Denis Pronin from comment #2)
> Should I open new issues if any new findings take place?
> I learnt many packages that have this issue, I can supply the bugtracker
> with more packages

Yes.

Comment 5 Sam James archtester

2021-03-31 23:16:04 UTC

Okay, all blockers done.

TL;DR is that it's easiest to check ltmain.sh and that elibtoolize from libtool.eclass is insufficient to refresh (at least by itself), so I just used eautoreconf which seemed to be fine.