Using system tcl/tk version 8.5

Using system tcl/tk version 8.5

[Gene Smith]

I followed these instructions from Keith on how to build (cvs head) 
insight w/o using the included tcl/tk:

<quoth Keith from 3-18-2010>
To build using the system-supplied tcl/tk, make sure you have the dev 
packages (on linux) installed: tcl-devel, tk-devel, itcl-devel, 
itk-devel. Remove (or rename) tcl, tk, and itcl from your source 
directory, and the build will find the system-installed versions. [I 
don't recall if this is absolutely necessary, but I do it anyway.]

When starting an untested build configuration for the first time, I 
usually do a "make configure-gdb" and check the output of configure that 
it found the tcl/tk/itcl/itk stuff that I expected it to.
<end quote>

I did what he said in the first paragraph but my system (fedora 12) has 
tk/tcl 8.5 and the build process expects 8.4. But if I rename my 
installed libtcl8.5.so and libtcl8.5.so to 8.4 the link works.

But when I run insight it expects 8.5 again so it fails to run. But if I 
rename the system files above back to 8.5 it runs.

Is there a way to specify in configure the version of tcl/tk that you 
have on your system or, even better, to try to work with whatever you have?

Regarding his 2nd paragraph above, where do you run the "make 
configure-gdb" he speaks of? It does not seem to be a supported target.

-gene

Re: Using system tcl/tk version 8.5

[Keith Seitz]

On 03/18/2010 09:32 PM, Gene Smith wrote:
> I did what he said in the first paragraph but my system (fedora 12) has
> tk/tcl 8.5 and the build process expects 8.4. But if I rename my
> installed libtcl8.5.so and libtcl8.5.so to 8.4 the link works.

I use Fedora 11 (soon 13) with Tcl 8.5 (don't forget all the -devel RPMS 
on Red Hat-like systems):

tcl-8.5.6-6.fc11.i586
tcl-devel-8.5.6-6.fc11.i586
tk-8.5.6-4.fc11.i586
tk-devel-8.5.6-4.fc11.i586
itcl-3.4-4.fc11.i586
itcl-devel-3.4-4.fc11.i586
itk-3.4-4.fc11.i586
itk-devel-3.4-4.fc11.i586
iwidgets-4.0.2-2.fc11.noarch

Are you using x86_64? I believe I am sitting on a patch to fix some bad 
assumptions with that... Still need to test them some more, though.

> But when I run insight it expects 8.5 again so it fails to run. But if I
> rename the system files above back to 8.5 it runs.

Yeah, definitely cannot do that...

> Is there a way to specify in configure the version of tcl/tk that you
> have on your system or, even better, to try to work with whatever you have?

You can use:

   --with-tcl              directory containing tcl configuration 
(tclConfig.sh)
   --with-tk               directory containing tk configuration 
(tkConfig.sh)

Normally, you only need to use --with-tcl -- the configury will assume 
that tkConfig.sh is in the same place. I believe I tested all this when 
I did this work a while ago, but I might have missed something. Testing 
three different configury scenarios can get a little confusing.

> Regarding his 2nd paragraph above, where do you run the "make
> configure-gdb" he speaks of? It does not seem to be a supported target.

Do "make configure-gdb" just after you do the configure. This is how I 
normally do it (when I do configure-gdb instead of all-gdb):

$ CFLAGS="-g" ../src/configure --prefix=/home/keiths/insight/HEAD/built
[snip]
$ make configure-gdb
[now you can check the configure log in gdb/]
$ make all-gdb

What version of insight are you trying to build, BTW. It might make a 
difference. [It might not, either. I remember fixing some build bugs a 
while ago...]

I've built Insight this way for almost two-three years now, and I've 
used the resulting executable for my daily work on archer, so it can be 
done.

Keith

Re: Using system tcl/tk version 8.5

[Gene Smith]

Keith Seitz wrote, On 03/19/2010 03:09 AM:
> On 03/18/2010 09:32 PM, Gene Smith wrote:
>> I did what he said in the first paragraph but my system (fedora 12) has
>> tk/tcl 8.5 and the build process expects 8.4. But if I rename my
>> installed libtcl8.5.so and libtcl8.5.so to 8.4 the link works.
>
> I use Fedora 11 (soon 13) with Tcl 8.5 (don't forget all the -devel RPMS
> on Red Hat-like systems):
>
> tcl-8.5.6-6.fc11.i586
> tcl-devel-8.5.6-6.fc11.i586
> tk-8.5.6-4.fc11.i586
> tk-devel-8.5.6-4.fc11.i586
> itcl-3.4-4.fc11.i586
> itcl-devel-3.4-4.fc11.i586
> itk-3.4-4.fc11.i586
> itk-devel-3.4-4.fc11.i586
> iwidgets-4.0.2-2.fc11.noarch
>

tcl-8.5.7-5.fc12.x86_64
tcl-devel-8.5.7-5.fc12.x86_64
tk-devel-8.5.7-3.fc12.x86_64
tk-8.5.7-3.fc12.x86_64
itcl-3.4-6.fc12.x86_64
itcl-devel-3.4-6.fc12.x86_64
itk-devel-3.4-5.fc12.x86_64
itk-3.4-5.fc12.x86_64
iwidgets-4.0.2-4.fc12.noarch


> Are you using x86_64? I believe I am sitting on a patch to fix some bad
> assumptions with that... Still need to test them some more, though.

Yes. Maybe that's some of the weird stuff (see below).

>
>> But when I run insight it expects 8.5 again so it fails to run. But if I
>> rename the system files above back to 8.5 it runs.
>
> Yeah, definitely cannot do that...

Well, it runs and I can almost debug. (I renamed them to 8.4 to get it 
to link then changed the names back to 8.5 to run insight.)

I just tried with the real system and openocd server. It runs but is 
weird. Sometimes won't step. Keyboard doesn't work in dialogs. Radio 
buttons are all highlighted and can't select things. Some strange icons 
buttons (a movie camera?). Fonts don't look good.

>
>> Is there a way to specify in configure the version of tcl/tk that you
>> have on your system or, even better, to try to work with whatever you
>> have?
>
> You can use:
>
> --with-tcl directory containing tcl configuration (tclConfig.sh)
> --with-tk directory containing tk configuration (tkConfig.sh)

I had to specify both. Specifically I had to say:

--with-tcl=/usr/lib64 --with-tk=/usr/lib64

(Without the --with-tk it "couldn't find private tk headers")

After doing this, still no improvement in how it runs. It doesn't crash 
but it is basically unusable. Maybe because of 64 bits?  I assume I 
would need the 32 bit tk/tcl-devel packages to build for 32 bits.

But now it builds with no errors.

At first it kind of worked, but now I can't get it to step through my 
arm cortex-m3 program at all. Been using the old Ins 6.8 (with kluges to 
make it build). Just wanted to try the lastest again. 6.8 works well for 
projects except doubles don't display right (floats OK).

>
> Normally, you only need to use --with-tcl -- the configury will assume
> that tkConfig.sh is in the same place. I believe I tested all this when
> I did this work a while ago, but I might have missed something. Testing
> three different configury scenarios can get a little confusing.
>
>> Regarding his 2nd paragraph above, where do you run the "make
>> configure-gdb" he speaks of? It does not seem to be a supported target.
>
> Do "make configure-gdb" just after you do the configure. This is how I
> normally do it (when I do configure-gdb instead of all-gdb):
>
> $ CFLAGS="-g" ../src/configure --prefix=/home/keiths/insight/HEAD/built
> [snip]
> $ make configure-gdb
> [now you can check the configure log in gdb/]
> $ make all-gdb

Thanks. Will try this. Not sure what I will see...

>
> What version of insight are you trying to build, BTW. It might make a
> difference. [It might not, either. I remember fixing some build bugs a
> while ago...]

It's the cvs head version. I just got it the other day.

>
> I've built Insight this way for almost two-three years now, and I've
> used the resulting executable for my daily work on archer, so it can be
> done.
>
> Keith
>

Re: Using system tcl/tk version 8.5

[Gene Smith]

Keith Seitz wrote, On 03/19/2010 03:09 AM:
>
> Are you using x86_64? I believe I am sitting on a patch to fix some bad
> assumptions with that... Still need to test them some more, though.
>

I rebuilt for i686 on my x86_64 system. Had to install all the 
tcl/itcl/tk/itk and devels etc as i686. But it still runs basically the 
same. The main problem is it can't set breakpoints that do anything. It 
appears to step but it won't visibly show that it ever hit a breakpoint. 
The green line always is at the same place.

Also had to install expat and python-devel as i686 which was not 
expected. There were also a couple other libs for i686 that it needed 
like X11 and freetype. To build for i686 on x86_64 had to export CFLAGS 
and LDFLAGS as "-m32".

Re: Using system tcl/tk version 8.5

[Gene Smith]

Keith,
I will look again at this stuff weekend and get back with you on what I 
find. Thanks for you comments and suggestions. At this point, I don't 
remember the details of what I did.

-gene

Re: Using system tcl/tk version 8.5

[Gene Smith]

Keith Seitz wrote, On 03/31/2010 01:37 AM:
> On 03/19/2010 10:33 PM, Gene Smith wrote:
>> Well, it runs and I can almost debug. (I renamed them to 8.4 to get it
>> to link then changed the names back to 8.5 to run insight.)
>
> This sounds like something very unexpected happened. The build must have
> found the wrong versions of the libraries.
>
>> I just tried with the real system and openocd server. It runs but is
>> weird. Sometimes won't step. Keyboard doesn't work in dialogs. Radio
>> buttons are all highlighted and can't select things. Some strange icons
>> buttons (a movie camera?). Fonts don't look good.
>
> This is *very* odd. I've never seen this. Could you try starting up with
> "-nx" to suppress reading the preferences file. Does that get you any
> further? [I don't think this patch is entirely correct, BTW, but
> probably close.]
>
> Can you tell me the entire build procedure you used?

Didn't get much time but tried it again this weekend with latest CVS 
HEAD. Seems like quite a bit has changed, not sure. Anyhow, when I 
configure like this in my usual way:

../insight_sources/configure -v --quiet --prefix=$PREFIX \
    --target=$TARGET --enable-interwork --enable-multilib \
    --with-gnu-ld --with-gnu-as --with-tcl=/usr/lib64 \
    --with-tk=/usr/lib64 \
    --disable-werror --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu

I get errors when configuring itcl:

mkdir -p -- ./itcl
Configuring in ./itcl
config.status: WARNING:  ../../../insight_sources/itcl/itcl/Makefile.in 
seems to ignore the --datarootdir setting
configure: WARNING: Found Makefile - using build library specs for itcl
config.status: WARNING:  ../../../insight_sources/itcl/itk/Makefile.in 
seems to ignore the --datarootdir setting
configure: error: Can't find Itcl source.  Use --with-itcl to specify 
the the toplevel incr Tcl directory on your system.  (This directory 
should contain itcl/library/itcl.tcl, itk/library/itk.tcl, and 
config/mkinstalldirs.)
configure: error: ../../../insight_sources/itcl/iwidgets/configure 
failed for iwidgets
make[1]: *** [configure-itcl] Error 1
make[1]: Leaving directory `/home/gene/addons/insight-cvs/insight_build'
make: *** [all] Error 2

Tried to add --with-itcl=/usr/lib64 and --with-itk=/usr/lib64 with the 
same result.

Any idea what this could be? Have all the tcl/tk/itcl/itk runtime and 
dev packages installed. Also, everything for iwidgets intalled. This 
step worked with the previous HEAD version that I got a couple weeks 
ago. Do I need source code for itcl?

<snip for now (until configure error resolved)>

-gene

Re: Using system tcl/tk version 8.5

[Gene Smith]

Keith Seitz wrote, On 03/31/2010 01:37 AM:
> On 03/19/2010 10:33 PM, Gene Smith wrote:
>> Well, it runs and I can almost debug. (I renamed them to 8.4 to get it
>> to link then changed the names back to 8.5 to run insight.)
>
> This sounds like something very unexpected happened. The build must have
> found the wrong versions of the libraries.
>
>> I just tried with the real system and openocd server. It runs but is
>> weird. Sometimes won't step. Keyboard doesn't work in dialogs. Radio
>> buttons are all highlighted and can't select things. Some strange icons
>> buttons (a movie camera?). Fonts don't look good.
>
> This is *very* odd. I've never seen this. Could you try starting up with
> "-nx" to suppress reading the preferences file. Does that get you any
> further? [I don't think this patch is entirely correct, BTW, but
> probably close.]
>
> Can you tell me the entire build procedure you used?

With the curent CVS head I can only get a native 64-bit build to work 
using insight's own tcl/tk stuff. I am building on a 64-bit f12 and it 
works OK debugging a 64 bit c++ linux program. Even reg window seems OK.
I build like this from inside an build directory at same level as 
insight_sources:

../insight_sources/configure -v --quiet --prefix=$PREFIX
make
make install

However, this is all I can get to work. If I try to build a 32 bit 
insight on 64 bit f12, with insight's own tcl/tk, configured like this,

../insight_sources/configure -v --quiet --prefix=$PREFIX \
    CFLAGS="-m32" LDFLAGS="-m32"

I get this error:

rm -f libitk3.3.so
gcc -pipe -shared -o libitk3.3.so itk_cmds.o itk_option.o 
itk_archetype.o itk_util.o itkStubInit.o -lX11 
-L/home/gene/addons/insight-cvs/insight_build/tcl/unix -ltclstub8.4 
-L/home/gene/addons/insight-cvs/insight_build/tk/unix -ltkstub8.4 
-L/home/gene/addons/insight-cvs/insight_build/itcl/itcl -litclstub3.3
/usr/bin/ld: skipping incompatible 
/home/gene/addons/insight-cvs/insight_build/tcl/unix/libtclstub8.4.a 
when searching for -ltclstub8.4
/usr/bin/ld: cannot find -ltclstub8.4
collect2: ld returned 1 exit status
make[3]: *** [libitk3.3.so] Error 1
make[3]: Leaving directory 
`/home/gene/addons/insight-cvs/insight_build/itcl/itk'
Making all in iwidgets
make[3]: Entering directory 
`/home/gene/addons/insight-cvs/insight_build/itcl/iwidgets'
Nothing to make for target 'all'.  Run 'make test' to test the distribution

If I try a native 64bit build with system tcl/tk like this,

../insight_sources/configure -v --quiet --prefix=$PREFIX \
    --with-tcl=/usr/lib64 --with-tk=/usr/lib64  --with-itcl=/usr/lib64 \
    --with-itk=/usr/lib64

I see this error:

Configuring in ./itcl
config.status: WARNING:  ../../../insight_sources/itcl/itcl/Makefile.in 
seems to ignore the --datarootdir setting
config.status: WARNING:  ../../../insight_sources/itcl/itk/Makefile.in 
seems to ignore the --datarootdir setting
configure: error: Can't find Itcl source.  Use --with-itcl to specify 
the the toplevel incr Tcl directory on your system.  (This directory 
should contain itcl/library/itcl.tcl, itk/library/itk.tcl, and 
config/mkinstalldirs.)
configure: error: ../../../insight_sources/itcl/iwidgets/configure 
failed for iwidgets
make[1]: *** [configure-itcl] Error 1
make[1]: Leaving directory `/home/gene/addons/insight-cvs/insight_build'
make: *** [all] Error 2

>
> I can build insight for x86_64/64-bit, but the register window will
> crash insight. I will look into that. Otherwise, dialogs all behave
> normally, I can step, browse the stack, inspect variables, and
> everything else. Only problem I found was the register window.

Reg. window looks OK to me on 64-bit f12.

>
> [For the record, I did this with: 'CFLAGS="-m64" ../src/configure
> --enable-64-bit-bfd'. Don't know if that is 100% correct, but it works
> better than what you've got! :-/]
>

I tried the --enable-64-bit-bfd but it didn't help.

>> I had to specify both. Specifically I had to say:
>>
>> --with-tcl=/usr/lib64 --with-tk=/usr/lib64
>>
>> (Without the --with-tk it "couldn't find private tk headers")
>>
>> After doing this, still no improvement in how it runs. It doesn't crash
>> but it is basically unusable. Maybe because of 64 bits? I assume I would
>> need the 32 bit tk/tcl-devel packages to build for 32 bits.
>
> I don't have a lot of experience with 64-bit vs 32-bit, but I would
> guess that mixing 32-bit and 64-bit would be bad. Maybe even very bad.
> What does "ldd" of your insight executable say? Does it mix 32-bit and
> 64-bit?
>
> For the record, mine says:
>
> $ ldd insight
> linux-vdso.so.1 => (0x00007fff64dff000)
> libtk8.5.so => /usr/lib64/libtk8.5.so (0x000000346c400000)
> libtcl8.5.so => /usr/lib64/libtcl8.5.so (0x0000003854e00000)
> libX11.so.6 => /usr/lib64/libX11.so.6 (0x000000346b800000)
> libdl.so.2 => /lib64/libdl.so.2 (0x0000003553000000)
> libm.so.6 => /lib64/libm.so.6 (0x0000003552c00000)
> libncurses.so.5 => /lib64/libncurses.so.5 (0x0000003430600000)
> libz.so.1 => /lib64/libz.so.1 (0x0000003553800000)
> libpython2.5.so.1.0 => /usr/lib64/libpython2.5.so.1.0 (0x0000003569600000)
> libexpat.so.1 => /lib64/libexpat.so.1 (0x000000346c000000)
> libc.so.6 => /lib64/libc.so.6 (0x0000003552800000)
> libtinfo.so.5 => /lib64/libtinfo.so.5 (0x0000003565e00000)
> libXft.so.2 => /usr/lib64/libXft.so.2 (0x0000003473a00000)
> libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x000000346d800000)
> libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x000000346c800000)
> libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00000036bb000000)
> libxcb-xlib.so.0 => /usr/lib64/libxcb-xlib.so.0 (0x000000346b400000)
> libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x000000346bc00000)
> /lib64/ld-linux-x86-64.so.2 (0x0000003552400000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003553400000)
> libutil.so.1 => /lib64/libutil.so.1 (0x000000355e600000)
> libXau.so.6 => /usr/lib64/libXau.so.6 (0x0000003556000000)
> libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x0000003555c00000)
>
>> At first it kind of worked, but now I can't get it to step through my
>> arm cortex-m3 program at all. Been using the old Ins 6.8 (with kluges to
>> make it build). Just wanted to try the lastest again. 6.8 works well for
>> projects except doubles don't display right (floats OK).
>
> Maybe we need to start simple? Can you build the native *only* version?
> Perhaps there is a configury bug w.r.t. cross-toolchains?

