From: Ian Roxborough <irox@redhat.com>
To: Phil Edwards <pedwards@disaster.jaj.com>, gcc@gcc.gnu.org
Cc: insight@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Tcl/Tk update on the upgrade...
Date: Fri, 21 Sep 2001 17:12:00 -0000 [thread overview]
Message-ID: <3BABDA51.8C9B293A@redhat.com> (raw)
In-Reply-To: <20010921165404.A22761@disaster.jaj.com>
Phil Edwards wrote:
> This was a common practice for me, too, until a few days ago. Since then
> the tcl/tk/tix builds have been breaking with either ranlib not recognizing
> the .so file format (???), or more recently,
>
> rm -f libtk8.3.so
> gcc -pipe -shared -o libtk8.3.so tk3d.o [... bunch of object files ...]
> -Wl,-rpath,/home/pme/build/install-2001-09-21/lib:/usr/X11R6/lib
> -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
> libtclstub8.3.a is right over in ../../tcl/unix. Why isn't that being
> searched? Why am I the only one seeing this? :-)
So far I've not seen it or heard of it from anybody else. I'm not sure
why ../../tcl/unix isn't being searched. But I'll try and find out....
What options are you running configure with?
Ian.
next prev parent reply other threads:[~2001-09-21 17: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 [this message]
2001-09-24 10:12 ` Phil Edwards
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=3BABDA51.8C9B293A@redhat.com \
--to=irox@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=pedwards@disaster.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).