public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: "Gerald Pfeifer" <gerald@pfeifer.com>,
		<dave.korn.cygwin@googlemail.com>, 	<dave@hiauly1.hia.nrc.ca>,
		"David Edelsohn" <dje.gcc@gmail.com>,
		<Eric.Weddington@atmel.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: MPC version 0.8 released!
Date: Sat, 07 Nov 2009 17:39:00 -0000	[thread overview]
Message-ID: <BCED246F27594B80868C13130864E5BB@glap> (raw)
In-Reply-To: <yddskcs51nu.fsf@komagatake.TechFak.Uni-Bielefeld.DE>

> "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu> writes:
>
>> Please test this version and report back in this thread (not to me
>> privately) the results of "make check".  Also include your target
>> triplet,
>> and the versions of your compiler, gmp and mpfr.

Wow we've gotten a lot of results, thanks everyone!  But we're still missing
a few of the GCC primary and secondary platforms for the mpc-0.8 final
release.  Some of you provided results for the missing systems either for
the mpc-0.8dev prerelease or a previous full release.  I would very much
appreciate it if you would try out the latest package.

The platforms still needed for mpc-0.8 release testing are:

i386-unknown-freebsd (have results for mpc-0.8dev)

i686-pc-cygwin (have results for mpc-0.8dev)
hppa2.0w-hp-hpux11.11 (have results for mpc-0.8dev)

i686-apple-darwin (have results for mpc-0.7)
powerpc-ibm-aix5.3.0.0 (have results for mpc-0.7)
i686-mingw32 (have results for mpc-0.7)

        Thanks!
        --Kaveh
--
Kaveh R. Ghazi

  reply	other threads:[~2009-11-07 17:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 15:54 Kaveh R. GHAZI
2009-11-05 17:20 ` Rainer Orth
2009-11-07 17:39   ` Kaveh R. Ghazi [this message]
2009-11-07 19:38     ` Gerald Pfeifer
2009-11-08  2:33       ` Gerald Pfeifer
2009-11-07 22:06     ` Dave Korn
2009-11-08  4:40     ` Weddington, Eric
2009-11-09  2:49     ` John David Anglin
2009-11-06 17:13 ` Paolo Carlini
2009-11-06 17:16   ` Richard Guenther
2009-11-06 17:21     ` Paolo Carlini
2009-11-06 17:28   ` Eric Botcazou
2009-11-06 17:38     ` Paolo Carlini
2009-11-06 17:44       ` Eric Botcazou
2009-11-06 17:53         ` Paolo Carlini
2009-11-06 18:16           ` Basile STARYNKEVITCH
2009-11-06 18:37             ` Paolo Carlini
2009-11-06 18:51               ` Richard Guenther
2009-11-06 19:01                 ` Paolo Carlini
2009-11-06 19:04                 ` Paolo Carlini
2009-11-06 19:05                   ` Richard Guenther
2009-11-06 19:07                     ` Paolo Carlini
2009-11-06 19:24                       ` Ian Lance Taylor
2009-11-06 19:33                         ` Paolo Carlini
2009-11-06 21:58                           ` Kaveh R. Ghazi
2009-11-06 23:25                             ` Joseph S. Myers
2009-11-08 10:43 ` Janus Weil
2009-11-08 22:57 ` Kaz Kojima
2009-11-05 17:22 Dennis Clarke
2009-11-05 17:53 ` Rainer Orth
2009-11-05 20:59 ` Eric Botcazou
2009-11-05 18:16 Dennis Clarke
2009-11-05 19:06 ` Kaveh R. Ghazi
2009-11-05 20:29   ` Mikael Pettersson

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=BCED246F27594B80868C13130864E5BB@glap \
    --to=ghazi@caip.rutgers.edu \
    --cc=Eric.Weddington@atmel.com \
    --cc=dave.korn.cygwin@googlemail.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.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 read-only IMAP folder(s) and NNTP newsgroup(s).