At this point can only get a native only build of CVS head with 
insight's own tk/tcl and it works. If I try to build 32-bit (on 64 bit 
system) or try to use system supplied tcl/tk, build fails. This seems 
independent of whether a native or cross build.

>
>> It's the cvs head version. I just got it the other day.
>
> Wow, I am really sorry that you're having so many problems.

Thanks, but at least good old 6.8 still works :).

>
> Keith
>

Re: Using system tcl/tk version 8.5

[Gene Smith]

Gene Smith wrote, On 04/06/2010 11:11 PM:
>
> If I try a native 64bit build with system tcl/tk like this,
>
> ../insight_sources/configure -v --quiet --prefix=$PREFIX \
> --with-tcl=/usr/lib64 --with-tk=/usr/lib64 --with-itcl=/usr/lib64 \
> --with-itk=/usr/lib64
>
> I see this error:
>
> Configuring in ./itcl
> config.status: WARNING: ../../../insight_sources/itcl/itcl/Makefile.in
> seems to ignore the --datarootdir setting
> config.status: WARNING: ../../../insight_sources/itcl/itk/Makefile.in
> seems to ignore the --datarootdir setting
> configure: error: Can't find Itcl source. Use --with-itcl to specify the
> the toplevel incr Tcl directory on your system. (This directory should
> contain itcl/library/itcl.tcl, itk/library/itk.tcl, and
> config/mkinstalldirs.)
> configure: error: ../../../insight_sources/itcl/iwidgets/configure
> failed for iwidgets
> make[1]: *** [configure-itcl] Error 1
> make[1]: Leaving directory `/home/gene/addons/insight-cvs/insight_build'
> make: *** [all] Error 2
>

This error seems to be due to the fact that I left insight's tcl and tk 
dirs in the tree. When I rename or delete them the build works and 
installs. Don't know that it actually debugs correctly but it runs. Was 
able to build for 64 or 32bit host.

The --with-itcl=... is not needed but doesn't hurt.

To build for 32 bit host I do this:
../insight_sources/configure -v --quiet --prefix=$PREFIX \
    --target=$TARGET --enable-interwork --enable-multilib \
    --with-gnu-ld --with-gnu-as --with-tcl=/usr/lib \
    --with-tk=/usr/lib \
    --disable-werror --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu \
    CFLAGS="-m32" LDFLAGS="-m32"

Also, today built CVS head on a 32-bit f8 system w/ insight's own 
tk/tcl. It ran but the source gui window would not debug. I was able to 
see code, load code to flash etc but no stepping or GREEN highlight line 
was ever visible. Was able to step and set BPs using console/gdb window 
however. Gdb does not inform the GUI source window as to what is going 
on, it seems. This is configured as target arm-none-eabi so I guess that 
has something to do with it since a default/native x86_64 or i686 target 
works OK with cvs head.

-gene

Re: Using system tcl/tk version 8.5

[Gene Smith]

Gene Smith wrote:
> Gene Smith wrote, On 04/06/2010 11:11 PM:
>>
>> If I try a native 64bit build with system tcl/tk like this,
>>
>> ../insight_sources/configure -v --quiet --prefix=$PREFIX \
>> --with-tcl=/usr/lib64 --with-tk=/usr/lib64 --with-itcl=/usr/lib64 \
>> --with-itk=/usr/lib64
>>
>> I see this error:
>>
>> Configuring in ./itcl
>> config.status: WARNING: ../../../insight_sources/itcl/itcl/Makefile.in
>> seems to ignore the --datarootdir setting
>> config.status: WARNING: ../../../insight_sources/itcl/itk/Makefile.in
>> seems to ignore the --datarootdir setting
>> configure: error: Can't find Itcl source. Use --with-itcl to specify the
>> the toplevel incr Tcl directory on your system. (This directory should
>> contain itcl/library/itcl.tcl, itk/library/itk.tcl, and
>> config/mkinstalldirs.)
>> configure: error: ../../../insight_sources/itcl/iwidgets/configure
>> failed for iwidgets
>> make[1]: *** [configure-itcl] Error 1
>> make[1]: Leaving directory `/home/gene/addons/insight-cvs/insight_build'
>> make: *** [all] Error 2
>>
> 
> This error seems to be due to the fact that I left insight's tcl and tk 
> dirs in the tree. When I rename or delete them the build works and 
> installs. Don't know that it actually debugs correctly but it runs. Was 
> able to build for 64 or 32bit host.
> 
> The --with-itcl=... is not needed but doesn't hurt.
> 
> To build for 32 bit host I do this:
> ../insight_sources/configure -v --quiet --prefix=$PREFIX \
>    --target=$TARGET --enable-interwork --enable-multilib \
>    --with-gnu-ld --with-gnu-as --with-tcl=/usr/lib \
>    --with-tk=/usr/lib \
>    --disable-werror --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu \
>    CFLAGS="-m32" LDFLAGS="-m32"
> 
> Also, today built CVS head on a 32-bit f8 system w/ insight's own 
> tk/tcl. It ran but the source gui window would not debug. I was able to 
> see code, load code to flash etc but no stepping or GREEN highlight line 
> was ever visible. Was able to step and set BPs using console/gdb window 
> however. Gdb does not inform the GUI source window as to what is going 
> on, it seems. This is configured as target arm-none-eabi so I guess that 
> has something to do with it since a default/native x86_64 or i686 target 
> works OK with cvs head.
> 
>

