From: Phil Edwards <phil@jaj.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sources.redhat.com
Subject: Re: Tk lib build doesn't look in the Tcl build directory
Date: Mon, 15 Jul 2002 09:11:00 -0000 [thread overview]
Message-ID: <20020715121104.A1187@disaster.basement.lan> (raw)
In-Reply-To: <Pine.GSO.4.33.0207150840380.15580-100000@makita.cygnus.com>; from keiths@redhat.com on Mon, Jul 15, 2002 at 08:42:32AM -0700
On Mon, Jul 15, 2002 at 08:42:32AM -0700, Keith Seitz wrote:
> On Mon, 15 Jul 2002, Phil Edwards wrote:
>
> > Which config.status? The one in {build}/tcl/unix or the one in
> > {build}/tk/unix? Or a third one? I looked through the first two and
> > nothing jumped out at me.
>
> Any of them will do. It'll just tell me how you configured your toolchain
> (host, target, build).
Oh, that. It's an i686 native build. Here's the toplevel config.status
(the nice tiny one):
#!/bin/sh
# This file was generated automatically by configure. Do not edit.
# This directory was configured as follows:
/home/pme/src/unified/configure
--with-gcc-version-trigger=/home/pme/src/unified/gcc/version.c
--host=i686-pc-linux-gnu --prefix=/home/pme/build/install-2002-07-15
--quiet --enable-shared --enable-languages=c++ --disable-nls --disable-sim
--enable-version-specific-runtime-libs --enable-install-libiberty
--enable-concept-checks --enable-symvers --enable-gdbtk --with-dwarf2
--norecursion
# using "mt-frag"
> > > Is it pulling in the right tclConfig.sh (the one in the build tree).
> >
> > How do I tell?
>
> Take a look at the config.cache in your build directory. Look for a
> variable with "tclconfig" in it. It should be pointing to a file in the
> source tree. If not, it got the wrong one.
It's getting the right one:
11% cd build/build-2002-07-15
12% grep tclconfig config.cache
ac_cv_c_itclconfig=${ac_cv_c_itclconfig=/home/pme/build/build-2002-07-15/itcl/itcl}
ac_cv_c_tclconfig=${ac_cv_c_tclconfig=/home/pme/build/build-2002-07-15/tcl/unix}
13% ls -lF tcl/unix/tclConfig.sh
-rw-r--r-- 1 pme pme 7449 Jul 15 10:40 tcl/unix/tclConfig.sh
14% grep TCL_STUB_LIB_SPEC tcl/unix/tclConfig.sh
TCL_STUB_LIB_SPEC='-L/home/pme/build/install-2002-07-15/lib -ltclstub8.3${TCL_DBGX}'
15%
I opened tclConfig.sh, intending to hack the build path in there just so
I can get the rest of the tree to build, and noticed the other variables
alongside TCL_STUB_LIB_SPEC. So instead of changing that file, I went
back into the source and made this change instead:
26% cvs diff -u3 configure.in
Index: configure.in
===================================================================
RCS file: /home/pme/Repositories/srctree/src/tk/unix/configure.in,v
retrieving revision 1.6
diff -u -3 -r1.6 configure.in
--- configure.in 9 Feb 2002 18:54:17 -0000 1.6
+++ configure.in 15 Jul 2002 16:05:28 -0000
@@ -434,7 +434,7 @@
if test "${SHARED_BUILD}" = "1" -a "${SHLIB_SUFFIX}" != ""; then
TK_SHLIB_CFLAGS="${SHLIB_CFLAGS}"
TCL_TOOL_SHARED_LIB_LONGNAME(TK_LIB_FILE, tk, ${TK_SHARED_LIB_SUFFIX})
- MAKE_LIB="\${SHLIB_LD} -o \${TK_LIB_FILE} \${OBJS} \$(TK_LD_SEARCH_FLAGS) ${TCL_STUB_LIB_SPEC} \${LIBS}"
+ MAKE_LIB="\${SHLIB_LD} -o \${TK_LIB_FILE} \${OBJS} \$(TK_LD_SEARCH_FLAGS) ${TCL_BUILD_STUB_LIB_PATH} \${LIBS}"
RANLIB=":"
# TCL_STUB_FLAGS="-DUSE_TCL_STUBS"
So now instead of MAKE_LIB reading "-L{prefix}/lib -lstubname" it reads
"{build}/stubname.a" explicitly. And this works.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams
next prev parent reply other threads:[~2002-07-15 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 10:06 Phil Edwards
2002-07-14 13:34 ` Keith Seitz
2002-07-15 7:44 ` Phil Edwards
2002-07-15 8:42 ` Keith Seitz
2002-07-15 9:11 ` Phil Edwards [this message]
2002-07-15 9:16 ` Keith Seitz
2002-07-15 9:42 ` Phil Edwards
2002-07-15 9:45 ` Keith Seitz
2002-07-15 9:49 ` Phil Edwards
2002-07-14 23:55 Mo DeJong
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=20020715121104.A1187@disaster.basement.lan \
--to=phil@jaj.com \
--cc=insight@sources.redhat.com \
--cc=keiths@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).