From: Grant Edwards <grante@visi.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: insight@sources.redhat.com
Subject: Re: tcl/tk extension problems
Date: Mon, 13 Aug 2001 15:23:00 -0000 [thread overview]
Message-ID: <20010813172437.A21110@visi.com> (raw)
In-Reply-To: <20010813165042.A8857@visi.com>
On Mon, Aug 13, 2001 at 04:50:43PM -0500, Grant Edwards wrote:
> > > I'm trying to build and install insight-5.0, and it's failing
> > > because the directory where I built and installed it 8 months
> > > ago isn't there.
> >
> > I don't quite understand. You're doing a clean build and install and it's
> > complaining about something you did months ago???
[...]
> It's the itcl/itk config file that found the previous
> installation:
>
> /home/grante/mybuild/BUILD/insight-5.0/itcl/iwidgets3.0.0/unix:
>
> Makefile:ITCL_SRC_DIR = /home/grante/insight-5.0-mod/itcl/itcl
> Makefile:ITK_SRC_DIR = /home/grante/insight-5.0-mod/itcl/itk
> config.status:s%@ITCL_SRC_DIR@%/home/grante/insight-5.0-mod/itcl/itcl%g
> config.status:s%@ITK_SRC_DIR@%/home/grante/insight-5.0-mod/itcl/itk%g
>
> It looks like the configure.in files searches default locations
> if it isn't passed the --with-tcl option.
I renamed /usr/local/lib/itkConfig.sh and
/usr/local/lib/itclConfig.sh, and everything installed fine.
When the itk/itcl configure scripts are run, they aren't being
passed the --with-tcl flag to tell them where to look for
configuration info, so they look for *Config.sh in standard
places -- including /usr/local/lib. They find those files from
a previous install and use them.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-08-13 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 13:40 Grant Edwards
2001-08-13 14:01 ` Grant Edwards
2001-08-13 14:07 ` Keith Seitz
2001-08-13 14:49 ` Grant Edwards
2001-08-13 15:23 ` Grant Edwards [this message]
2001-08-13 14:19 ` Kaoru Fukui
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=20010813172437.A21110@visi.com \
--to=grante@visi.com \
--cc=insight@sources.redhat.com \
--cc=keiths@cygnus.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).