MPC 0.8 prerelease tarball (last release before MPC is mandatory!)

[Kaveh R. Ghazi]

A prerelease tarball of the upcoming mpc-0.8 is available here:
http://www.multiprecision.org/mpc/download/mpc-0.8-dev.tar.gz

This release is feature complete with respect to C99 and GCC's needs.
So I expect to make this version be the one made mandatory for the
gcc-4.5 release.  If there are any remaining bugs especially
portability problems to GCC's primary or secondary platforms, I'd like
to get those reported and fixed before this release is final.

Please test this MPC package and report back the results of running
"make check" along with your target triplet, the compiler version you
used, and the versions of gmp/mpfr used to compile it.  You do not
necessarily need to bootstrap mainline GCC with this MPC, but if you
have the spare time and cycles it would be nice too.

                Thanks,
                --Kaveh
--
Kaveh R. Ghazi ghazi@...

[Kaveh R. Ghazi]

From: "David Fang" <fang@...>

> On powerpc-apple-darwin8:
>
> gmp: 4.3.1
> mpfr: 2.4.1
>
> % gcc -v
> Using built-in specs.
> Target: powerpc-apple-darwin8
> Configured with:
> /var/tmp/gcc/gcc-5370~2/src/configure --disable-checking -enable-werror --prefix=/usr
>  --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/
>  --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=powerpc-apple-darwin8
>  --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8
> Thread model: posix
> gcc version 4.0.1 (Apple Computer, Inc. build 5370)
>
> CPU: dual G4, powerpc 7400
>
> ===================
> All 57 tests passed
> ===================

Thanks!

[Kaveh R. Ghazi]

From: "Allan McRae" <allan@...>
 

> Nothing exotic:
> i686-pc-linux-gnu & x86_64-unknown-linux-gnu
>
> Both:
> ===================
> All 57 tests passed
> ===================
>
> gcc-4.4.2
> mpfr-2.4.1
> gmp-4.3.1
>
> Also fine on i686-pc-linux-gnu with gcc-4.5-20091008
>
> Allan

Thanks!

[John David Anglin-4]

> Please test this MPC package and report back the results of running
> "make check" along with your target triplet, the compiler version you
> used, and the versions of gmp/mpfr used to compile it.  You do not
> necessarily need to bootstrap mainline GCC with this MPC, but if you
> have the spare time and cycles it would be nice too.

All 57 tests passed on hppa2.0w-hp-hpux11.11 and hppa64-hp-hpux11.11.

Dave
--
J. David Anglin                                  dave.anglin@...
National Research Council of Canada              [phone] (FAX: [phone])

[Ed Smith-Rowland]

Kaveh R. GHAZI wrote:

> A prerelease tarball of the upcoming mpc-0.8 is available here:
> http://www.multiprecision.org/mpc/download/mpc-0.8-dev.tar.gz
>
> This release is feature complete with respect to C99 and GCC's needs.
> So I expect to make this version be the one made mandatory for the
> gcc-4.5 release.  If there are any remaining bugs especially
> portability problems to GCC's primary or secondary platforms, I'd like
> to get those reported and fixed before this release is final.
>
> Please test this MPC package and report back the results of running
> "make check" along with your target triplet, the compiler version you
> used, and the versions of gmp/mpfr used to compile it.  You do not
> necessarily need to bootstrap mainline GCC with this MPC, but if you
> have the spare time and cycles it would be nice too.
>
> Thanks,
> --Kaveh
> --
> Kaveh R. Ghazi ghazi@...
>
>  

I'm on MacOSX 10.3

MacOSX:~/Tarballs/mpc-0.8-dev ed$ gcc -v
Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1671)

The -Werror kills it.
This warning is familiar.

