public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Re: Using system tcl/tk version 8.5
Date: Fri, 09 Apr 2010 04:13:00 -0000	[thread overview]
Message-ID: <hpm9gk$ous$1@dough.gmane.org> (raw)
In-Reply-To: <hpgt60$fq4$1@dough.gmane.org>

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



  reply	other threads:[~2010-04-09  4:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  7:10 Gene Smith
2010-03-19  9:02 ` Keith Seitz
2010-03-21  5:49   ` Gene Smith
     [not found]     ` <4BB2DF85.10208@redhat.com>
2010-04-01  3:15       ` Gene Smith
2010-04-05  3:00       ` Gene Smith
2010-04-07  3:12       ` Gene Smith
2010-04-09  4:13         ` Gene Smith [this message]
2010-04-09 20:33           ` Gene Smith
2010-05-20  2:14             ` Gene Smith
2010-03-23  2:47   ` Gene Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='hpm9gk$ous$1@dough.gmane.org' \
    --to=gds@chartertn.net \
    --cc=insight@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).