Some issues

[Paul Smith <psmith at netezza dot com>]

Hi all;  I have some problems, at least some of which probably aren't
Insight problems per se.

The first major problem is things don't work if "insight" is a relative
symlink.  The code tries to compute a pathname based on this, but it
doesn't find the right path.  For example, I have this setup:

	/tools/bin/insight -> ../i686-pc-linux-gnu/bin/insight

My working directory is /home/psmith, and /tools/bin is on my PATH.
When I run "insight", I get this error:

	ide_initialize_paths failed: couldn't change working directory to "/home/psmith/../x86_64-pc-linux-gnu/bin": no such file or directory

I think whatever is constructing this pathname needs to do a search
through PATH to find argv[0], if it's not fully qualified.

There are a number of issues with standard configure options not
working, because they're not being passed to the tcl areas correctly.

      * DESTDIR is not working, because it's not being handled by the
        tcl subdirectories.  The tcl directory can be handled by passing
        INSTALL_ROOT=$(DESTDIR) to the tcl make.  Unfortunately, this
        doesn't work with itcl; maybe that could be fixed.

      * There are other path problems.  I wanted to change --prefix to
        something like /tools/share/insight-6.6 so that the tcl stuff
        provided by insight wouldn't conflict with other versions of
        TCL, and I wanted to set --exec-prefix as above; this doesn't
        work because:

	Tcl_Init failed: Can't find a usable init.tcl in the following directories: 
    {} /tools/share/tcl8.4 /share/tcl8.4 /tools/library /library /tcl8.4.1/library

        Probably the correct values for --sharedir, --prefix, or
        whatever are not being sent to the tcl builds.

-- 
-----------------------------------------------------------------------------
 Paul D. Smith <psmith@netezza.com>                       http://netezza.com
 "Please remain calm--I may be mad, but I am a professional."--Mad Scientist
-----------------------------------------------------------------------------
      These are my opinions--Netezza takes no responsibility for them.