| Author |
binary of gcc and gfortran shapshot 20080125 for windows
|
|
|
|
| Gerry Ford 2008-01-26, 7:21 pm |
| As usual, at the waters where the g s meet, my ability to comment is
limited.
--
The most common of all follies is to believe passionately in the palpably
not true. It is the chief occupation of mankind.
-- H L Mencken, A Mencken Chrestomathy (1949)
"post" <no-spam@equation.com> wrote in message
news:KDGmj.425$ar6.319@trnddc07...
> available for download at www.equation.com
> Enjoy free compilers.
>
>
| |
|
| On Sat, 26 Jan 2008 13:32:26 +0000, post wrote:
> available for download at www.equation.com
> Enjoy free compilers.
Would you let us know what has changed between each snapshot that you
make available?
| |
|
| >> available for download at www.equation.com
>
> Would you let us know what has changed between each snapshot that you
> make available?
I'd suggest that the kind of announcement should be posted only when
notable changes in the said compilers happen. At least, I think too
frequent announcement lower the information/noise ration of the group.
--
FX
| |
|
| On Sat, 26 Jan 2008 22:19:56 +0000, FX wrote:
>
> I'd suggest that the kind of announcement should be posted only when
> notable changes in the said compilers happen. At least, I think too
> frequent announcement lower the information/noise ration of the group.
Since we have a one-liner, Version xxx available @ yyy', we could have a
little more info - even 'based on gcc snapshot dated zzz' would be
helpful, as we can then look up on the gcc website. But as it stands
there is no reference to the gcc original, either.
| |
|
|
"none" <none@none.net> wrote in message
news:pan.2008.01.26.22.53.39.658000@none.net...
> On Sat, 26 Jan 2008 22:19:56 +0000, FX wrote:
> Since we have a one-liner, Version xxx available @ yyy', we could have a
> little more info - even 'based on gcc snapshot dated zzz' would be
> helpful, as we can then look up on the gcc website. But as it stands
> there is no reference to the gcc original, either.
You should see the subject: s[n]apshot 20080125
| |
|
|
"FX" <coudert@alussinan.org> wrote in message
news:fngbmc$get$1@nef.ens.fr...
> I'd suggest that the kind of announcement should be posted only when
> notable changes in the said compilers happen. At least, I think too
> frequent announcement lower the information/noise ration of the group.
>
> --
> FX
Thank you for the opinion. You think "the kind of announcement should be
posted only when notable changes in the said compilers happen." Not everyone
agrees with your opinion. GNU releases snapshot wly. No interest to argue
whether once a w is too frequent. The announcement (two lines) does not
bother you if you have no interest in it.
Thank you for your contribution to gfortran.
| |
| Steven G. Kargl 2008-01-26, 10:30 pm |
| In article <g4Rmj.5900$O9.5519@trnddc01>,
"post" <no-spam@equation.com> writes:
>
> "FX" <coudert@alussinan.org> wrote in message
> news:fngbmc$get$1@nef.ens.fr...
>
> Thank you for the opinion. You think "the kind of announcement should be
> posted only when notable changes in the said compilers happen." Not everyone
> agrees with your opinion. GNU releases snapshot wly. No interest to argue
> whether once a w is too frequent. The announcement (two lines) does not
> bother you if you have no interest in it.
>
> Thank you for your contribution to gfortran.
>
Are you also making the source code available? Are you
going to have the code for this specific snapshot that
you are distributing available for 3 years as per section
3 of the GPL?
--
Steve
http://troutmask.apl.washington.edu/~kargl/
| |
| Richard Maine 2008-01-26, 10:30 pm |
| post <no-spam@equation.com> wrote:
> "none" <none@none.net> wrote in message
> news:pan.2008.01.26.22.53.39.658000@none.net...
>
> You should see the subject: s[n]apshot 20080125
Yes, I sort of guessed that, but a lesson from my technical writing
training seems applicable.
The title/subject of an article (or section) is not supposed to
substitute for content. The title is an guide to the content - not a
replacement. In the particular case of usenet articles, depending on the
particular reader, the subject line might be separated far enough from
the content that it is not evident to the reader of the content. It
might be evident in whatever newsreader you use, but do not assume this
is so of all newsreaders; it isn't. I have even seen article text manage
to get completely separated from its subject and displayed without the
subject at all.
--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
| |
|
| On Sun, 27 Jan 2008 01:16:33 +0000, post wrote:
>
> "none" <none@none.net> wrote in message
> news:pan.2008.01.26.22.53.39.658000@none.net...
>
> You should see the subject: s[n]apshot 20080125
Fair enough. I took the snapshot date to be the date of *your*
compilation, not that of the associated gcc snapshot.
| |
|
|
"none" <none@none.net> wrote in message
news:pan.2008.01.27.18.22.02.342000@none.net...
>
> Fair enough. I took the snapshot date to be the date of *your*
> compilation, not that of the associated gcc snapshot.
Richard Maine:
I know it is you. IP can tell. Take a look at the following, snapshot fated
20080125.
11/23/2007 11:07PM Directory 4.3-20071123
11/30/2007 11:07PM Directory 4.3-20071130
12/07/2007 11:07PM Directory 4.3-20071207
12/14/2007 11:07PM Directory 4.3-20071214
12/21/2007 11:07PM Directory 4.3-20071221
12/28/2007 11:07PM Directory 4.3-20071228
01/04/2008 11:07PM Directory 4.3-20080104
01/11/2008 11:07PM Directory 4.3-20080111
01/18/2008 11:07PM Directory 4.3-20080118
01/25/2008 11:07PM Directory 4.3-20080125
| |
|
|
"Steven G. Kargl" <kargl@troutmask.apl.washington.edu> wrote in message
news:fngop6$j6d$1@gnus01.u.washington.edu...
> Are you also making the source code available? Are you
> going to have the code for this specific snapshot that
> you are distributing available for 3 years as per section
> 3 of the GPL?
>
> --
> Steve
> http://troutmask.apl.washington.edu/~kargl/
It is not an issue.
| |
|
| On Mon, 28 Jan 2008 14:15:28 +0000, post wrote:
>
> "none" <none@none.net> wrote in message
> news:pan.2008.01.27.18.22.02.342000@none.net...
>
>
> Richard Maine:
>
> I know it is you. IP can tell. Take a look at the following, snapshot fated
> 20080125.
>
> 11/23/2007 11:07PM Directory 4.3-20071123
> 11/30/2007 11:07PM Directory 4.3-20071130
> 12/07/2007 11:07PM Directory 4.3-20071207
> 12/14/2007 11:07PM Directory 4.3-20071214
> 12/21/2007 11:07PM Directory 4.3-20071221
> 12/28/2007 11:07PM Directory 4.3-20071228
> 01/04/2008 11:07PM Directory 4.3-20080104
> 01/11/2008 11:07PM Directory 4.3-20080111
> 01/18/2008 11:07PM Directory 4.3-20080118
> 01/25/2008 11:07PM Directory 4.3-20080125
? You think 'none@none.net' is Richard Maine? If only! The IP address is
in the UK, and my original reason for wanting some idea of what had
changed was that you were posting wly, & I didn't know how you
tied in with gcc - you appeared to be making some unspecified
change to work with your parallel programming support, hence I
assumed that you weren't strictly tracking the gcc release dates. Because
you post your updates here I assumed that there was some significant
change - most people providing minor updates rely on 'pull' rather than
'push' to inform people outside the known customer base. (Main gfortran,
for example, seems to wait for a point update, and provides a link to a
'what has changed' page with the announcement. So I know that their
announcements are worth paying attention to. I'd assumed that your company
was of a similar level of gravitas.)
| |
| Richard Maine 2008-01-28, 7:25 pm |
| post <no-spam@equation.com> wrote:
> Richard Maine:
>
> I know it is you. IP can tell.
I have no idea what you are talking about. Nor do I particularly care.
It isn't worth bothering to figure out what might have mislead you. I
take pride in my work and I put my name on it. It isn't as though the
subject post had anything particularly meriting anonymous posting
anyway.
--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
| |
| Paul van Delst 2008-01-28, 7:25 pm |
| Richard Maine wrote:
> post <no-spam@equation.com> wrote:
>
>
> I have no idea what you are talking about. Nor do I particularly care.
> It isn't worth bothering to figure out what might have mislead you. I
> take pride in my work and I put my name on it. It isn't as though the
> subject post had anything particularly meriting anonymous posting
> anyway.
And one wonders if the same attention to detail was applied to other endeavours at the
OP's website.
cheers,
paulv
| |
| Fly Away 2008-01-28, 7:25 pm |
| On Jan 28, 12:17=A0pm, "FX" <coud...@alussinan.org> wrote:
>
> That was the thing that I thought was not desirable. Now, if I'm alone
> feeling that way (and it looks that way), I'm perfectly fine with it. I
> don't think it's reasonable path to choose, but if that's the one
> favoured by the community, I'll go along it.
I am with you on this one.
Also, I wouldn't use any gfortran builds not associated with gfortran
development team. Well, unless I built it myself :-)
Victor.
| |
| James Van Buskirk 2008-02-16, 7:22 pm |
| "post" <no-spam@equation.com> wrote in message
news:KDGmj.425$ar6.319@trnddc07...
> available for download at www.equation.com
> Enjoy free compilers.
Thank you for providing this service, which also helps out the
gfortran people because you provide snapshots more frequently than
they do, making it possible to determine whether any bugs found
are due to using an outdated version of gfortran or are still
present in the current version.
One problem with your installer, at least the the x64 version, is
that it sets the LIBRARY_PATH variable without asking the user if
he wants to do so. As it turns out, this variable seems not to be
required by gfortran but if set it messes up other installations
of gcc. Could you take this environmental variable out of the
installation process or at least ask this user whether he wants
to set it before doing so?
--
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end
| |
|
|
"James Van Buskirk" <not_valid@comcast.net> wrote in message
news:85-dnRP_wKEYxCranZ2dnUVZ_jSdnZ2d@comcast.com...
> "post" <no-spam@equation.com> wrote in message
> news:KDGmj.425$ar6.319@trnddc07...
> ......
> One problem with your installer, at least the the x64 version, is
> that it sets the LIBRARY_PATH variable without asking the user if
> he wants to do so. As it turns out, this variable seems not to be
> required by gfortran but if set it messes up other installations
> of gcc. Could you take this environmental variable out of the
> installation process or at least ask this user whether he wants
> to set it before doing so?
You are right. The variable LIBRARY_PATH is no longer required. The
installer will be modified not to set the variable.
Old version of w64-api and runtime binaries are in the subdirectory
x86_64-pc-mingw32/lib64. Linker needs the variable to search libraries.
Current w64 and runtime binaries are in subdirectory
x86_64-pc-mingw32/lib.The variable LIBRARY_PATH is unnecessary.
|
|
|
|