From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: problem installing openTimer in cygwin
Date: Fri, 11 Nov 2016 11:57:00 -0000 [thread overview]
Message-ID: <CAEhDDbCs2waHJqM01YL3L66vuCEY-UEvAZwbsP7M6MyYm7Jc4Q@mail.gmail.com> (raw)
In-Reply-To: <CAAgSk3gsyX=4JKoWi9v4+_fk6SckoZ8xCMN-SrEKYANKcviRAg@mail.gmail.com>
Hi Kunal,
On Fri, Nov 11, 2016 at 7:21 AM, kunal ghosh wrote:
> Hi
> I am trying to install OpenTimer software on my Windows 7 machine
> through cygwin, using standard steps "./configure", "make" , "make
> install"
>
> ./configure gives me the below errors for which I have googled and
> didnt founf anything constructive:
>
> Kunal@Kunal-PC /cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5
> $ grep error config.log
configure tries to compile a variety of throw-away programs to check
for the capabilities of the system.
Lots of errors in config.log are expected.
You should only look at config.log if configure reports an error and
fails to generate the Makefile.
(snip)
> g++: error: unrecognized command line option '-V'
> g++: fatal error: no input files
> g++: error: unrecognized command line option '-qversion'
> g++: fatal error: no input files
Here it probably tries to find the switch that prints the compiler version.
It has to try every known switch that does that; but no compiler will
accept every possibility.
These errors are harmless. They tell configure that GCC doesn't
support the -qversion switch
(-qversion is accepted by IBM's XL C/C++ compiler for AIX).
(snip)
> /usr/lib/gcc/x86_64-pc-cygwin/5.4.0/include/omp.h:39:3: error:
> 'omp_lock_t' does not name a type
> /usr/lib/gcc/x86_64-pc-cygwin/5.4.0/include/omp.h:86:28: error:
> variable or field 'omp_init_lock' declared void
Here it probably found out that OMP is not supported.
> Inspite of the above errors, I go ahead with 'make' command and I get
> below errors:
>
> src/utilities.cc: In function 'pid_t
> google::glog_internal_namespace_::GetTID()':
> src/utilities.cc:265:29: error: 'GetCurrentThreadId' was not declared
> in this scope
> return GetCurrentThreadId();
> ^
This suggests that OpenTimer thinks it's being compiled under Windows
(GetCurrentThreadId is a Win32 API function). It failed to identify
Cygwin as a POSIX platform. You could try submitting a bug report or,
if you're a programmer, fix it and supply a patch:
"OpenTimer is actively maintained by Tsung-Wei Huang. If you are
discovering any bugs or are interested in pursuing an OpenTimer-based
project with me, please contact twh760812@gmail.com"
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds
--
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:[~2016-11-11 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 8:58 kunal ghosh
2016-11-11 11:57 ` Csaba Raduly [this message]
2016-11-11 14:06 ` kunal ghosh
2016-11-11 14:13 ` kunal ghosh
2016-11-11 16:10 ` kunal ghosh
2016-11-13 19:50 ` Csaba Raduly
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=CAEhDDbCs2waHJqM01YL3L66vuCEY-UEvAZwbsP7M6MyYm7Jc4Q@mail.gmail.com \
--to=rcsaba@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).