public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cross complie linux make files onto a windows 7 machine using PGI Cygwin
Date: Thu, 09 Jun 2011 19:23:00 -0000	[thread overview]
Message-ID: <4DF11D81.4090701@cygwin.com> (raw)
In-Reply-To: <31812441.post@talk.nabble.com>

On 6/9/2011 2:43 PM, roba77 wrote:
>
> Hello,
>
>
>    I am very unfamiliar with linux/unix (don't even know the difference), but
> am trying to get some linux software to run on my Windows machine for my
> research. I have the makefiles for the software, and it is designed to be
> compiled in the PGI complier, which I also have. When i try to compile the
> software i start the bash shell through PGI, go to the directory of the
> makefiles and enter the command:
>
> make -f make_rrtm_linux_pgi
> or
> gmake -f make_rrtm_linux_pgi
>
> I've attached screenshots of both trials
> http://old.nabble.com/file/p31812441/Cygwin%2Bmake%2Bscreenshot.jpg
> in both cases, there seems to be an error, in the case of gmake, something
> seems to happen, but it makes a .o file (which I can't find) where I need to
> be making a .exe file.
>
> I have been stuck on this for a while, and obviously don't know what I'm
> doing, any help would be appreciated. The program I am trying to run is
> RRTM, an atmospheric modelling program available free at
> (rtweb.aer.com/rrtm_frame.html )

I can understand your confusion.  I spent 5 minutes at the RRTM link you
provided and could not find hide nor hair of anything remotely resembling
documentation on how to build their software.  I tried downloading one of
the source tarballs and came up with a link connection error.  Obviously,
you were able to get beyond this and at least theoretically, you found
some such documentation somewhere to describe something about a build
process, otherwise you wouldn't have gotten as far as you did.  So I can't
tell you much about how to build this package.  I can, however, tell you
that:

   1. Cygwin has no gmake command, only make.
   2. Given 1, it's questionable that you're Cygwin environment, assuming
      that's what you're using, is properly configured.
   3. Your problems really sound like issues with the RRTM build process.
      I'll hazard a guess that there aren't any RRTM experts or groupies
      hanging out on this list so I'd say your best bet for help with
      RRTM issues is the RRTM authors.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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

  reply	other threads:[~2011-06-09 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 18:44 roba77
2011-06-09 19:23 ` Larry Hall (Cygwin) [this message]
2011-06-09 19:28   ` Larry Hall (Cygwin)
2011-06-09 19:35   ` roba77
2011-06-10  1:11     ` Larry Hall (Cygwin)

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=4DF11D81.4090701@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.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).