public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: MPC 0.8 prerelease tarball (last release before MPC is  	mandatory!)
Date: Sun, 08 Nov 2009 21:29:00 -0000	[thread overview]
Message-ID: <303e1d290911081329mcd1f020g7643400a476eabde@mail.gmail.com> (raw)
In-Reply-To: <63C993CFFB4B4FC88660A99A3DE2D62D@glap>

On Sun, Nov 8, 2009 at 1:22 AM, Kaveh R. Ghazi <ghazi@caip.rutgers.edu> wrote:
>> From: "David Edelsohn" <dje.gcc@gmail.com>
>>
>> MPC-0.8 build fails on AIX due to libtool.  The changes to libtool
>> between MPC-0.7 and MPC-0.8 rely on Bash-specific features.  Manually
>> editing libtool to use Bash allowed the build to succeed.
>
> Hi David,
>
> Can you please be more specific about this problem?  I've seen several build
> reports on non-gnu systems that don't use bash as the default shell,
> including my own solaris2.9 box.  None of them fail on bash-isms.  So I'm
> curious what the actual failure is on AIX.
>
> The more recent libtool was suggested to avoid some issues on darwin, so I
> prefer not to opt for a downgrade if at all possible.  If there is some
> non-portable shell construct, we should file a bug report with the libtool
> maintainers.  Another option in the mean time is that if ksh or some other
> shell supplied by default works on AIX we could recommend using that via
> CONFIG_SHELL.

AIX Shell is KSH.

The problem is shell append += and libtool not running with the same
shell used by configure.

After my intervention:

$ make check

===================
All 57 tests passed
===================

Thanks, David

  reply	other threads:[~2009-11-08 21:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 19:34 Kaveh R. GHAZI
     [not found] ` <20091029153734.F64985@shannon.csl.cornell.edu>
2009-10-30  3:31   ` Kaveh R. Ghazi
     [not found] ` <4AEA24F6.1020203@archlinux.org>
2009-10-30  4:16   ` Kaveh R. Ghazi
2009-10-31  5:11 ` Ed Smith-Rowland
2009-10-31  6:31   ` Ed Smith-Rowland
2009-10-31 21:36     ` Kaveh R. Ghazi
2009-10-31 18:10 ` Dave Korn
2009-11-01  0:17 ` John David Anglin
2009-11-01 17:54 ` Gerald Pfeifer
2009-11-02  3:06   ` Kaveh R. Ghazi
2009-11-01 21:57 ` Kaz Kojima
2009-11-08  2:01 ` David Edelsohn
2009-11-08  6:22   ` Kaveh R. Ghazi
2009-11-08 21:29     ` David Edelsohn [this message]
2009-11-09  1:14       ` Paolo Bonzini
2009-11-09  5:38         ` Kaveh R. GHAZI
2009-11-09  5:33       ` Kaveh R. Ghazi
2009-11-09  9:21         ` Paolo Bonzini
2009-11-10  6:16           ` Kaveh R. GHAZI
2009-11-10 16:13             ` David Edelsohn
2009-11-10 16:50               ` Kaveh R. Ghazi
2009-11-11  0:22                 ` David Edelsohn
2009-11-12 16:59 Jack Howarth
2009-11-12 17:02 ` Richard Guenther

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=303e1d290911081329mcd1f020g7643400a476eabde@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).