public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Fortran compiler for ia64?
Date: Fri, 16 Mar 2001 18:31:08 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005287@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005278@msgid-missing>

>All is in $subject... The existing toolchain doesn't seem to have any support
>for Fortran right now.

The Red Hat tools group (formerly Cygnus) does not support Fortran, so Fortran
is not present in our releases.  Fortran is present in the FSF gcc tree
though, and should be working fine.  Here are test results from a couple of
days ago off the gcc3 branch:

		== g77 Summary =
# of expected passes		904
# of unexpected failures	9
# of untested testcases		6
# of unsupported tests		8

This is very close to the x86 testsuite results.

>Oh, and the linux-ia64 website and cygnus FTP site are still down... Is this
>normal?

Yes, the cygnus ftp site is still down.  It has been down for over a week,
and I still don't have any estimate for when it will be back up.

At this point though, I don't think it really matters anymore.  I'd been
planning for a while to phase out the last compiler release in favor of gcc3.  
I may as well use the ftp site problems to effect the change.  If you still
need the old compiler, you can get source RPMS from Red Hat, Suse, Turbolinux,
etc.  Meanwhile, gcc3 is still not stable enough for building distributions,
but it should be stable enough for most development work.

Jim


      parent reply	other threads:[~2001-03-16 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-16  9:53 [Linux-ia64] Fortran compiler for ia64? Francis Galiegue
2001-03-16 10:21 ` Francis Galiegue
2001-03-16 11:38 ` Roberto Romano
2001-03-16 13:48 ` Andreas Schwab
2001-03-16 15:06 ` Don Dugger
2001-03-16 18:31 ` Jim Wilson [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=marc-linux-ia64-105590693005287@msgid-missing \
    --to=wilson@cygnus.com \
    --cc=linux-ia64@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