public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew DeFaria <Andrew@DeFaria.com>
To: cygwin@cygwin.com
Subject: Re: real beginer
Date: Tue, 23 Oct 2012 22:23:00 -0000	[thread overview]
Message-ID: <k675bo$q08$1@ger.gmane.org> (raw)
In-Reply-To: <1351028816534-93921.post@n5.nabble.com>

On 10/23/2012 2:46 PM, Trixie wrote:
> On 10/23/2012 12:46 PM, Trixie wrote:
>>> I have liblapack-devel instaled and did ./configure and make . It took
>>> some
>>> time but it finished.
>> Did make finish successfully, returning a 0 status? Did you have a
>> bigdft.exe file? If you type "ls bigdft" do you see an executable?
>> (Note: The file's name is actually bigdft.exe but ls will list it as
>> bigdft).
> /i type ls bigdft and there's "No such file or directory" and i cant find
> bigdft.exe file anywhere. That means install and make didnt finish well,
> right?
Probably. You could do something like: make; echo "Status from make was $?"

The $? is the return status from the previous command. That will only 
tell you if the make turned 0 for success. The output of make would be 
much more instructive.
> posinp.xyz is there./
AFAICT posinp.xyz is not produced from the make.

You really should approach the people who maintain this package and ask 
them about it. This package is not Cygwin.
-- 
Andrew DeFaria <http://defaria.com>
By the time you make ends meet, they move the ends.


--
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:[~2012-10-23 22:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 13:28 Trixie
2012-10-23 13:32 ` Earnie Boyd
2012-10-23 13:33 ` Brian Wilson
2012-10-23 13:53 ` Eliot Moss
2012-10-23 13:53 ` Trixie
2012-10-23 14:04   ` Christopher Faylor
2012-10-23 14:19 ` Andrew DeFaria
2012-10-23 15:06   ` Bill Meier
2012-10-23 14:31 ` Trixie
2012-10-23 14:48   ` Christopher Faylor
2012-10-23 16:35   ` Eliot Moss
2012-10-23 17:18     ` marco atzeri
2012-10-23 19:46       ` Trixie
2012-10-23 21:22         ` Andrew DeFaria
2012-10-23 21:47           ` Trixie
2012-10-23 22:23             ` Andrew DeFaria [this message]
2012-10-23 22:35               ` Trixie
2012-10-23 23:19                 ` Eliot Moss
2012-10-24  0:51                   ` Eliot Moss
2012-10-24 12:17                     ` Trixie
2012-10-24 13:59                       ` Andrew DeFaria
2012-10-24 14:12                         ` Eliot Moss
2012-10-24 14:13                         ` Trixie
2012-10-24 15:02                           ` Eliot Moss
2012-10-24 18:25                             ` Trixie
2012-10-24 21:06                               ` René Berber
2012-10-24 23:02                                 ` Trixie
2012-10-25  7:02                                   ` René Berber
2012-10-25 12:51                                     ` Warren Young
2012-10-25 14:24                                       ` Trixie
2012-10-23 17:49     ` Andrew DeFaria
2012-10-23 17:35 ` Sven Köhler

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='k675bo$q08$1@ger.gmane.org' \
    --to=andrew@defaria.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).