public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
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:42:00 -0000	[thread overview]
Message-ID: <20020715124249.A1539@disaster.basement.lan> (raw)
In-Reply-To: <Pine.GSO.4.33.0207150912280.15580-100000@makita.cygnus.com>; from keiths@redhat.com on Mon, Jul 15, 2002 at 09:16:49AM -0700

On Mon, Jul 15, 2002 at 09:16:49AM -0700, Keith Seitz wrote:
> 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.

Ah, cool.  I just now went to the archives and read Mo's message.

(I didn't know that the shared library is a relatively recent thing.
It explains some of the other hacks I have in my local tree, e.g., don't
run ranlib on a .so.)

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

  reply	other threads:[~2002-07-15 16:42 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
2002-07-15  9:42           ` Phil Edwards [this message]
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=20020715124249.A1539@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).