MacOSX:~/Tarballs/mpc-0.8-dev ed$ make
make  all-recursive
make[1]: Entering directory `/Users/ed/Tarballs/mpc-0.8-dev'
Making all in src
make[2]: Entering directory `/Users/ed/Tarballs/mpc-0.8-dev/src'
/bin/sh ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I..    -pedantic -Wno-long-long -Wall -Werror -O2 -pedantic -mpowerpc
-no-cpp-precomp -force_cpusubtype_ALL -mcpu=7450 -MT abs.lo -MD -MP -MF
.deps/abs.Tpo -c -o abs.lo abs.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -pedantic -Wno-long-long
-Wall -Werror -O2 -pedantic -mpowerpc -no-cpp-precomp
-force_cpusubtype_ALL -mcpu=7450 -MT abs.lo -MD -MP -MF .deps/abs.Tpo -c
abs.c  -fno-common -DPIC -o .libs/abs.o
In file included from mpc-impl.h:33,
                 from abs.c:22:
mpc.h:148: warning: use of `long double' type; its size may change in a
future release
mpc.h:148: warning: (Long double usage is reported only once for each file.
mpc.h:148: warning: To disable this warning, use -Wno-long-double.)
make[2]: *** [abs.lo] Error 1
make[2]: Leaving directory `/Users/ed/Tarballs/mpc-0.8-dev/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/Users/ed/Tarballs/mpc-0.8-dev'
make: *** [all] Error 2

[Ed Smith-Rowland]

Ed Smith-Rowland wrote:

> Kaveh R. GHAZI wrote:
>> A prerelease tarball of the upcoming mpc-0.8 is available here:
>> http://www.multiprecision.org/mpc/download/mpc-0.8-dev.tar.gz
>>
>> This release is feature complete with respect to C99 and GCC's needs.
>> So I expect to make this version be the one made mandatory for the
>> gcc-4.5 release.  If there are any remaining bugs especially
>> portability problems to GCC's primary or secondary platforms, I'd like
>> to get those reported and fixed before this release is final.
>>
>> Please test this MPC package and report back the results of running
>> "make check" along with your target triplet, the compiler version you
>> used, and the versions of gmp/mpfr used to compile it.  You do not
>> necessarily need to bootstrap mainline GCC with this MPC, but if you
>> have the spare time and cycles it would be nice too.
>>
>>         Thanks,
>>         --Kaveh
>> --
>> Kaveh R. Ghazi            ghazi@...
>>
>>  
> I'm on MacOSX 10.3
>
> MacOSX:~/Tarballs/mpc-0.8-dev ed$ gcc -v
> Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
> Thread model: posix
> gcc version 3.3 20030304 (Apple Computer, Inc. build 1671)
>
> The -Werror kills it.
> This warning is familiar.
>
> MacOSX:~/Tarballs/mpc-0.8-dev ed$ make
> make  all-recursive
> make[1]: Entering directory `/Users/ed/Tarballs/mpc-0.8-dev'
> Making all in src
> make[2]: Entering directory `/Users/ed/Tarballs/mpc-0.8-dev/src'
> /bin/sh ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I..    -pedantic -Wno-long-long -Wall -Werror -O2 -pedantic -mpowerpc
> -no-cpp-precomp -force_cpusubtype_ALL -mcpu=7450 -MT abs.lo -MD -MP
> -MF .deps/abs.Tpo -c -o abs.lo abs.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -pedantic
> -Wno-long-long -Wall -Werror -O2 -pedantic -mpowerpc -no-cpp-precomp
> -force_cpusubtype_ALL -mcpu=7450 -MT abs.lo -MD -MP -MF .deps/abs.Tpo
> -c abs.c  -fno-common -DPIC -o .libs/abs.o
> In file included from mpc-impl.h:33,
>                 from abs.c:22:
> mpc.h:148: warning: use of `long double' type; its size may change in
> a future release
> mpc.h:148: warning: (Long double usage is reported only once for each
> file.
> mpc.h:148: warning: To disable this warning, use -Wno-long-double.)
> make[2]: *** [abs.lo] Error 1
> make[2]: Leaving directory `/Users/ed/Tarballs/mpc-0.8-dev/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/Users/ed/Tarballs/mpc-0.8-dev'
> make: *** [all] Error 2
>
>

Once I deleted -Werror out of the makefiles...

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

I don't know how you would tweak the configure to kill this -Werror for
mac but that would do it.

Ed

[Dave Korn-6]

Kaveh R. GHAZI wrote:

> Please test this MPC package and report back the results of running
> "make check" along with your target triplet, the compiler version you
> used, and the versions of gmp/mpfr used to compile it.  

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

i686-pc-cygwin

gcc version 4.3.4 20090804 (release) 1 (GCC)

Cygwin Package Information
Package              Version
gmp                  4.3.1-3
mpfr                 2.4.1-4

> You do not
> necessarily need to bootstrap mainline GCC with this MPC, but if you
> have the spare time and cycles it would be nice too.

  I didn't, I'm afraid, sorry.

    cheers,
      DaveK

[Kaveh R. Ghazi]

From: "Ed Smith-Rowland" <3dw4rd@...>

>> I'm on MacOSX 10.3
>>
>> MacOSX:~/Tarballs/mpc-0.8-dev ed$ gcc -v
>> Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
>> Thread model: posix
>> gcc version 3.3 20030304 (Apple Computer, Inc. build 1671)
>>
>> The -Werror kills it.
> Once I deleted -Werror out of the makefiles...
>
> ===================
> All 57 tests passed
> ===================
>
> I don't know how you would tweak the configure to kill this -Werror for
> mac but that would do it.

The -Werror flag will not be used in the final release, so it should work
for you.

Thanks for testing.

        --Kaveh

[Gerald Pfeifer]

On Thu, 29 Oct 2009, Kaveh R. GHAZI wrote:
> Please test this MPC package and report back the results of running
> "make check" along with your target triplet, the compiler version you
> used, and the versions of gmp/mpfr used to compile it.  You do not
> necessarily need to bootstrap mainline GCC with this MPC, but if you
> have the spare time and cycles it would be nice too.

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

i386-unknown-freebsd7.2
gcc version 4.2.1 20070719  [FreeBSD]
mpfr-2.4.1_1

(FWIW, on FreeBSD I have made MPC a hard requirement for the GCC 4.5
port already.  I assume the next steps on your side are waiting for
the official releaes of MPC 0.8 and then making that a requirement for
our configure scripts?)

Gerald

[Kaz Kojima]

"Kaveh R. GHAZI" <ghazi@...> wrote:
> Please test this MPC package and report back the results of running
> "make check" along with your target triplet, the compiler version you
> used, and the versions of gmp/mpfr used to compile it.  You do not
> necessarily need to bootstrap mainline GCC with this MPC, but if you
> have the spare time and cycles it would be nice too.

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

sh4-unknown-linux-gnu
gcc 4.2.4
gmp 4.2.2
mpfr 2.3.2

Regards,
        kaz

[Kaveh R. Ghazi]

From: "Gerald Pfeifer" <gerald@...>

> ===================
> All 57 tests passed
> ===================
>
> i386-unknown-freebsd7.2
> gcc version 4.2.1 20070719  [FreeBSD]
> mpfr-2.4.1_1
>
> (FWIW, on FreeBSD I have made MPC a hard requirement for the GCC 4.5
> port already.  I assume the next steps on your side are waiting for
> the official releaes of MPC 0.8 and then making that a requirement for
> our configure scripts?)

Yes.  There remains a few cleanups (see PR40302), but the heavy lifting is
all done.

        --Kaveh

[David Edelsohn-3]

On Thu, Oct 29, 2009 at 12:18 PM, Kaveh R. GHAZI <ghazi@...> wrote:

> A prerelease tarball of the upcoming mpc-0.8 is available here:
> http://www.multiprecision.org/mpc/download/mpc-0.8-dev.tar.gz
>
> This release is feature complete with respect to C99 and GCC's needs.
> So I expect to make this version be the one made mandatory for the
> gcc-4.5 release.  If there are any remaining bugs especially
> portability problems to GCC's primary or secondary platforms, I'd like
> to get those reported and fixed before this release is final.
>
> Please test this MPC package and report back the results of running
> "make check" along with your target triplet, the compiler version you
> used, and the versions of gmp/mpfr used to compile it.  You do not
> necessarily need to bootstrap mainline GCC with this MPC, but if you
> have the spare time and cycles it would be nice too.

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.

David

[Kaveh R. Ghazi]

