From: dominiq@lps.ens.fr (Dominique Dhumieres)
To: felipepimenta@gmail.com, arjen.markus895@gmail.com
Cc: sgk@troutmask.apl.washington.edu, fortran@gcc.gnu.org,
dominiq@lps.ens.fr
Subject: Re: Undefined symbols for architecture x86_64
Date: Tue, 22 Oct 2013 17:06:00 -0000 [thread overview]
Message-ID: <20131022170625.A63FDF7@mailhost.lps.ens.fr> (raw)
In-Reply-To: <CAMCbSMpeS45D-vONZ8+Uo+C=zmCN4mtctGKOLcpBkpW5TT0sjQ@mail.gmail.com>
The trick is to compile the Fortran files with '-fno-underscoring'.
Dominique
next prev parent reply other threads:[~2013-10-22 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 17:50 Dominique Dhumieres
2013-10-22 10:54 ` Felipe Pimenta
2013-10-22 12:30 ` Arjen Markus
2013-10-22 17:06 ` Dominique Dhumieres [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-20 0:49 Felipe Pimenta
2013-10-20 1:00 ` Steve Kargl
2013-10-20 10:22 ` Arjen Markus
2014-07-01 19:01 ` mcz1216
2014-07-01 21:43 ` Tim Prince
2014-07-01 19:49 ` Tobias Schlüter
2017-07-09 3:12 ` OWEN1412
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=20131022170625.A63FDF7@mailhost.lps.ens.fr \
--to=dominiq@lps.ens.fr \
--cc=arjen.markus895@gmail.com \
--cc=felipepimenta@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).