From: Mike Frysinger <vapier@gentoo.org>
To: Madhu Pavan <kmp@linux.vnet.ibm.com>
Cc: kzak@redhat.com, util-linux@vger.kernel.org,
deepakcs@linux.vnet.ibm.com, athunugu@linux.vnet.ibm.com
Subject: Re: util-linux-2.24 not compatible with ppc64le architecture
Date: Thu, 26 Dec 2013 02:56:34 -0500 [thread overview]
Message-ID: <201312260256.36705.vapier@gentoo.org> (raw)
In-Reply-To: <52BBD37B.30609@linux.vnet.ibm.com>
[-- Attachment #1: Type: Text/Plain, Size: 1034 bytes --]
On Thursday 26 December 2013 01:58:03 Madhu Pavan wrote:
> 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.
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-12-26 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 6:58 util-linux-2.24 not compatible with ppc64le architecture Madhu Pavan
2013-12-26 7:56 ` Mike Frysinger [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201312260256.36705.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=athunugu@linux.vnet.ibm.com \
--cc=deepakcs@linux.vnet.ibm.com \
--cc=kmp@linux.vnet.ibm.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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