From: "Martin Tee via fortran" <fortran@gcc.gnu.org>
To: nachiket k <nachiket316@gmail.com>
Cc: fortran@gcc.gnu.org
Subject: Re: -assume noold_ldout_format for GNU
Date: Wed, 30 May 2018 11:43:00 -0000 [thread overview]
Message-ID: <1527678731.6484.2.camel@btinternet.com> (raw)
In-Reply-To: <CAAsAziBGujiM_KG1yyX+SsH2k5iEQGeAM-gWgvnv01Gn8N7tHA@mail.gmail.com>
.f files are fixed format?
For explicit interface include an interface block or put sub-program in
a module and 'USE' the module in the calling procedure.
On Wed, 2018-05-30 at 15:25 +0530, nachiket k wrote:
> Yes I tried removing all those flags but I am still getting same
> errors
> I tried that's why I thought may be it is due to some flags that I am
> missing
>
> Same source has been compiled with intel compilers
>
> Is there anything obvious about the error that I am missing ?
>
> Is this because of some format mismatch error in source (as error is
> reported at 72 column copygb2.f:1074:72 )
> Is there any flag that I can you so control this kind of behavior ?
>
> I have also tried
> -ffree-line-length-0 -fconvert=swap -freal-4-real-8 -lm -fcheck=all
> (-static and -ffast-math too just to check)
>
> Also what does it mean to make an explicit interface available in the
> subprogram where this CALL occurs.
> I copied the subroutine in another file
> compilation happens with -c to create .o
> but when I do -o to create exe it gives undefined references
>
> PS: I am new to fortran
>
>
>
> On Tue, May 29, 2018 at 10:05 PM, Steve Kargl <
> sgk@troutmask.apl.washington.edu> wrote:
>
> > On Tue, May 29, 2018 at 11:35:00AM +0530, nachiket k wrote:
> > > Hi,
> > > copygb2 has dependency on modfiles genereated from library g2
> > >
> > > Makefile parameters for g2 were
> > >
> > > Original for intel
> > >
> > > DEFS=-DLINUX
> > > FC=ftn
> > > CC=cc
> > > CPP=CC -P
> > > MODDIR=../g2/lib/temp/incmod/g2_4
> > >
> > > FFLAGS=-O3 -g -assume noold_ldout_format -module $(MODDIR)
> > >
> >
> > Remove all options and only add those that are needed.
> > You can remove '-assume noold_ldout_format' as that is
> > an Intel specific loader option. Change -module to -I.
> >
> > --
> > Steve
> >
next prev parent reply other threads:[~2018-05-30 11:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 11:24 nachiket k
2018-05-28 15:38 ` Steve Kargl
2018-05-29 6:05 ` nachiket k
2018-05-29 16:35 ` Steve Kargl
2018-05-30 9:55 ` nachiket k
2018-05-30 11:43 ` Martin Tee via fortran [this message]
2018-05-30 12:05 ` nachiket k
2018-05-30 12:23 Dominique d'Humières
2018-05-30 12:56 ` nachiket k
2018-05-30 13:35 ` Dominique d'Humières
2018-05-31 8:06 ` nachiket k
2018-05-31 13:34 ` Dominique d'Humières
2018-05-31 15:12 ` Steve Kargl
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=1527678731.6484.2.camel@btinternet.com \
--to=fortran@gcc.gnu.org \
--cc=martintee@btinternet.com \
--cc=nachiket316@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).