Tcl Source Code

View Ticket
Login
Ticket UUID: 1075936
Title: add cygwin support
Type: Patch Version: None
Submitter: aotto1968 Created on: 2004-11-30 11:52:27
Subsystem: 52. Portability Support Assigned To: nijtmans
Priority: 5 Medium Severity:
Status: Closed Last Modified: 2012-03-15 17:24:26
Resolution: Out of Date Closed By: nijtmans
    Closed on: 2012-03-15 10:24:26
Description:
Hi, 
 
 the patch adds CYGWIN support for the 'unix' and  
 the 'win' tree to tcl8.4.8 
 
 
mfg 
 
  aotto
User Comments: nijtmans added on 2012-03-15 17:24:26:

allow_comments - 1

Cygwin solved this for us: Cygwin includes (since febr '12) the unix
build of Tcl 8.5 in stead of the Windows build. This means that
all such kinds of cludges are not neccessary any more.

Remark 2: Cygwin has a mingw-w64 package now which can
cross-compile Win32 on Cygwin. Tcl 8.5 has support for
cross-compilation now, so just use
    configure --host=i686-w64-mingw ....
It appears to work fine.

nijtmans added on 2009-12-21 20:10:31:
Just found the most important reason why Cygwin support is so difficult: There is a conflict between the fd_set macro's in sys/types.h and
winsock2. The standard Cygwin way of dealing with that is including
"winsock2.h" before sys/types.h, but because sys/types.h is included
from other header files in turn (e.g. stdlib.h) it is not completely
streightforward.

Still, I'll have a look.........

mdejong added on 2005-06-30 04:19:56:
Logged In: YES 
user_id=90858

Building under Cygwin is not supported. Building under
Cygwin with
a mingw cross compile is REALLY not supported. It is just
too error
prone. The right way to build is using a native mingw
toolchain. That
support is already included in Tcl, works just fine, and
will continue
to work. Look, we have been over this issue over and over
again. The
way it builds right now is the right way. Bending over
backwards to
try and get things building under Cygwin with -mno-cygwin is
just
not going to happen. On the other hand, if someone was
willing to do
the work to keep a Cygwin build of Tcl going, then that would be
helpful.

aotto1968 added on 2005-01-07 22:33:48:
Logged In: YES 
user_id=1030114

Hi,

  this was a change to compile native WINDOWS in a CYGWIN
environment !!!!

  if you want to have a native CYGWIN build in a CYGWIN
environment you havt to choose the UNIX build

probably you misanderstood the relationship between CYGWIN
WINDOWS and UNIX  ...

  - (unix TREE) -> native CYGWIN means native UNIX on a
WINDOWS box
  - (win TREE) -> native WINDOWS means native WINDOWS on a
WINDOWS box   (CYGWIN is just used as build environment
including a FREE compiler and autoconf build setup)


mfg

  aotto

kirben added on 2005-01-02 11:11:53:
Logged In: YES 
user_id=34715

The change to 'win' tree is wrong, you just changed a Cygwin 
build to a mingw cross-compile. That isn't improving native 
Cygwin support.

aotto1968 added on 2004-11-30 22:06:48:
Logged In: YES 
user_id=1030114

Hi, 
 
 the '[symbols]' is a need for Linux/GnuM4 build autoconf 
 if I don't use '[symbols]',  autoconf will break the build 
 -> I published this patch some time ago but it seems 
     nobody will see the problem :-( 
 solution: if it does not break your build .... 
 let it in ... 
 it '[symbols]' break anything please contact me 
 
mfg 
 
  aotto

dkf added on 2004-11-30 20:18:38:
Logged In: YES 
user_id=79902

Summary of changes to C files (there's also changes to
Makefile.in, tcl.m4 and the win configure.in, though the
changes of 'symbols' to '[symbols]' seems a little
gratuitous to me):

 • Cygwin uses _timezone instead of timezone

That's it.

aotto1968 added on 2004-11-30 18:53:21:

File Added - 110678: patch.1

Attachments: