public inbox for
 help / color / mirror / Atom feed
From: Pavel Fedin <>
To: 'Keith Seitz' <>
Subject: RE: How to build Insight for 64-bit linux with system Tcl et al
Date: Tue, 30 Jul 2013 06:09:00 -0000	[thread overview]
Message-ID: <003601ce8ceb$5976bc80$0c643580$> (raw)
In-Reply-To: <>


> I sent a user these instructions some time ago. Someone was recently
> asking on #gdb, so I thought I would publish this to the mailing list.
> I am attempting to switch insight to GIT, but no ETA yet.

 By the way, why doesn't anybody update TCL and TK in Insight's repository ?
 It would be just convenient. Windows users would benefit because under
Windows every piece of software is expected to be self-contained, and
built-in TCL and TK are nice to have.
 Current TCL works even for 64 bits, but has to be patched. All of the
patching is already done in upstream version.

 And one more little thing. Even if i supply --with-tcl=/usr/lib to main
configure script it will still attempt to configure bundled TCL. Shouldn't
it be omitted in this case ? Currently i worked around just by erasing the
directory, but again, it's inconvenient. Usually i just checkout 'insight'
module and expect that everything will work.

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia

      reply	other threads:[~2013-07-30  6:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D7E38FC3AB80A048A6312823FFB1753F7C23EE64@TWS-MBX02>
     [not found] ` <>
     [not found]   ` <D7E38FC3AB80A048A6312823FFB1753F7C23FE7D@TWS-MBX02>
     [not found]     ` <>
     [not found]       ` <D7E38FC3AB80A048A6312823FFB1753F7C23FE8E@TWS-MBX02>
     [not found]         ` <D7E38FC3AB80A048A6312823FFB1753F7C242250@TWS-MBX02>
2013-07-26 22:40           ` FYI: " Keith Seitz
2013-07-30  6:09             ` Pavel Fedin [this message]

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:

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

  git send-email \
    --in-reply-to='003601ce8ceb$5976bc80$0c643580$' \ \ \ \

* 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).