build error for tcl8.4.14 on Windows Vista (using cygwin)

Hello,

I am trying to build tcl8.4.14 on windows vista ultimate (32bits)
with the latest version of cygwin 1.5.24-2 (gcc 3.4.4).
My machine is uses a core 2 intel processor.

I included the log of the ./configure and of the make in attachment.

I found a post on such a problem here:
https://sourceforge.net/tracker/?func=detail&atid=310894&aid=656765&g...

but this bug is supposed to have been solved in August 2004.

Is it a regression?
Any clue on how to build tcl on my platform.

Regards,
Arnaud.

[ make.log.txt ]
gcc -pipe -c -O -DTCL_DBGX= -Wall -Wno-implicit-int -fno-strict-aliasing -I/cygdrive/c/Apps/ns/tcl8.4.14/unix/../generic -I/cygdrive/c/Apps/ns/tcl8.4.14/unix -DNO_VALUES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_PARAM_H=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 -DUSE_TERMIOS=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_TZNAME=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 -DNO_UNION_WAIT=1 -DHAVE_SIGNED_CHAR=1 -DHAVE_LANGINFO=1 -DHAVE_FTS=1 -DHAVE_SYS_IOCTL_H=1 -DTCL_SHLIB_EXT=\"\" /cygdrive/c/Apps/ns/tcl8.4.14/unix/../generic/tclClock.c
/cygdrive/c/Apps/ns/tcl8.4.14/unix/../generic/tclClock.c: In function `FormatClock':
/cygdrive/c/Apps/ns/tcl8.4.14/unix/../generic/tclClock.c:314: warning: assignment makes integer from pointer without a cast
/cygdrive/c/Apps/ns/tcl8.4.14/unix/../generic/tclClock.c:315: error: invalid lvalue in assignment
/cygdrive/c/Apps/ns/tcl8.4.14/unix/../generic/tclClock.c:360: error: invalid lvalue in assignment
make: *** [tclClock.o] Error 1

[ configure.log.txt ]
loading cache ./config.cache
checking whether to use symlinks for manpages... no
checking whether to compress the manpages... no
checking whether to add a package name suffix for the manpages... no
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking dirent.h... (cached) yes
checking for errno.h... (cached) yes
checking for float.h... (cached) yes
checking for values.h... (cached) no
checking for limits.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for sys/wait.h... (cached) yes
checking for dlfcn.h... (cached) yes
checking for unistd.h... (cached) yes
checking for sys/param.h... (cached) yes
checking if the compiler understands -pipe... yes
checking for building with threads... no (default)
checking for sin... (cached) yes
checking for main in -lieee... (cached) no
checking for main in -linet... (cached) no
checking for net/errno.h... (cached) no
checking for connect... (cached) yes
checking for gethostbyname... (cached) yes
checking how to build libraries... shared
checking for ranlib... (cached) ranlib
checking if 64bit support is requested... no
checking if 64bit Sparc VIS support is requested... no
checking system version... (cached) CYGWIN_NT-6.0-1.5.24(0.156/4/2)
checking for dlopen in -ldl... (cached) yes
checking for ar... (cached) ar
Can't figure out how to do dynamic loading or shared libraries
on this system.
checking for build with symbols... no
checking for required early compiler flags... (cached) (cached) (cached) none
checking for 64-bit integer type... (cached) long long
checking for struct dirent64... (cached) no
checking for struct stat64... (cached) no
checking for open64... (cached) no
checking for lseek64... (cached) no
checking for off64_t... (cached) no
checking whether byte ordering is bigendian... (cached) no
checking for getcwd... (cached) yes
checking for opendir... (cached) yes
checking for strstr... (cached) yes
checking for strtol... (cached) yes
checking for strtoll... (cached) yes
checking for strtoull... (cached) yes
checking for tmpnam... (cached) yes
checking for waitpid... (cached) yes
checking for strerror... (cached) yes
checking for getwd... (cached) yes
checking for wait3... (cached) yes
checking for uname... (cached) yes
checking for realpath... (cached) yes
checking for sys/modem.h... (cached) no
checking termios vs. termio vs. sgtty... (cached) termios
checking for fd_set in sys/types... (cached) yes
checking whether struct tm is in sys/time.h or time.h... (cached) time.h
checking for sys/time.h... (cached) yes
checking whether time.h and sys/time.h may both be included... (cached) yes
checking for tm_zone in struct tm... (cached) no
checking for tzname... (cached) yes
checking for gmtime_r... (cached) yes
checking for localtime_r... (cached) yes
checking tm_tzadj in struct tm... (cached) no
checking tm_gmtoff in struct tm... (cached) no
checking long timezone variable... (cached) no
checking time_t timezone variable... (cached) no
checking for st_blksize in struct stat... (cached) yes
checking for fstatfs... (cached) yes
checking for 8-bit clean memcmp... (cached) yes
checking for memmove... (cached) yes
checking proper strstr implementation... (cached) ok
checking for strtoul... (cached) yes
checking proper strtoul implementation... (cached) ok
checking for strtod... (cached) yes
checking proper strtod implementation... (cached) ok
checking for strtod... (cached) yes
checking for Solaris2.4/Tru64 strtod bugs... (cached) ok
checking for ANSI C header files... (cached) yes
checking for mode_t... (cached) yes
checking for pid_t... (cached) yes
checking for size_t... (cached) yes
checking for uid_t in sys/types.h... (cached) yes
checking for socklen_t... (cached) yes
checking for opendir... (cached) yes
checking union wait... (cached) no
checking for strncasecmp... (cached) yes
checking for BSDgettimeofday... (cached) no
checking for gettimeofday... (cached) yes
checking for gettimeofday declaration... (cached) present
checking whether char is unsigned... (cached) no
checking signed char declarations... (cached) yes
checking for a putenv() that copies the buffer... (cached) no
checking for langinfo.h... (cached) yes
checking whether to use nl_langinfo... (cached) yes
checking for fts... (cached) yes
checking for sys/ioctl.h... (cached) yes
checking for sys/filio.h... (cached) no
checking system version... (cached) CYGWIN_NT-6.0-1.5.24(0.156/4/2)
checking FIONBIO vs. O_NONBLOCK for nonblocking I/O... O_NONBLOCK
creating ./config.status
creating Makefile
creating dltest/Makefile
creating tclConfig.sh

Hello,

I am trying to build tcl8.4.14 on windows vista ultimate (32bits)
with the latest version of cygwin 1.5.24-2 (gcc 3.4.4).
My machine is uses a core 2 intel processor.

I included the log of the ./configure and of the make in attachment.

I found a post on such a problem here:
https://sourceforge.net/tracker/?func=detail&atid=310894&aid=656765&g...

but this bug is supposed to have been solved in August 2004.

Is it a regression?
Any clue on how to build tcl on my platform.

Regards,
Arnaud.

Hello,

I am trying to build tcl8.4.14 on windows vista ultimate (32bits)
with the latest version of cygwin 1.5.24-2 (gcc 3.4.4).
My machine is uses a core 2 intel processor.

I included the log of the ./configure and of the make in attachment.

I found a post on such a problem here:
https://sourceforge.net/tracker/?func=detail&atid=310894&aid=656765&g...

but this bug is supposed to have been solved in August 2004.

Is it a regression?
Any clue on how to build tcl on my platform.

Regards,
Arnaud.

arnaud.legout schrieb:

> Hello,

> I am trying to build tcl8.4.14 on windows vista ultimate (32bits)
> with the latest version of cygwin 1.5.24-2 (gcc 3.4.4).
> My machine is uses a core 2 intel processor.

> I included the log of the ./configure and of the make in attachment.

Any specific reason to try a cygwin build instead of a simpler native
windows build?

You can build Tcl just fine with the msys based gcc system, which
creates native windows binaries.

Michael

Michael Schlenker wrote:
> You can build Tcl just fine with the msys based gcc system, which
> creates native windows binaries.

Not just that, we support building with msys/gcc. We don't really
support cygwin; it's just too strange. (There's code in there to try to
make it work, but cygwin really is a lower priority.)

Donal.

Donal K. Fellows wrote:
> Michael Schlenker wrote:
>> You can build Tcl just fine with the msys based gcc system, which
>> creates native windows binaries.

> Not just that, we support building with msys/gcc. We don't really
> support cygwin; it's just too strange. (There's code in there to try to
> make it work, but cygwin really is a lower priority.)

> Donal.

The reason is because it is the way it is compiled for the network
simulator nsv2 project, which is the most popular
network simulator used by the research community.
http://www.isi.edu/nsnam/ns/

I am not sure what will be the impact to compile tcl/tk using msys
on the compilation of ns (that is compiled with the gcc version of cygwin).
I will try.

Thanks,
Arnaud.

O/H Donal K. Fellows :

> Michael Schlenker wrote:
>> You can build Tcl just fine with the msys based gcc system, which
>> creates native windows binaries.

> Not just that, we support building with msys/gcc. We don't really
> support cygwin; it's just too strange. (There's code in there to try to
> make it work, but cygwin really is a lower priority.)

> Donal.

Just a note: msys/gcc does not work under 64-bit windows (either XP or
Vista). I tried to make msys/mingw work under vista 64, with no success...

George

Donal K. Fellows a crit :

> Michael Schlenker wrote:
>> You can build Tcl just fine with the msys based gcc system, which
>> creates native windows binaries.

> Not just that, we support building with msys/gcc. We don't really
> support cygwin; it's just too strange. (There's code in there to try to
> make it work, but cygwin really is a lower priority.)

> Donal.

So I have downloaded msys from the URL given in the README file of tcl:
http://prdownloads.sourceforge.net/tcl/msys_mingw8.zip

However, I did not succeed compiling.
I have the following configure error:

$ ./configure
loading site script /etc/config.site
loading cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc ) works... no
configure: error: installation or configuration problem: C compiler
cannot create executables.

I found on the web that it might be an issue with CFLAGS, but I have no
clue what to set.

Arnaud.

Donal K. Fellows a crit :

> Michael Schlenker wrote:
>> You can build Tcl just fine with the msys based gcc system, which
>> creates native windows binaries.

> Not just that, we support building with msys/gcc. We don't really
> support cygwin; it's just too strange. (There's code in there to try to
> make it work, but cygwin really is a lower priority.)

> Donal.

So I have downloaded msys from the URL given in the README file of tcl:
http://prdownloads.sourceforge.net/tcl/msys_mingw8.zip

However, I did not succeed compiling.
I have the following configure error:

I found on the web that it might be an issue with CFLAGS, but I have no
clue what to set.

Arnaud.

arnaud.legout wrote:
> The reason is because it is the way it is compiled for the network
> simulator nsv2 project, which is the most popular
> network simulator used by the research community.
> http://www.isi.edu/nsnam/ns/

But that's a Unix project. That's like saying LTSpice (a windows SPICE modeler)
works on Linux too because Linux has WINE. Yeah, I know comparing binaries to
source is silly.

Tcl compiles as a native executable on windows. It doesn't need to be POSIX
translated thru cygwin. If you want that comfy GNU autoconf thing, MingW
(msys/gcc) is the way to go.

--
I like to say "quark"! Quark, quark, quark, quark!
-- Calvin

signature.asc
1K Download

David Gravereaux wrote:
> Tcl compiles as a native executable on windows. It doesn't need to be POSIX
> translated thru cygwin. If you want that comfy GNU autoconf thing, MingW
> (msys/gcc) is the way to go.

It should be noted that the msys/gcc code is only capable of generating
32-bit code. Though that's good enough for most apps... :-)

Donal.

arnaud.legout wrote:
> I have the following configure error:
> $ ./configure
> configure: error: installation or configuration problem: C compiler
> cannot create executables.
> I found on the web that it might be an issue with CFLAGS, but I have no
> clue what to set.

It's probably a spaces-in-directory-names problem. (I assume you can run
32-bit binaries... ;-))

Donal.

O/H Georgios Petasis :

> O/H Donal K. Fellows :
>> Michael Schlenker wrote:
>>> You can build Tcl just fine with the msys based gcc system, which
>>> creates native windows binaries.

>> Not just that, we support building with msys/gcc. We don't really
>> support cygwin; it's just too strange. (There's code in there to try to
>> make it work, but cygwin really is a lower priority.)

>> Donal.

> Just a note: msys/gcc does not work under 64-bit windows (either XP or
> Vista). I tried to make msys/mingw work under vista 64, with no success...

> George

I forgot to mention that I tried to produce 32-bit programs with msys:
msys does not produce 64-bit programs, but in general msys/mingw does
not even run under 64-bit windows...

Just to let you know.

I never succeeded compiling 8.4.14 on vista either with cygwin or
with Minggw.

I installed tcl8.4.15 and it compiled smoothly with cygwin.
Then I installed tk8.4.15 and the compilation failed with an
error saying that tkWinDefault.h could not be found (during the
compilation of tkButtons)
I found tkWinDefault.h in the directory win/ and I copied it to the
directory unix/

That solved the problem and tk8.4.15 finished to compile smoothly.

Arnaud.

arnaud.legout wrote:
> Just to let you know.

> I never succeeded compiling 8.4.14 on vista either with cygwin or
> with Minggw.

> I installed tcl8.4.15 and it compiled smoothly with cygwin.

I recognize the error that you mention below. Because its cause applies
to tcl as well, I am a bit surprised that the tcl build proceeded smoothly.

TCL(Tool Command Language) Scripting

build error for tcl8.4.14 on Windows Vista (using cygwin)