Re: Oops (was Re: [Xotcl] Bug: make install step tries to perform chmod on xowish even if not configured to build [PATCH])

From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Sat, 10 Apr 2004 21:48:09 +0200

On Friday 09 April 2004 02:20, Jim Lynch wrote:
> > Hi,
> >
> > I got an error when building xotcl without tk and wish support where it
> > tries to do a chmod on xowish (which of course doesn't exist at that
> > point.)
> >
> > This patch will fix the problem
>
> Actually no it won't, it's broke... needs " ; \ " at the line ends of the
> new chmod lines. Here's a better patch (attached).

 Hi Jim,

 i get the impression you are fixing things that are not broken
 in the general distribution. The configure stuff is
 defined to produces always a file xotclsh or xowish, no
 matter whether you compile with or without --with-xotclsh.
 Sounds wierd, isn't it? If you compile with the default
 values (without xotclsh), the generated file
 unix/xotclsh is a small tcl script with e.g. the following content:

#!/usr/bin/tclsh8.4
if {$argc == 0} {
  puts "Don't use [info script] as interactive shell! Use instead:"
  puts " /usr/bin/tclsh8.4"
  puts " package require XOTcl; namespace import ::xotcl::*"
} else {
  package require XOTcl
  namespace import ::xotcl::*
  set argv0 [lindex $argv 0]
  set argv [lreplace $argv 0 0]
  incr argc -1
  source $argv0
}
 This scriped is generated from xotclsh.in and requires a "chmod +x".

 If you configure ... --with-xotclsh, the file unix/xotclsh is a true
 binary (a statically linked shell, also useful for these few platforms
 that have still problems with dynamic loading).

 Producing a shell in form of a tcl script is useful for
 legacy applications, that still use xotclsh to call the xotcl scripts.

-gustaf

-- 
Univ.Prof. Dr.Gustaf Neumann
Abteilung für Wirtschaftsinformatik
WU-Wien, Augasse 2-6, 1090 Wien