Bug 25991
Summary: | spawn doesn't work in expect. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Red Hat Bugzilla <bugzilla> |
Component: | tcltk | Assignee: | Jens Petersen <petersen> |
Status: | CLOSED WORKSFORME | QA Contact: | Bill Huang <bhuang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-03-20 16:17:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Red Hat Bugzilla
2001-02-04 22:24:12 UTC
I think I found the problem. tcltk is not 64bit clean. That is why it fails under ia64. There are tens of warnings like ./../generic/tclIndexObj.c:97: warning: passing arg 4 of `Tcl_GetIndexFromObjStruct' with different width due to prototype ./../generic/tclIndexObj.c: In function `Tcl_GetIndexFromObjStruct': ./../generic/tclIndexObj.c:154: warning: cast from pointer to integer of different size ./../generic/tclIndexObj.c: In function `Tcl_WrongNumArgs': ./../generic/tclIndexObj.c:331: warning: cast from pointer to integer of different size I believe if all those warnings are fixed, the ia64 problem will go away. autoconf 64 bit doesn't seem to work. The above bugs are failing because routines are using unions to access the same data different ways. will defer and try to get it for gold. I have a kludge at http://ftp.valinux.com/pub/support/hjl/ia64/ It has both srpms and rpms. It is a kludge, not a real fix, although it works for me and Jakub. Thanks for the patch. Need to test on the other architectures before I go with it. Last version had problems on IA-32 and other architectures (make clean failed on some tests-- some font related, others more serious and pointing to something deeper) I'm taking a look at it. Is this still a problem? Closing this for now, since it is no longer clear what the problem was. |