From: Christian <cdeb77@gmail.com>
To: cygwin@cygwin.com
Subject: Re: gfortran and lapack problem
Date: Mon, 20 Oct 2014 15:42:00 -0000 [thread overview]
Message-ID: <CAHeeG7dVe_sCYb3qwbz=GiUXGm+RfqCkUV-gJMipkU12ntVo6Q@mail.gmail.com> (raw)
In-Reply-To: <BAY169-DS1987F409DAC3D45ABA0626A7970@phx.gbl>
I'm using 64 bit Cygwin.
I guess that the "compilation finished" message I got is because of my
compiling interface, so I don't think is important.
Regarding the checks you suggested:
$ cygcheck gfortran
Found: D:\Cygwin64\bin\gfortran.exe
Found: D:\Cygwin64\bin\gfortran.exe
Found: D:\Cygwin64\bin\gfortran.exe
D:\Cygwin64\bin\gfortran.exe
And then a bunch of dll's. When I check gfortran I get
$ which -a gfortran
/usr/bin/gfortran
/usr/bin/gfortran
/usr/bin/gfortran
While for blas:
$ which -a cygblas-0.dll
/usr/lib/lapack/cygblas-0.dll
Thanks!
On Mon, Oct 20, 2014 at 4:10 AM, Tony Kelman <tony@kelman.net> wrote:
>> I compile it as gfortran MyTest.f90 -o MyTest -llapack -lblas. I don't
>> get any errors (it says "compilation finished"), but the output file
>> doesn't print anything (neither the strings, or the variable info). If
>> I comment the "CALL DGESV" line, it does print everything (with
>> info=0, of course).
>
>
> 32 bit or 64 bit Cygwin? Works for me, I get
>
> $ gfortran MyTest.f90 -o MyTest -llapack -lblas
>
> $ ./MyTest
> Printing the results
> 0
> End printing
>
> So no "compilation finished" message. Might you have some other
> version of gfortran on your path? I believe cygcheck.out would
> list some of this information. Other things to check:
>
> which -a gfortran
> which -a cygblas-0.dll
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-10-20 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 6:35 Christian
2014-10-20 8:10 ` Tony Kelman
2014-10-20 15:42 ` Christian [this message]
2014-10-20 15:57 ` Marco Atzeri
2014-10-20 16:25 ` Christian
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='CAHeeG7dVe_sCYb3qwbz=GiUXGm+RfqCkUV-gJMipkU12ntVo6Q@mail.gmail.com' \
--to=cdeb77@gmail.com \
--cc=cygwin@cygwin.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).