Red Hat Bugzilla – Bug 22187
Tcl/Tk build env doesn't work well with auto build environment
Last modified: 2007-04-18 12:30:11 EDT
Tcl/Tk supplied with RH7, does not support the -mode option with
fconfigure. Neither do the supplied libraries. Libraries (exactly which
one) supplied with RH6.1 are O.K. for compile.
Are you referring to the
fconfigure -translation mode
where mode is for setting the lf/cr raw/cooked aspects?
Created attachment 10460 [details]
example of problem
Created attachment 12083 [details]
detailed explanation and a way to solve it...
Thanks for the fix. It will save much tim on next system build.
The reason is that Tcl's configure script doesn't detect the systems I/O API
(termios, termio or sgtty)
if configure's stdin isn't a tty. I guess that Red Hat build the distributions
packages for their distributions in an automated environment where stdin is a
pipe or /dev/null. Therefore the correct API can't be detected and the option
-mode isn't compiled in. When someone rebuilds the package by hand, stdin is a
tty and everything works.
The solution is a patch against unix/tcl.m4 I submitted to the Tcl patch manager
at SourceForge. It makes configure detect the API even when stdin is no tty.
The patch has not yet been accepted by the Tcl maintainers.
*** Bug 28224 has been marked as a duplicate of this bug. ***
build scripts need to be patched so /var/tmp doesn't get pulled into the paths
and stdin is recognized to be a tty
Created attachment 13665 [details]
Why we need a fix: additional privs exploit for mkpasswd / /var/tmp - trivial...
Why have these bugs been marked as duplicates?
Though both are related to Tcl/Tk and the buildsystem, they cover totally
There is already a patch that fixes this one and I am working on a fix for
#28224 that doesn not depend on changes in the build system.
Created attachment 14424 [details]
Quick fix bug #28224
*** Bug 42630 has been marked as a duplicate of this bug. ***
fixed in release 60.
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.