From: kunal ghosh <kunalpghosh@gmail.com>
To: cygwin@cygwin.com
Subject: errors while doing 'make' for openTimer installation
Date: Sat, 12 Nov 2016 10:45:00 -0000 [thread overview]
Message-ID: <CAAgSk3gG7DfVeqf67a_uJLddLQM1+Z9jC-TPpAx+8XtZCkhB_Q@mail.gmail.com> (raw)
Hi,
I am trying to install OpenTimer on Cygwin
I do below (saw some update on this in cygwin mailing list 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
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. Can you please help?
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);
Thanks
Kunal
--
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:[~2016-11-12 3:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAAgSk3gG7DfVeqf67a_uJLddLQM1+Z9jC-TPpAx+8XtZCkhB_Q@mail.gmail.com \
--to=kunalpghosh@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).