bug-sourceinstall
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-sourceinstall] unknown configure error


From: Claudio Fontana
Subject: Re: [bug-sourceinstall] unknown configure error
Date: Thu, 14 Jul 2005 06:16:16 -0700 (PDT)

Hello,

--- Nagy Gergely <address@hidden> wrote:

> Hi!
> 
> I wanted to give a try to sourceinstall, and i stuck
> on the following
> problem.
> System: Debian Woody/Sarge mixture
> tcl: 8.4
> 
> 
> One thing is i have NO tcl command (maybe i missed
> something in the tcl
> installation in Debian?) only tclsh.

No, it's ok.

> Please be so kind to help me with this problem.

Sure.

> The configure produces the following:
> ----
> ./configure 
> checking for a BSD-compatible install...
> /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for tclsh... /usr/bin/tclsh8.4
> checking tcl version... ./configure: command
> substitution: line 1:
> syntax error near unexpected token `<<<'
> ./configure: command substitution: line 1:
> `$TCLSH_PROG <<< 'puts [info
> tclversion]; exit''
> 
> checking package Expect version... ./configure:
> command substitution:
> line 1: syntax error near unexpected token `<<<'
> ./configure: command substitution: line 1:
> `$TCLSH_PROG <<< $program'
> 
> checking package Tk version... ./configure: command
> substitution: line
> 1: syntax error near unexpected token `<<<'
> ./configure: command substitution: line 1:
> `$TCLSH_PROG <<< $program'

It seems a bash-only construct has leaked in, and you
are probably using another shell as your /bin/sh.

I am fixing this, because this program should NOT
require bash.

Meanwhile you could change the first line of the
configure script (the file called "configure" in the
top source directory) from:

#! /bin/sh

to

#! /bin/bash



> checking whether ln -s works... yes
> checking for cp... /bin/cp
> checking for du... /usr/bin/du
> checking for mv... /bin/mv
> checking for rm... /bin/rm
> checking for sh... /bin/sh
> checking for su... /bin/su
> checking for mkdir... /bin/mkdir
> checking for rmdir... /bin/rmdir
> checking for kill... /bin/kill
> checking for find... /usr/bin/find
> checking for bunzip2... /usr/bin/bunzip2
> checking for bzip2... /usr/bin/bzip2
> checking for compress... no
> configure: WARNING: some functionality will be
> missing
> checking for gunzip... /bin/gunzip
> checking for gzip... /bin/gzip
> checking for tar... /bin/tar
> checking for unzip... /usr/bin/unzip
> checking for zip... /usr/bin/zip
> checking for ps... /bin/ps
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating src/Makefile
> config.status: creating icons/Makefile
> config.status: creating doc/Makefile
> config.status: creating m4/Makefile
> config.status: creating src/sourceinstall.tcl
> ----

Even though ./configure script succeeded in producing
the makefiles, I would suggest using the change above,
since running

$ make
...
$ make install

without the proper package checks could result in
problems at run-time.

Please tell me if you still have troubles.

Bye,

Claudio


> Nagy Gergely
> -----------------------------------
> address@hidden





                
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]