From: Keith Seitz <keiths@redhat.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: insight@sources.redhat.com
Subject: Re: libgui build machinery issues
Date: Tue, 18 Aug 2009 19:29:00 -0000 [thread overview]
Message-ID: <4A8B010F.4050807@redhat.com> (raw)
In-Reply-To: <20090818054302.GE28254@gmx.de>
On 08/17/2009 10:43 PM, Ralf Wildenhues wrote:
> | config/ChangeLog:
> | 2009-02-02 Doug Evans<dje@google.com>
> |
> | * tcl.m4 (SC_PATH_TCLCONFIG): Don't exit 0 if tclconfig fails.
> | (SC_PATH_TKCONFIG): Don't exit 0 if tkconfig fails.
> | (SC_LOAD_TCLCONFIG): Quote all uses of TCL_BIN_DIR, it may contain
> | "# no Tcl configs found".
> | (SC_LOAD_TKCONFIG): Similarily for TK_BIN_DIR.
>
> and I assume they ought to help also for libgui
> (I can apply a patch to regenerate configure unless you disagree).
Yes, please. It was probably just on oversight on my part.
> @TCLSH@ is not substituted by configure. Maybe it was at some point
> back? Looking at the tree, I cannot tell what would be the right thing
> here, or how this broke. Maybe you need SC_PROG_TCLSH from
> config/tcl.m4 and then use TCLSH_PROG, or BUILD_TCLSH?
>
> To reproduce: I have configured my tree with
> '--enable-shared' '--disable-rda' '--enable-libgloss' '--enable-sim' \
> '--enable-maintainer-mode'
Yes, I think that the old configure was substituting TCLSH, but that got
borked at some time or another. Using SC_PROG_TCLSH should be good
enough. I'm the only one that ever really tweaks it, and that is as
little as I possibly can manage. ;-)
If there is anything you would like me to do, don't hesitate to ask.
Keith
prev parent reply other threads:[~2009-08-18 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 5:43 Ralf Wildenhues
2009-08-18 19:29 ` Keith Seitz [this message]
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=4A8B010F.4050807@redhat.com \
--to=keiths@redhat.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=insight@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).