From: Keith Seitz <keiths@redhat.com>
To: Phil Edwards <phil@jaj.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:16:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0207150912280.15580-100000@makita.cygnus.com> (raw)
In-Reply-To: <20020715121104.A1187@disaster.basement.lan>
On Mon, 15 Jul 2002, Phil Edwards wrote:
> So now instead of MAKE_LIB reading "-L{prefix}/lib -lstubname" it reads
> "{build}/stubname.a" explicitly. And this works.
Hmmm. Odd. Mine builds just fine without any of this. Alas, as Mo and you
indicate, it seems that this is necessary. At the very least, it seems
that it is correct to use the build spec in our tree.
I'll check it in.
Keith
next prev parent reply other threads:[~2002-07-15 16:16 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
2002-07-15 9:16 ` Keith Seitz [this message]
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=Pine.GSO.4.33.0207150912280.15580-100000@makita.cygnus.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=phil@jaj.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).