> From: "David Edelsohn" <dje.gcc@...>
>
> 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.

What do you suggest as possible ways forward?

        Thanks,
        --Kaveh

[David Edelsohn-3]

On Sun, Nov 8, 2009 at 1:22 AM, Kaveh R. Ghazi <ghazi@...> wrote:

>> From: "David Edelsohn" <dje.gcc@...>
>>
>> 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

[Paolo Bonzini-2]

On 11/08/2009 10:29 PM, David Edelsohn wrote:
> The problem is shell append += and libtool not running with the same
> shell used by configure.

What version of libtool is used by mpc?  Libtool HEAD could fix this bug.

Paolo

[Kaveh R. Ghazi]

From: "David Edelsohn" <dje.gcc@...>

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

Hm, the mpc configure script actually has a check for shell +=, and on my
solaris box it correctly detects that it doesn't work.

        checking whether the shell understands "+="... no

Presumably on solaris then += isn't used.  I wonder what does configure say
here for AIX and why does it attempt to use it?


>
>After my intervention:
>
>$ make check
>
>===================
>All 57 tests passed
>===================

Thanks for the report.  Do you consider this issue closed or would you like
to pursue it further?

        --Kaveh

[Kaveh R. Ghazi]

On Mon, 9 Nov 2009, Paolo Bonzini wrote:

> On 11/08/2009 10:29 PM, David Edelsohn wrote:
> > The problem is shell append += and libtool not running with the same
> > shell used by configure.
>
> What version of libtool is used by mpc?  Libtool HEAD could fix this bug.
> Paolo

(GNU libtool) 2.2.6 Debian-2.2.6a-4

[Paolo Bonzini-2]

On 11/09/2009 06:33 AM, Kaveh R. Ghazi wrote:

> From: "David Edelsohn" <dje.gcc@...>
>
>> AIX Shell is KSH.
>>
>> The problem is shell append += and libtool not running with the same
>> shell used by configure.
>
> Hm, the mpc configure script actually has a check for shell +=, and on
> my solaris box it correctly detects that it doesn't work.
>
> checking whether the shell understands "+="... no
>
> Presumably on solaris then += isn't used. I wonder what does configure
> say here for AIX and why does it attempt to use it?

As David said, the problem is using the same shell in configure and
libtool.  I think I fixed this upstream (just as a consequence of cleanups).

Paolo

[Kaveh R. Ghazi]

On Mon, 9 Nov 2009, Paolo Bonzini wrote:

> On 11/09/2009 06:33 AM, Kaveh R. Ghazi wrote:
> > From: "David Edelsohn" <dje.gcc@...>
> >
> >> AIX Shell is KSH.
> >>
> >> The problem is shell append += and libtool not running with the same
> >> shell used by configure.
> >
> > Hm, the mpc configure script actually has a check for shell +=, and on
> > my solaris box it correctly detects that it doesn't work.
> >
> > checking whether the shell understands "+="... no
> >
> > Presumably on solaris then += isn't used. I wonder what does configure
> > say here for AIX and why does it attempt to use it?
>
> As David said, the problem is using the same shell in configure and
> libtool.  I think I fixed this upstream (just as a consequence of cleanups).
> Paolo

So IIUC, David is setting SHELL=/path/to/bash first, then running
configure, then getting an error.  This happens because configure tests
that bash understands +=, but libtool is run with (presumably) /bin/sh and
doesn't understand += right?

If so, then if one doesn't set SHELL (or CONFIG_SHELL?) on AIX, everything
should work fine building MPC, right?

                --Kaveh

[David Edelsohn-3]

On Tue, Nov 10, 2009 at 1:16 AM, Kaveh R. GHAZI <ghazi@...> wrote:

> So IIUC, David is setting SHELL=/path/to/bash first, then running
> configure, then getting an error.  This happens because configure tests
> that bash understands +=, but libtool is run with (presumably) /bin/sh and
> doesn't understand += right?
>
> If so, then if one doesn't set SHELL (or CONFIG_SHELL?) on AIX, everything
> should work fine building MPC, right?

Basically, but using /bin/sh on AIX causes other problems.

David