Tried again on 32-bit f8 using system tcl/tk (had to install tcl, 
tcl-dev, tk, tk-dev, itcl, itcl-dev, itk, itk-dev and iwidgets packages 
from old f8 repo). Even configured with --with-itcl=/usr/lib it 
complained that it needed env vars ITCL_LIBRARY and ITK_LIBRARY pointing 
to the respective libraries. Expected to find itcll3.3/ and itk3.3/ in 
/usr/share/ so made symlink to them rather than define them (yum put 
them in /usr/lib like everything else tcl/tk related).

Once this was resolved still would not step properly in arm code. 
Changed loading my elf file with "symbol-file" to "file" command in 
gdbinit fixed it. So now running "7.1.50.20100407-cvs" OK. This would 
probably also fix case above using insight's own tcl/tk (haven't tried it).

Re: Using system tcl/tk version 8.5

[Gene Smith]

Gene Smith wrote, On 04/09/2010 04:33 PM:
>
> Tried again on 32-bit f8 using system tcl/tk (had to install tcl,
> tcl-dev, tk, tk-dev, itcl, itcl-dev, itk, itk-dev and iwidgets packages
> from old f8 repo). Even configured with --with-itcl=/usr/lib it
> complained that it needed env vars ITCL_LIBRARY and ITK_LIBRARY pointing
> to the respective libraries. Expected to find itcll3.3/ and itk3.3/ in
> /usr/share/ so made symlink to them rather than define them (yum put
> them in /usr/lib like everything else tcl/tk related).
>
> Once this was resolved still would not step properly in arm code.
> Changed loading my elf file with "symbol-file" to "file" command in
> gdbinit fixed it. So now running "7.1.50.20100407-cvs" OK. This would
> probably also fix case above using insight's own tcl/tk (haven't tried it).
>

One other benefit to this cvs HEAD version vs. the official released 
6.8.x is that I can
inspect doubles. Before the values were decoded and displayed wrong. 
(Haven't tried for a while to build a 64-bit, mingw32 or cygwin versions 
however.)