public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Gaurav Gautam, Noida" <gauravga@noida.hcltech.com>
To: "Larry Blodgett" <lblodgett@gmail.com>,
	"François-Xavier Coudert" <fxcoudert@gmail.com>
Cc: <fortran@gcc.gnu.org>
Subject: RE: gfortran.org
Date: Tue, 28 Jun 2005 06:53:00 -0000	[thread overview]
Message-ID: <8A6EB6A72A5C774C8814DDC1501FC90EF1EA53@exch-01.noida.hcltech.com> (raw)

Yes, that's correct.

I was looking for the latest version of compiler, but I am not able to find what version should I downld.
I mean to say that in order to check out from CVS, I need to write the following command in the CVS.

cvs -z 9 co -P -rgcc-x_y-branch gcc

Where GCC x.y release branch is the version to downld.

Please tell me the the x.y release branch for gfortran ?

I checked out some more sites, have found that its probably 4.0.0.0, is it so ??

Gaurav

> -----Original Message-----
> From: fortran-owner@gcc.gnu.org 
> [mailto:fortran-owner@gcc.gnu.org] On Behalf Of Larry Blodgett
> Sent: Friday, June 24, 2005 1:10 AM
> To: François-Xavier Coudert
> Cc: fortran@gcc.gnu.org
> Subject: Re: gfortran.org
> 
> Your are correct!  I have noticed this also.  And you are 
> correct it is makes it very difficult to find the binaries.
> 
> Larry
> 
> On Jun 23, 2005, at 8:49 AM, François-Xavier Coudert wrote:
> 
> > Hi,
> >
> > I just noticed that gfortran.org doesn't redirect to the 
> wiki, but to 
> > the "GNU Fortran 95" official page. That makes it harder 
> for people to 
> > get the binaries and test the compiler, doesn't it?
> >
> > FX
> >
> >
> > PS: moreover, there's a infinite loop, this the "GNU Fortran 95"
> > webpage states that binaries are available from www.gfortran.org!
> >
> 

             reply	other threads:[~2005-06-28  6:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28  6:53 Gaurav Gautam, Noida [this message]
2005-06-28  7:05 ` gfortran.org FX Coudert
  -- strict thread matches above, loose matches on Subject: below --
2023-11-15 20:55 gfortran.org Hans Weber
2021-11-05  9:15 gfortran.org Manfred Schwarb
2021-11-06 13:49 ` gfortran.org Bud Davis
     [not found] <19c433eb05062306471cd67f3e@mail.gmail.com>
2005-06-23 13:49 ` Fwd: gfortran.org François-Xavier Coudert
2005-06-23 19:40   ` gfortran.org Larry Blodgett
     [not found] <1114598771.9949.ezmlm@gcc.gnu.org>
2005-04-28  0:14 ` gfortran.org R. D. Flowers
2005-04-27 15:13 gfortran.org Paul Thomas
2005-04-26 13:51 gfortran.org THOMAS Paul Richard 169137
2005-04-27 10:46 ` gfortran.org bud davis
2005-04-27 10:57   ` gfortran.org Tobias Schlüter
2005-04-26 12:56 gfortran.org François-Xavier Coudert
2005-04-26 13:19 ` gfortran.org Tobias Schlüter
2005-04-26 13:41   ` gfortran.org François-Xavier Coudert
2005-04-26 14:10     ` gfortran.org Tobias Schlüter
2005-04-26 14:36       ` gfortran.org Tobias Schlüter
2005-04-26 14:50         ` gfortran.org Tobias Schlüter
2005-04-26 18:26         ` gfortran.org François-Xavier Coudert
2005-04-26 18:50         ` gfortran.org Brooks Moses
2005-04-26 14:46       ` gfortran.org François-Xavier Coudert
2005-04-26 15:04         ` gfortran.org Tobias Schlüter
2005-04-26 15:06       ` gfortran.org Alex Gibson
2005-04-27 11:16         ` gfortran.org bud davis

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=8A6EB6A72A5C774C8814DDC1501FC90EF1EA53@exch-01.noida.hcltech.com \
    --to=gauravga@noida.hcltech.com \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=lblodgett@gmail.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).