From: Mo DeJong <supermo@bayarea.net>
To: Insight <insight@sources.redhat.com>
Subject: Re: Tk lib build doesn't look in the Tcl build directory
Date: Sun, 14 Jul 2002 23:55:00 -0000 [thread overview]
Message-ID: <20020714235520.74ec887b.supermo@bayarea.net> (raw)
>> Am I the only one seeing this? It would seem that the Tk build requires
>> all the Tcl stuff to have been /installed/, not just built, before it itself
>> can build. Perhaps the majority (totality?) of the developers already have
>> a Tcl installation somewhere in the default paths searched by the linker?
>What does "cat config.status" give? I just built for linux with and
>without --enable-shared, and it worked just fine.
>Is it pulling in the right tclConfig.sh (the one in the build tree). Tcl
>should definately not need to be installed to build tk in our tree.
The problem here only shows up when --enable-shared is passed
and that was never tested as part of the 8.3 upgrade because we
always build static under Unix. At any rate, here is the most
simple little fix for the problem.
2002-07-14 Mo DeJong <supermo@bayarea.net>
* unix/configure: Regen.
* unix/configure.in: Use TCL_BUILD_STUB_LIB_SPEC instead of
TCL_STUB_LIB_SPEC when defining MAKE_LIB since we want to
link to the libtclstub in the build directory.
Index: unix/configure.in
===================================================================
RCS file: /cvs/src/src/tk/unix/configure.in,v
retrieving revision 1.6
diff -u -r1.6 configure.in
--- unix/configure.in 9 Feb 2002 18:54:17 -0000 1.6
+++ unix/configure.in 15 Jul 2002 06:44:58 -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_SPEC} \${LIBS}"
RANLIB=":"
# TCL_STUB_FLAGS="-DUSE_TCL_STUBS"
next reply other threads:[~2002-07-15 6:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 23:55 Mo DeJong [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=20020714235520.74ec887b.supermo@bayarea.net \
--to=supermo@bayarea.net \
--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).