util-linux-2.24 not compatible with ppc64le architecture

Hi Karel Zak,

We are in the process of adding support for new arch (ppc64le) and as part of that we wanted to send patches for config.guess and configure as appropriate.

util-linux-2.24 could not be built on ppc64le because it had an outdated configure/config.guess/libtool.m4. Since your pkg uses libtool and the latest tarball of your pkg didn't build on ppc64le due to outdated libtool present on your system. We wanted to request you to upgrade your libtool to the alpha release of libtool which has all the bits and pieces needed for ppc64le support.

In that context, I wanted to confirm the below

1) Should we send patches to '[email protected]' mailing list or there is some other mailing list?

2) New libtool alpha release which supports ppc64le arch is available, you may pick up the alpha release from either of the below:

ftp://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.gz (1.6MB)

ftp://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.xz (920KB)

It would be great if you can install this new libtool which supports ppc64le, and spin the pkg and let us know the new tar availability. We can test it on ppc64le architecture for you. Please let me know if you are planning to release or spin newer version.

Currently I used

https://www.kernel.org/pub/linux/utils/util-linux/v2.24/util-linux-2.24.tar.xz

Which does not have ppc64le support.

Your response is highly appreciated.

Thanks in advance,
Madhu Pavan Kothapally

as i explained to one of your coworkers (specifically, about GNU/patch & libtool & ppc64le), and to others about aarch64 in config.{sub,guess}, you're approaching this all wrong. your packaging system should be updating config. {sub,guess} automatically, and you probably should implement something for autoregenerating libtool stuff for ppc64le support.

you're going to hit this in every single package out there. it is unreasonable to go to every maintainer and ask them to regenerate their autotools & re-release using bleeding edge tools (in this case, master branch of libtool). you're going to have to update your build scripts to do this automatically. this is expected behavior every time you release a new architecture that requires changes in core autotool packages. -mike