From: Colin Tuckley <colin@tuckley.org>
To: "Atwood, Robert C" <r.atwood@imperial.ac.uk>
Cc: John Love-Jensen <eljay@adobe.com>, gcc-help@gcc.gnu.org
Subject: Re: gFortran problem compiling complex character strings
Date: Mon, 17 Dec 2007 15:05:00 -0000 [thread overview]
Message-ID: <47669020.9090709@tuckley.org> (raw)
In-Reply-To: <2CB39EAF0E0EFF498ADEDA636B8C999F05574A8F@icex1.ic.ac.uk>
Atwood, Robert C wrote:
> Sorry , I was unclear, what I meant was: why DIDN'T it fail to compile
> in g77?
> (i.e. why did it work for Colin previously?)
Yes, that was my main question too. Note that I am NOT the author or
maintainer of this package. I've just been tasked with converting it to use
gfortran.
> Unless some flags were used that were not mentioned in the original
> post, shoudn't the 73-character line fail just as much whether it's
> compiled with g77 or gfortran, because of that same punchcard-style
> statement requirement?
I've checked the makefile and the log, the actual command was as stated:
gfortran -g -O2 -c fortestF.f
Attempting to build the original package on my x86 system it does:
g77 -g -O2 -c fortestF.f
which builds ok.
So it would appear that the Debian version of g77 does not have the 72 char
limit.
regards,
Colin
--
Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id
Debian Developer | +44(0)7799 143369 | 0x1B3045CE
Try to learn from other people's mistakes, you haven't time to make them all
yourself! - Anon
next prev parent reply other threads:[~2007-12-17 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 16:10 Dominique Dhumieres
2007-12-15 16:17 ` John (Eljay) Love-Jensen
2007-12-15 16:36 ` Colin Tuckley
2007-12-17 14:09 ` Atwood, Robert C
2007-12-17 14:15 ` John Love-Jensen
2007-12-17 14:34 ` Atwood, Robert C
2007-12-17 15:05 ` Colin Tuckley [this message]
2007-12-17 15:29 ` Atwood, Robert C
-- strict thread matches above, loose matches on Subject: below --
2007-12-14 8:53 Colin Tuckley
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=47669020.9090709@tuckley.org \
--to=colin@tuckley.org \
--cc=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=r.atwood@imperial.ac.uk \
/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).