Latest build of Insight 24/1/00

["Andy Hare" <andy at hare dot u-net dot com>]

I have been compiling the Insight debugger for some time now and the latest
build gives me a problem. Below is the output from the make process.

>make[3]: Entering directory `/c/cygnus/build/insight/libgui/library'
>TCL_LIBRARY=/c/cygnus/GNU-Source-Code/insight/libgui/library/../../tcl/libr
ary;
>export TCL_LIBRARY; \
>here=`pwd`; \
> \
>cd /c/cygnus/GNU-Source-Code/insight/libgui/library && \
>  echo " auto_mkindex `pwd` advice.tcl balloon.tcl bbox.tcl bgerror.tcl
bindings
>.tcl canvas.tcl cframe.tcl center.tcl debug.tcl def.tcl internet.tcl
font.tcl ge
>nsym.tcl gettext.tcl hooks.tcl lframe.tcl list.tcl looknfeel.tcl menu.tcl
mono.t
>cl multibox.tcl parse_args.tcl path.tcl postghost.tcl prefs.tcl print.tcl
sendpr
>.tcl topbind.tcl toolbar.tcl treetable.tcl ulset.tcl wframe.tcl wingrab.tcl
vent
>ry.tcl combobox.tcl pane.tcl panedwindow.tcl tree.tcl" |
$here/../../itcl/itcl/u
>nix/itclsh.exe
>/c/cygnus/build/insight/libgui/library/../../itcl/itcl/unix/itclsh.exe: not
foun
>d
>make[3]: *** [tclIndex] Error 127
>make[3]: Leaving directory `/c/cygnus/build/insight/libgui/library'
>make[2]: *** [all-recursive] Error 1
>make[2]: Leaving directory `/c/cygnus/build/insight/libgui'
>make[1]: *** [all-recursive-am] Error 2
>make[1]: Leaving directory `/c/cygnus/build/insight/libgui'
>make: *** [all-libgui] Error 2

I am building under b20.1 and NT to build a cross version of the tools for
the ARM processor. The command line I use is as below.

/c/cygnus/GNU-Source-Code/insight/configure -v \
 --prefix=/c/cygnus/xgcc-arm/insight \
 --exec-prefix=/c/cygnus/xgcc-arm/insight \
 --host=i586-cygwin32 --target=arm-elf >configure.out

make -w all install LIBGCC2_DEBUG_CFLAGS="-g1 -O1" \
 LANGUAGES="c c++" > make.out

It appears to be looking for a file "itclsh.exe" in the wrong build
directory, it looks in Unix but the build is for win. The object files exist
in the win directory but they have not been linked to form the file. I am
assuming this is a problem with a config script somewhere, unfortunately I
cannot understand these config scripts and so cannot help to find the
problem.


Andy Hare

Andy Hare