From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Tom Low-Shang <tlow@low-shang.homelinux.com>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Cannot build Xconq on Debian Linux
Date: Sun, 07 Dec 2003 00:16:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312061228290.28834-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <20031206162443.GA25918@low-shang.homelinux.com>
Hi Tom, Lincoln,
I just checked in some changes which might address your Tcl/Tk
configuration hassles. Please let me know how they work.
On Sat, 6 Dec 2003, Tom Low-Shang wrote:
> On Fri, Dec 05, 2003 at 09:35:58PM -0800, Lincoln Peters wrote:
> >
> > On Debian unstable, the files tclConfig.sh and tkConfig.sh in
> > /usr/lib/tcl8.2 and /usr/lib/tk8.2 respectively.
Right. And the configuration logic correctly finds those. What it
does (or doesn't do, to put it more accurately) with the contents
of these is/was the problem.
> Since I have used tcl/tk 8.2, 8.3 and 8.4 on debian unstable,
> here is what worked for me. With 8.2 I always used:
>
> make CFLAGS=-I/usr/include/8.2
Do you mean "-I/usr/include/tcl8.2"?
I hope so. Otherwise things just got even more convoluted.
> 8.3 had similar requirements. Since 8.4, the arguments are no
> longer needed. Whether this is due to changes in
> tclConfig.sh/tkConfig.sh or the configure script, I cannot say.
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 decided to
do something more mainstream....
Thanks,
Eric
next prev parent reply other threads:[~2003-12-06 17:39 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 [this message]
2003-12-07 1:07 ` Tom Low-Shang
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=Pine.LNX.4.44.0312061228290.28834-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=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).