From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Cannot build Xconq on Debian Linux
Date: Sat, 06 Dec 2003 04:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312052003590.28451-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <1070655931.14589.6.camel@odysseus>
Hi Lincoln,
Sorry for the late response. I have been busting tail at work
all week, since I have to present at a conference next week.
Can you send me your tclConfig.sh and tkConfig.sh files? I had
to add some tests to aclocal.m4 to handle Peter's Debian, but it
sounds like yours may have even another interesting twist. These
two files are the most important debugging tools I have wrt to
tkconq build problems....
Or if you want to investigate the problem yourself, you could
look for the presence of the TCL_INCLUDE_SPEC or TCL_INC_DIR
variables. And if neither exists or both are blank, then try to
locate which variables provide some "-I" include flags or which
provide paths to the includes directories from which the "-I"
flags can be synthesized.
Thanks,
Eric
P.S. My turnaround time may be even poorer next week. I don't know
whether there are any good Internet cafes in San Francisco, and I
won't have a laptop with me....
next prev parent reply other threads:[~2003-12-06 1:17 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 [this message]
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
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.0312052003590.28451-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=sampln@sbcglobal.net \
--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).