public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: tlow@low-shang.homelinux.com (Tom Low-Shang)
To: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Cannot build Xconq on Debian Linux
Date: Sun, 07 Dec 2003 01:07:00 -0000	[thread overview]
Message-ID: <20031206200130.GA10371@low-shang.homelinux.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312061228290.28834-100000@leon.phy.cmich.edu>

On Sat, Dec 06, 2003 at 12:39:21PM -0500, Eric McDonald wrote:
> Hi Tom, Lincoln,
> 
> I just checked in some changes which might address your Tcl/Tk 
> configuration hassles. Please let me know how they work.

I tried your change with tcl/tk 8.4 and eveything still works
for me. I got curious about how you do this magic and noticed a
small error:

--- configure   6 Dec 2003 17:28:08 -0000       1.33
+++ configure   6 Dec 2003 19:23:45 -0000
@@ -1337,7 +1337,7 @@
         TCL_INCLUDE_SPEC="-I${TCL_PREFIX}/include/tcl${TCL_VERSION}"
       fi
     fi
-    TCL_INLCUDE_SPEC=`echo ${TCL_INCLUDE_SPEC} | grep -v '/usr/include$'`
+    TCL_INCLUDE_SPEC=`echo ${TCL_INCLUDE_SPEC} | grep -v '/usr/include$'`
     
 
     if test "x${TCL_LDFLAGS}" = "x" ; then

> 
> Do you mean "-I/usr/include/tcl8.2"?
> I hope so. Otherwise things just got even more convoluted.

Oops, sorry, yes that is what I meant.

> 
> Well if your 8.4 tclConfig.sh/tkConfig.sh files contain
> 'TCL_INC_DIR' and 'TK_INC_DIR', repsectively, then this was
> handled by an enhancement to the configure system. If
> tclConfig.sh contains a 'TCL_INCLUDE_SPEC' var, then Debian
> finally do something more mainstream....

$ grep TCL_INCLUDE_SPEC /usr/lib/tcl8.4/tclConfig.sh 
TCL_INCLUDE_SPEC='-I/usr/include/tcl8.4'
$ grep TCL_INC_DIR /usr/lib/tcl8.4/tclConfig.sh 
TCL_INC_DIR='/usr/include/tcl8.4/tcl-private/generic'
$ grep TK_INC_DIR /usr/lib/tk8.4/tkConfig.sh 
TK_INC_DIR='/usr/include/tcl8.4/tk-private/generic'

I believe Debian is the only distribution that allows multiple
versions of tcl/tk development packages to be installed, which
possibly broke tcl/tk in a subtle way.  Keeps things interesting
for configure script writers...

Tom

  reply	other threads:[~2003-12-07  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06  0:04 Lincoln Peters
2003-12-06  4:01 ` Eric McDonald
2003-12-06  4:55   ` Lincoln Peters
2003-12-06  5:34     ` Eric McDonald
2003-12-06 16:24       ` Lincoln Peters
2003-12-06 22:34         ` Tom Low-Shang
2003-12-07  0:16           ` Eric McDonald
2003-12-07  1:07             ` Tom Low-Shang [this message]
2003-12-07  6:47               ` Eric McDonald

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=20031206200130.GA10371@low-shang.homelinux.com \
    --to=tlow@low-shang.homelinux.com \
    --cc=xconq7@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).