public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: we <kyjdzw@21cn.com>
Cc: sid@sources.redhat.com
Subject: Re: error build sid on cygwin
Date: Sun, 24 Oct 2004 14:03:00 -0000	[thread overview]
Message-ID: <20041024140250.GE15001@redhat.com> (raw)
In-Reply-To: <P0958975794360.13552@webmail1.inner-21cn.com>

Hi -


> I am trying to build SID,  and I get the following error.
> [...]
> make[2]: Entering directory `/cygdrive/h/bak/src-041024/tcl/win'
> gcc -c -g -O2  -Wall -Wconversion  -I"./../generic" -I"." -mwin32   -DHAVE_NO_SEH=1 -DEXCEPTION_DISPOSITION=int   -DBUILD_tcl "tclWin32Dll.c" -o tclWin32Dll.o
> In file included from ../win/tclWinPort.h:72,
>                  from ../generic/tclPort.h:22,
>                  from tclWinInt.h:21,
>                  from tclWin32Dll.c:15:
> /usr/include/w32api/winsock2.h:95:2: warning: #warning "fd_set and associated macros have been defined in sys/types.      This may cause runtime problems with W32 sockets"
> tclWin32Dll.c:54: error: initializer element is not constant
> [...]

That's odd in that I would expect the UNIX / cygwin port of tcl to be
selected, not the Windows one, in such a configuration.  Maybe some
major src/tcl replacement has occurred that broke this logic.

I recommend removing (!) the tcl and tk subdirectories from the sid
sources, then configuring anew.  In this case, the configury should
attempt to find the system's tcl libraries (if any), and failing that,
it should just omit the tcl-bridge component.


- FChE

  reply	other threads:[~2004-10-24 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-24 12:55 we
2004-10-24 14:03 ` Frank Ch. Eigler [this message]
2004-10-24 16:59 we

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=20041024140250.GE15001@redhat.com \
    --to=fche@redhat.com \
    --cc=kyjdzw@21cn.com \
    --cc=sid@sources.redhat.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).