From: Keith Seitz <keiths@redhat.com>
To: Ben Pazolli <bpazolli@gmail.com>
Cc: insight@sourceware.org
Subject: Re: Compiling on cygwin
Date: Wed, 25 Mar 2009 23:21:00 -0000 [thread overview]
Message-ID: <49CABC7D.1050702@redhat.com> (raw)
In-Reply-To: <6d6652520903212016s50535a40t34a94cf6bf8c0770@mail.gmail.com>
Ben Pazolli wrote:
> I can't get insight to compile on cygwin so I can run insight on
> windows. I can do ./configure but when I run make it always exits with
> messages like '...pex-unix.c:518: error: 'F_SETFD' undelared...'
> '...pex-unix.c:518: error: 'FD_CLOEXEC' undeclared...' '...make[2]:
> *** [pex-unix.o] Error 1...' and '...make[1]: ***[all-libiberty] Error
> 2...'. Any Ideas? I am using the standard installation of cygwin and
> added the mingw installation and the gmp. I really really want to
> compile this.
I don't often test on cygwin, but I know I compiled it on that platform
a couple of months ago when I did the big configury overhaul.
Nonetheless, you are having problems with libiberty with some standard
defines missing... Either there is a compiler flag which is wrong or you
are missing some required software (like a library)... You might want to
ask on a more cygwin/mingw savvy mailing list than this one. [Have you
tried doing a web search?]
Otherwise, it would be helpful to have the complete output of configure
and make.
Keith
next prev parent reply other threads:[~2009-03-25 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 3:16 Ben Pazolli
2009-03-25 23:21 ` Keith Seitz [this message]
[not found] ` <6d6652520903260514o3b8ff517hcb7c0d8de75f09e1@mail.gmail.com>
2009-03-31 18:13 ` Keith Seitz
2009-04-01 15:11 ` Spencer Oliver
2009-04-01 15:15 ` Keith Seitz
2009-06-10 16:09 ` Gene Smith
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=49CABC7D.1050702@redhat.com \
--to=keiths@redhat.com \
--cc=bpazolli@gmail.com \
--cc=insight@sourceware.org \
/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).