From: Phil Edwards <pedwards@disaster.jaj.com>
To: Ian Roxborough <irox@redhat.com>
Cc: gcc@gcc.gnu.org, insight@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Tcl/Tk update on the upgrade...
Date: Mon, 24 Sep 2001 10:12:00 -0000 [thread overview]
Message-ID: <20010924131257.A27810@disaster.jaj.com> (raw)
In-Reply-To: <3BABDA51.8C9B293A@redhat.com>
On Fri, Sep 21, 2001 at 05:24:49PM -0700, Ian Roxborough wrote:
> Phil Edwards wrote:
> > -L/home/pme/build/install-2001-09-21/lib -ltclstub8.3 -L/usr/X11R6/lib
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Hmmmm, looks like this line should point to the build directory. I.E. it should
> probably read -L/home/pme/build/build-2001-09-21/tcl/unix -ltclstub8.3
Yep. I changed it in the generated Makefile, and the build succeeded.
It's coming from the rules in configure.in which set MAKE_LIB,
TCL_LD_SEARCH_FLAGS, and TK_CC_SEARCH_FLAGS. The -L paths are taken
from (around line 205) LIB_RUNTIME_DIR, with colons replaced by ' -L'.
And the library's runtime directory is indeed install-2001-09-21/lib.
But that shouldn't be used for link-time searching, or at least not
by itself.
Hmmmmmm... *looks* Under Red Hat 7.0, libtclstub.8.3.a exists in /usr/lib.
Not under Debian. That would explain it. (Same goes for libitclstub.)
In fact, after I copied libtclstub8.3.a and libitclstub3.1.a into /usr/lib,
changed the RANLIB thing in the Makefile.in like I mentioned in my private
email, and regenerated the Makefile, the build passed.
Thanks very much for helping me with this.
Phil
--
"You have to wonder what kind of life you have when your list of personal
rules begins with, '#3: No drowning in your own mucus,' and '#4: Don't
ask what happened to rules 1 and 2.'"
next prev parent reply other threads:[~2001-09-24 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200109211712.f8LHC7201923@constant.com>
2001-09-21 13:53 ` Phil Edwards
2001-09-21 17:12 ` Ian Roxborough
2001-09-24 10:12 ` Phil Edwards [this message]
2001-09-20 15:55 Ian Roxborough
2001-09-21 3:36 ` Gerald Pfeifer
2001-09-21 10:02 ` Andrew Cagney
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=20010924131257.A27810@disaster.jaj.com \
--to=pedwards@disaster.jaj.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=irox@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).