alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Madhu Pavan <kmp@linux.vnet.ibm.com>
To: alsa-devel@alsa-project.org
Cc: deepakcs@linux.vnet.ibm.com, athunugu@linux.vnet.ibm.com
Subject: alsa-lib-1.0.27.2 not compatible with ppc64le architecture
Date: Thu, 28 Nov 2013 11:17:26 +0530	[thread overview]
Message-ID: <5296D8EE.7070104@linux.vnet.ibm.com> (raw)

Hi,

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.

alsa-lib-1.0.27.2 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 this 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

http://www.alsa-project.org/main/index.php/Main_Page

Which does not have ppc64le support.

Your response is highly appreciated.

Thanks in advance,
Madhu Pavan Kothapally

                 reply	other threads:[~2013-11-28  5:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5296D8EE.7070104@linux.vnet.ibm.com \
    --to=kmp@linux.vnet.ibm.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=athunugu@linux.vnet.ibm.com \
    --cc=deepakcs@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).