On Mon, Mar 20, 2000 at 06:44:04PM +0100, Jose M. Alcaide wrote:
What part about "NO" was unclear?
Hey, OK, don't get upset! :-) You are the maintainer, so you have the
Not upset. I was just surprised by the request again.
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to
Hi David,
Now, a week after the discussion, what do you think about my proposal
of the "g77" link under /usr/bin? IMHO, the following facts are all good
reasons for creating the link:
- the output of "f77 -V", "f77 --version", "man f77", and "info g77";
- our Fortran compiler _is_ GNU
On Mon, Mar 20, 2000 at 11:48:02AM +0100, Jose M. Alcaide wrote:
Now, a week after the discussion, what do you think about my proposal
of the "g77" link under /usr/bin?
What part about "NO" was unclear?
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
David O'Brien wrote:
On Mon, Mar 20, 2000 at 11:48:02AM +0100, Jose M. Alcaide wrote:
Now, a week after the discussion, what do you think about my proposal
of the "g77" link under /usr/bin?
What part about "NO" was unclear?
Hey, OK, don't get upset! :-) You are the maintainer, so you
David O'Brien wrote:
NO. I will not apply this link. BSD has always had a "f77" command. It
has not always had a "g77" command. The G77 developers should have
installed a "f77" compatability link. It is their fault this misspelling
is perpitrating forward. All the world is not Gfoo.
On Mon, Mar 13, 2000 at 05:00:17PM +0100, Jose M. Alcaide wrote:
I found that the "configure" script, when instructed to use the
GNU Fortran compiler, searchs for "g77". Unfortunately, this compiler
is installed as /usr/bin/f77.
Fix Scilab-2.5's config script and send the patch to its
On Tue, 14 Mar 2000 14:38:26 -0800, "David O'Brien" [EMAIL PROTECTED] said:
NO. I will not apply this link. BSD has always had a "f77" command. It
has not always had a "g77" command. The G77 developers should have
installed a "f77" compatability link. It is their fault this misspelling
* From: "David O'Brien" [EMAIL PROTECTED]
* On Mon, Mar 13, 2000 at 05:00:17PM +0100, Jose M. Alcaide wrote:
* I found that the "configure" script, when instructed to use the
* GNU Fortran compiler, searchs for "g77". Unfortunately, this compiler
* is installed as /usr/bin/f77.
I think
On Tue, Mar 14, 2000 at 05:40:48PM -0500, Garrett Wollman wrote:
NO. I will not apply this link. BSD has always had a "f77" command. It
has not always had a "g77" command. The G77 developers should have
installed a "f77" compatability link. It is their fault this misspelling
is
On Tue, 14 Mar 2000 17:57:36 -0800, "David O'Brien" [EMAIL PROTECTED] said:
*IF* I understand what you are trying to say, here is my answer: if I
were to start fresh with with bringing in the first C compiler into
FreeBSD, it would not have a 'gcc' name to it -- only 'cc'.
Indeed, that was
Hello,
While trying to compile Scilab-2.5 (the math/Scilab port is outdated),
I found that the "configure" script, when instructed to use the
GNU Fortran compiler, searchs for "g77". Unfortunately, this compiler
is installed as /usr/bin/f77. The solution is simple: "ln f77 g77",
but I think that
11 matches
Mail list logo
