From: Phil Edwards <pedwards@disaster.jaj.com>
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: gcc@gcc.gnu.org, pfeifer@dbai.tuwien.ac.at, irox@redhat.com,
insight@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Tcl/Tk update on the upgrade...
Date: Fri, 21 Sep 2001 13:53:00 -0000 [thread overview]
Message-ID: <20010921165404.A22761@disaster.jaj.com> (raw)
In-Reply-To: <200109211712.f8LHC7201923@constant.com>
On Fri, Sep 21, 2001 at 10:12:07AM -0700, Benjamin Kosnik wrote:
> > GDB's and BINUTILS' combined CVS repository also contains a copy of
> > dejagnu, expect and tcl. Creating a source tree containing that and
> > GCC and then testing it is a very common pratice (well I thought it
> > was until now). Any changes Ian makes to tcl are going to directly
> > affect anyone using the src dejagnu to test GCC.
>
> I think you're correct about it being a common practice, Andrew. Since
> a lot of the 'make check' routines rely on current versions of
> dejagnu, this is an issue for gcc developers as well.
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
-lX11 -ldl -lieee -lm -lc
/usr/local/gcc-3.0/lib/gcc-lib/i686-pc-linux-gnu/3.0/../../../../i686-pc-linux-gnu/bin/ld: cannot find -ltclstub8.3
collect2: ld returned 1 exit status
gmake[2]: *** [libtk8.3.so] Error 1
gmake[2]: Leaving directory `/home/pme/build/build-2001-09-21/tk/unix'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/home/pme/build/build-2001-09-21/tk'
gmake: *** [all-tk] Error 2
libtclstub8.3.a is right over in ../../tcl/unix. Why isn't that being
searched? Why am I the only one seeing 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 parent reply other threads:[~2001-09-21 13:53 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 [this message]
2001-09-21 17:12 ` Ian Roxborough
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=20010921165404.A22761@disaster.jaj.com \
--to=pedwards@disaster.jaj.com \
--cc=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=irox@redhat.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).