public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Andy Hare" <ahare@btinternet.com>
To: "Keith Seitz" <keiths@cygnus.com>
Cc: "Insight Mail list" <insight@sourceware.cygnus.com>
Subject: Re: Problems building TCL for insight on cygwin & win2k
Date: Fri, 26 Oct 2001 14:22:00 -0000	[thread overview]
Message-ID: <089b01c15e64$563d4100$0100000a@dualbeast> (raw)
In-Reply-To: <Pine.GSO.4.33.0110251528590.23990-100000@makita.cygnus.com>

Keith,

    I have now re-configed into an empty directory and re-built without
the -mwin32 flags. I now get the errors shown below:

gcc -c -g -O2 -Wall -Wconversion  -I"/GNU-Source-Code/src/tcl/win/../generic
" -I"/GNU-Source-Code/src/tcl/win" -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=
1 -DHAVE_TZNAME=1   -DBUILD_tcl
"/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c" -o tclPipe.o
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c: In function
`TclCleanupChildren':
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:313: invalid operands to
binary &
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:313: invalid operands to
binary >>
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:318: invalid operands to
binary &
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:320: invalid operands to
binary >>
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:325: invalid operands to
binary &
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:325: invalid operands to
binary &
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:329: invalid operands to
binary &
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:331: invalid operands to
binary &
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:336: invalid operands to
binary &
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:340: invalid operands to
binary >>
/GNU-Source-Code/src/tcl/win/../generic/tclPipe.c:342: invalid operands to
binary >>
make[3]: *** [tclPipe.o] Error 1

This is the problem I started with before adding the win32 flags. The
problem is that the lines use a set of macros defined in tclunixport.h that
assume that the value passed is an int, but the value passed isn't an int.
Here is the snippet of code fromthe .h file:


#ifdef _AIX
#   define WAIT_STATUS_TYPE pid_t
#else
#ifndef NO_UNION_WAIT
#   define WAIT_STATUS_TYPE union wait
#else
#   define WAIT_STATUS_TYPE int
#endif
#endif

/*
 * Supply definitions for macros to query wait status, if not already
 * defined in header files above.
 */

#ifndef WIFEXITED
#   define WIFEXITED(stat)  (((*((int *) &(stat))) & 0xff) == 0)
#endif

The value passed in the line that give erros in tclpipe.c use this WIFEXIT
but the value passed is of type WAIT_STATUS_TYPE and I guesss is of type
union wait rather than the int. So should there be a definition for
NO_UNION_WAIT or should the defines be within the #ifndef NO_UNION_WAIT so
they take account of the differeing types.

Andy Hare
www.ahare.btinternet.co.uk

----- Original Message -----
From: "Keith Seitz" <keiths@cygnus.com>
To: "Andy Hare" <ahare@btinternet.com>
Cc: "Insight Mail list" <insight@sourceware.cygnus.com>
Sent: Thursday, October 25, 2001 11:31 PM
Subject: Re: Problems building TCL for insight on cygwin & win2k


> On Thu, 25 Oct 2001, Andy Hare wrote:
>
> > Have now re-built the config and the run the make in the /build/tcl
> > directory. Problem still exists with the missing #defines for MASK_SIZE
and
> > SELECT_MASK. Tried Ians suggestion of -mno-win32 and now the tcl stuff
> > compiles without a problem. So I will look at the way tcl is configured
to
> > see if I can find the problem and the missing -mno-win32.
>
> Hmm. I don't understand why this doesn't work for you, but it works for
> me. What is gcc -v?
>
> > Thanks for all your help, I will go back modify the make files in the
tcl
> > and then continue.
>
> This should not be necessary. I am really confused about why it is.
>
> Does the repository build for anyone else out there? I can do a checkout
> and build it as-is with the latest cygwin (1.3.3) and the gcc distributed
> with it (gcc-2.95.3-5 cygwin special).
>
> I am confused.
>
> Keith
>
>

  parent reply	other threads:[~2001-10-26 14:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 12:10 Andy Hare
2001-10-25 12:17 ` Ian Roxborough
2001-10-25 12:28   ` Christopher Faylor
2001-10-25 12:30     ` Christopher Faylor
2001-10-25 12:44     ` Ian Roxborough
2001-10-25 12:24 ` Keith Seitz
2001-10-25 13:54   ` Andy Hare
2001-10-25 14:00     ` Keith Seitz
2001-10-25 14:47       ` Andy Hare
2001-10-25 14:57         ` Keith Seitz
2001-10-25 15:21       ` Andy Hare
2001-10-25 15:31         ` Keith Seitz
2001-10-25 16:10           ` Andy Hare
2001-10-25 16:15             ` Christopher Faylor
2001-10-25 16:41               ` Ian Roxborough
2001-10-26 14:34                 ` Andy Hare
2001-10-26 14:22           ` Andy Hare [this message]
2001-10-26 14:51             ` Ian Roxborough
2001-10-28  2:08               ` Andy Hare
2001-10-28  8:31                 ` Christopher Faylor
2001-10-28 12:12                   ` Andy Hare
2001-10-28 15:02                     ` Christopher Faylor
2001-10-28  2:12               ` Andy Hare
2001-10-27 13:22           ` Andy Hare

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='089b01c15e64$563d4100$0100000a@dualbeast' \
    --to=ahare@btinternet.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=keiths@cygnus.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).