Has anyone successfully compiled tcl and/or tk and/or expect on tru64 5.1A.
I know these are on the OSSC, but I would like to compile my own so I have
more control over installation choices.
When I try tcl, several of the tests fail:
clock.test
==== clock-3.2 clock format tests FAILED
==== Contents of test case:
# TCL_USE_TIMEZONE_VAR
catch {set oldtz $env(TZ)}
set env(TZ) PST
set x {}
append x [clock format 863800000 -format %Z -gmt 1]
append x [set env(TZ)]
catch {unset env(TZ); set env(TZ) $oldtz}
set x
---- Result was:
ESTPST
---- Result should have been:
GMTPST
==== clock-3.2 FAILED
==== clock-3.4 clock format tests FAILED
==== Contents of test case:
# tzset() under Borland doesn't seem to set up tzname[] for gmt
timezone.
# tzset() under MSVC has the following weird observed behavior:
# First time we call "clock format [clock seconds] -format %Z -gmt 1"
# we get "GMT", but on all subsequent calls we get the current time
# zone string, even though env(TZ) is GMT and the variable _timezone
# is 0.
set x {}
append x [clock format 863800000 -format %Z -gmt 1]
append x [clock format 863800000 -format %Z -gmt 1]
---- Result was:
ESTEST
---- Result should have been:
GMTGMT
==== clock-3.4 FAILED
parseExpr.test
==== parseExpr-14.11 GetLexeme procedure, bad double lexeme too big FAILED
==== Contents of test case:
list [catch {testexprparser {123.e+99999999999999} -1} msg] $msg
---- Result was:
1 {syntax error in expression "123.e+99999999999999"}
---- Result should have been:
1 {floating-point value too large to represent}
==== parseExpr-14.11 FAILED
parseExpr.test
==== parseExpr-14.11 GetLexeme procedure, bad double lexeme too big FAILED
==== Contents of test case:
list [catch {testexprparser {123.e+99999999999999} -1} msg] $msg
---- Result was:
1 {syntax error in expression "123.e+99999999999999"}
---- Result should have been:
1 {floating-point value too large to represent}
==== parseExpr-14.11 FAILED
tcltest.test
==== tcltest-8.3 tcltest a.tcl -tmpdir notReadableDir FAILED
==== Contents of test case:
catch {exec $::tcltest::tcltest a.tcl -tmpdir $notReadableDir} msg
# The join is necessary because the message can be split on multiple
lines
list [regexp {not readable} [join $msg]]
---- Result was:
0
---- Result should have been:
1
==== tcltest-8.3 FAILED
==== tcltest-8.4 tcltest a.tcl -tmpdir notWriteableDir FAILED
==== Contents of test case:
catch {exec $::tcltest::tcltest a.tcl -tmpdir $notWriteableDir} msg
# The join is necessary because the message can be split on multiple
lines
list [regexp {not writeable} [join $msg]]
---- Result was:
0
---- Result should have been:
1
==== tcltest-8.4 FAILED
==== tcltest-8.7 tcltest a.tcl -testdir notReadableDir FAILED
==== Contents of test case:
catch {exec $::tcltest::tcltest a.tcl -testdir $notReadableDir} msg
# The join is necessary because the message can be split on multiple
lines
list [regexp {not readable} [join $msg]]
---- Result was:
0
---- Result should have been:
1
==== tcltest-8.7 FAILED
I will summarize to the list.
thanks,
James Richardson
Unix Systems Administrator
Horry Telephone
(843) 369-8549
Received on Tue Jan 29 2002 - 21:50:47 NZDT