This is the mail archive of the
insight@sourceware.org
mailing list for the Insight project.
RE: How to build Insight for 64-bit linux with system Tcl et al
- From: Pavel Fedin <p dot fedin at samsung dot com>
- To: 'Keith Seitz' <keiths at redhat dot com>
- Cc: insight at sourceware dot org
- Date: Tue, 30 Jul 2013 10:09:27 +0400
- Subject: RE: How to build Insight for 64-bit linux with system Tcl et al
- References: <D7E38FC3AB80A048A6312823FFB1753F7C23EE64 at TWS-MBX02> <51543F89 dot 4070503 at redhat dot com> <D7E38FC3AB80A048A6312823FFB1753F7C23FE7D at TWS-MBX02> <51544488 dot 3050501 at redhat dot com> <D7E38FC3AB80A048A6312823FFB1753F7C23FE8E at TWS-MBX02> <D7E38FC3AB80A048A6312823FFB1753F7C242250 at TWS-MBX02> <51F2FAD3 dot 3080302 at redhat dot com>
Hello!
> 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