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 05:34:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312052342430.28834-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <1070683370.14589.123.camel@odysseus>
On Fri, 5 Dec 2003, Lincoln Peters wrote:
> > TCL_CFLAGS = -I/usr/include/tcl8.2
> > TK_CFLAGS = -I/usr/include/tk8.2
Sure. But these should have been picked up from your tclConfig.sh
and tkConfig.sh files. Since they weren't, I would be quite
interested to see where your particular Debian version hides them
in these files.
> 50c50,51
> < XAW_LIB = -lXaw -lXt $(X11_LIB) -lXext -lm
> ---
> > # XAW_LIB = -lXaw -lXt $(X11_LIB) -lXext -lm
> > XAW_LIB = -lXt $(X11_LIB) -lXext -lm
Hmm... Probably this would break the xtconq build. But for the
purposes of building x2imf and imf2x this is fine, since they
don't rely on MIT's Athena widgets, AFAIK.
> This, of course, may not work on non-Debian systems.
Yeah, and hacking an autogenerated makefile by hand is not really
a fix, _in the configury sense of the word. I would like to get my
hands on your tclConfig.sh and tkConfig.sh files, so that we can
autogenerate the correct thing.
> accessible without a laptop. You could try the Zephyr Cafe (at 3643
> Balboa Street, near 38th Avenue); I seem to remember that they offer
Thanks. I'll keep it in mind. I'll have to look at my maps to
see if it is within walking distance of either the Moscone Center
or the hotel where I am staying....
Eric
next prev parent reply other threads:[~2003-12-06 4:54 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 [this message]
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.0312052342430.28834-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).