From: Keith Seitz <keiths@redhat.com>
To: Jon Beniston <jon@beniston.com>
Cc: insight@sources.redhat.com
Subject: Re: Build failure on Cygwin
Date: Mon, 04 Jan 2010 20:18:00 -0000 [thread overview]
Message-ID: <4B424D16.6020204@redhat.com> (raw)
In-Reply-To: <000001ca8bec$6d6b6d20$48424760$@com>
On 01/02/2010 12:44 PM, Jon Beniston wrote:
> make[3]: Entering directory `/home/Jon/t/import/build/tcl/win'
> gcc -c -g -O2 -Wall -Wconversion -I"../../../src/tcl/win/../generic"
> -I"../../../src/tcl/win" -mwin32 -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\"
> -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\"
> -DHAVE_NO_SEH=1 -DEXCEPTION_DISPOSITION=int -DSTDC_HEADERS=1
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
> -DHAVE_UNISTD_H=1 -DBUILD_tcl ../../../src/tcl/win/../generic/tclAlloc.c -o
> tclAlloc.o
> In file included from
> ../../../src/tcl/win/../generic/../win/tclWinPort.h:72,
> from ../../../src/tcl/win/../generic/tclPort.h:22,
> from ../../../src/tcl/win/../generic/tclAlloc.c:29:
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../include/w32api/winsock2.h:103:
> 2: warning: #warning "fd_set and associated macros have been defined in
> sys/types. This may cause runtime problems with W32 sockets"
> In file included from
> ../../../src/tcl/win/../generic/../win/tclWinPort.h:72,
> from ../../../src/tcl/win/../generic/tclPort.h:22,
> from ../../../src/tcl/win/../generic/tclAlloc.c:29:
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../include/w32api/winsock2.h:632:
> error: conflicting types for 'select'
> /usr/include/sys/select.h:31: error: previous declaration of 'select' was
> here
I haven't seen this one yet, but I admit, I don't really use much other
than linux nowadays... I'm going to update my cygwin box and kick off a
build. It should be done in a few hours. [It's a 500MHz P3!]
>
> I've just been running configure with no options (which used to work for
> Cygwin 1.5.x). Is there a magic option to get it to work, or does something
> need fixing?
I'll get back to you on this...
Keith
next prev parent reply other threads:[~2010-01-04 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 20:49 Jon Beniston
2010-01-04 20:18 ` Keith Seitz [this message]
2010-01-11 18:20 ` Jon Beniston
2011-04-28 16:39 ` mizo_hazem_2
2011-04-28 16:53 ` Christopher Faylor
2010-01-15 16:53 Matthias Andree
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=4B424D16.6020204@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=jon@beniston.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).