Re: problem installing openTimer in cygwin
On Fri, Nov 11, 2016 at 3:12 PM, kunal ghosh wrote:
> Also, I went ahead modifying the utilities.h to point to
> windows/port.h, instead of port.h.
That sounds dangerous
> And some more hacks to get rid of other errors. Now 'make' gives me
> the below errors. Not sure how to resolve this
>
> src/logging.cc: In member function 'bool
> google::{anonymous}::LogFileObject::CreateLogfile(const string&)':
> src/logging.cc:895:43: error: 'symlink' was not declared in this scope
> if (symlink(linkdest, linkpath.c_str()) != 0) {
>^
> src/logging.cc:904:45: error: 'symlink' was not declared in this scope
>if (symlink(filename, linkpath.c_str()) != 0) {
symlink() is in unistd.h
You need to make _DEFAULT_SOURCE or _GNU_SOURCE be defined for
symlin() to be visible on Cygwin.
It seems to me that the author of OpenTimer does not understand what
Cygwin is or what it does,
as evidenced by lines like
#if defined( WIN32) || defined(CYGWIN)
and the attempt to use Win32 instead of pthreads when compiling
Cygwin. Unfortunately (for you), I have no interest in OpenTimer, so I
can't help you any further.
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
Re: problem installing openTimer in cygwin
Also, I went ahead modifying the utilities.h to point to
windows/port.h, instead of port.h.
And some more hacks to get rid of other errors. Now 'make' gives me
the below errors. Not sure how to resolve this
src/logging.cc: In member function 'bool
google::{anonymous}::LogFileObject::CreateLogfile(const string&)':
src/logging.cc:895:43: error: 'symlink' was not declared in this scope
if (symlink(linkdest, linkpath.c_str()) != 0) {
^
src/logging.cc:904:45: error: 'symlink' was not declared in this scope
if (symlink(filename, linkpath.c_str()) != 0) {
^
src/logging.cc: In function 'void google::TruncateLogFile(const char*,
google::int64, google::int64)':
src/logging.cc:1828:69: error: 'O_NOFOLLOW' was not declared in this scope
if (strncmp(procfd_prefix, path, strlen(procfd_prefix))) flags |= O_NOFOLLOW;
^
src/logging.cc:1867:68: error: 'pread' was not declared in this scope
while ((bytesin = pread(fd, copybuf, sizeof(copybuf), read_offset)) > 0) {
^
src/logging.cc:1868:57: error: 'pwrite' was not declared in this scope
bytesout = pwrite(fd, copybuf, bytesin, write_offset);
^
make[2]: *** [Makefile:1176: src/libglog_la-logging.lo] Error 1
make[2]: Leaving directory
'/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5/3rd-party/glog-0.3.3'
make[1]: *** [Makefile:2676: all-recursive] Error 1
make[1]: Leaving directory '/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5'
make: *** [Makefile:846: all] Error 2
On Fri, Nov 11, 2016 at 7:26 PM, kunal ghosh wrote:
> Hi Csaba,
>
> The original error has gone. Now I get the below error:
>
> I do below (saw some update on this and so using --host): --- Works fine
> ./configure --host=x86_64-w64-mingw32
>
> and then below :
>
> Kunal@Kunal-PC /cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5
> $ make
> make all-recursive
> make[1]: Entering directory '/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5'
> Making all in 3rd-party/glog-0.3.3
> make[2]: Entering directory
> '/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5/3rd-party/glog-0.3.3'
> /bin/sh ./libtool --tag=CXX --mode=compile x86_64-w64-mingw32-g++
> -DHAVE_CONFIG_H -I. -I./src -I./src-Wall -Wwrite-strings
> -Woverloaded-virtual -Wno-sign-compare -DNO_FRAME_POINTER -DNDEBUG
> -g -O2 -MT src/libglog_la-logging.lo -MD -MP -MF
> src/.deps/libglog_la-logging.Tpo -c -o src/libglog_la-logging.lo `test
> -f 'src/logging.cc' || echo './'`src/logging.cc
> libtool: compile: x86_64-w64-mingw32-g++ -DHAVE_CONFIG_H -I. -I./src
> -I./src -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare
> -DNO_FRAME_POINTER -DNDEBUG -g -O2 -MT src/libglog_la-logging.lo -MD
> -MP -MF src/.deps/libglog_la-logging.Tpo -c src/logging.cc
> -DDLL_EXPORT -DPIC -o src/.libs/libglog_la-logging.o
> In file included from src/logging.cc:32:0:
> src/utilities.h:78:19: fatal error: port.h: No such file or directory
> compilation terminated.
> make[2]: *** [Makefile:1176: src/libglog_la-logging.lo] Error 1
> make[2]: Leaving directory
> '/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5/3rd-party/glog-0.3.3'
> make[1]: *** [Makefile:2676: all-recursive] Error 1
> make[1]: Leaving directory '/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5'
> make: *** [Makefile:846: all] Error 2
>
> Can you pelase help how to workaround this?
>
>
>
> On Fri, Nov 11, 2016 at 6:42 PM, kunal ghosh wrote:
>> Thanks Csaba. Let me check with owner of this tool and keep you posted
>>
>> On Fri, Nov 11, 2016 at 2:28 PM, Csaba Raduly wrote:
>>> 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 accepte
Re: problem installing openTimer in cygwin
Hi Csaba, The original error has gone. Now I get the below error: I do below (saw some update on this and so using --host): --- Works fine ./configure --host=x86_64-w64-mingw32 and then below : Kunal@Kunal-PC /cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5 $ make make all-recursive make[1]: Entering directory '/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5' Making all in 3rd-party/glog-0.3.3 make[2]: Entering directory '/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5/3rd-party/glog-0.3.3' /bin/sh ./libtool --tag=CXX --mode=compile x86_64-w64-mingw32-g++ -DHAVE_CONFIG_H -I. -I./src -I./src-Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -DNO_FRAME_POINTER -DNDEBUG -g -O2 -MT src/libglog_la-logging.lo -MD -MP -MF src/.deps/libglog_la-logging.Tpo -c -o src/libglog_la-logging.lo `test -f 'src/logging.cc' || echo './'`src/logging.cc libtool: compile: x86_64-w64-mingw32-g++ -DHAVE_CONFIG_H -I. -I./src -I./src -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -DNO_FRAME_POINTER -DNDEBUG -g -O2 -MT src/libglog_la-logging.lo -MD -MP -MF src/.deps/libglog_la-logging.Tpo -c src/logging.cc -DDLL_EXPORT -DPIC -o src/.libs/libglog_la-logging.o In file included from src/logging.cc:32:0: src/utilities.h:78:19: fatal error: port.h: No such file or directory compilation terminated. make[2]: *** [Makefile:1176: src/libglog_la-logging.lo] Error 1 make[2]: Leaving directory '/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5/3rd-party/glog-0.3.3' make[1]: *** [Makefile:2676: all-recursive] Error 1 make[1]: Leaving directory '/cygdrive/c/VSD/Tools/openTimer/OpenTimer-1.0.5' make: *** [Makefile:846: all] Error 2 Can you pelase help how to workaround this? On Fri, Nov 11, 2016 at 6:42 PM, kunal ghosh wrote: > Thanks Csaba. Let me check with owner of this tool and keep you posted > > On Fri, Nov 11, 2016 at 2:28 PM, Csaba Raduly wrote: >> 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 twh760...@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 >> > > > > -- > Thanks & Regards > Kunal P Ghosh > (www.vlsisystemdesign.com) > > "A pessimist always sees difficulty in ever
Re: problem installing openTimer in cygwin
Thanks Csaba. Let me check with owner of this tool and keep you posted On Fri, Nov 11, 2016 at 2:28 PM, Csaba Raduly wrote: > 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 twh760...@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 > -- Thanks & Regards Kunal P Ghosh (www.vlsisystemdesign.com) "A pessimist always sees difficulty in every opportunity, An optimist always sees opportunity in every difficulty" -- 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
Re: problem installing openTimer in cygwin
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 twh760...@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
