From: suleman <sulemankm@gmail.com>
To: sid@sourceware.org
Subject: Re: could not build tksm in sid snapshot 20070801
Date: Thu, 16 Aug 2007 13:47:00 -0000 [thread overview]
Message-ID: <1187272031.6249.7.camel@skmhome> (raw)
In-Reply-To: <20070814110520.GA31682@redhat.com>
Hi Frank,
>> This might be just an effect of not doing a "make install", without
>> which the tcl-bridge component would not find tksm's script.
>> Script-based components work by compTcl scanning for their source
>> files someplace in the install tree. See the tail end of compTcl.cxx.
I cleaned the build tree completely and re-build again and performed sudo make install.
>> Did this result in a plausible sidcomptcl.so file?
I did find a libtclapi.a and libtclapi.so file in the install
path /opt/sid/sidcomp. Is this the file? Here are more detailed
contents of the folders.
Here are the contents of the build directory sid/component/tcl
compTcl.lo config.h config.status libtool stamp-h1
compTcl.o config.log libtclapi.la Makefile
and the contents of the install directory /opt/sid/lib
libbfd.a libopcodes.a libtclstub8.4.a sidcomp tk8.4
libbfd.la libopcodes.la libtk8.4.a sidsamples tkConfig.sh
libiberty.a libtcl8.4.a libtkstub8.4.a tclConfig.sh
and the contents of the install directory /opt/sid/lib/sidcomp
libaudio.a libide.la libparport.so.0.0.0
libaudio.la libide.so libprof.a
libaudio.so libide.so.0 libprof.la
libaudio.so.0 libide.so.0.0.0 libprof.so
libaudio.so.0.0.0 libinterrupt.a libprof.so.0
libcache.a libinterrupt.la libprof.so.0.0.0
libcache.la libinterrupt.so librtc.a
libcache.so libinterrupt.so.0 librtc.la
libcache.so.0 libinterrupt.so.0.0.0 librtc.so
libcache.so.0.0.0 liblcd-char-display.a librtc.so.0
libcgencpu.a liblcd-char-display.la librtc.so.0.0.0
libcgencpu.la liblcd-char-display.so libsched.a
libcgencpu.so liblcd-char-display.so.0 libsched.la
libcgencpu.so.0 liblcd-char-display.so.0.0.0 libsched.so
libcgencpu.so.0.0.0 libloader.a libsched.so.0
libconfig.a libloader.la libsched.so.0.0.0
libconfig.la libloader.so libt6963c.a
libconsoles.a libloader.so.0 libt6963c.la
libconsoles.la libloader.so.0.0.0 libt6963c.so
libconsoles.so libmapper.a libt6963c.so.0
libconsoles.so.0 libmapper.la libt6963c.so.0.0.0
libconsoles.so.0.0.0 libmapper.so libtclapi.a
libgdb.a libmapper.so.0 libtclapi.la
libgdb.la libmapper.so.0.0.0 libtclapi.so
libgdb.so libmemory.a libtclapi.so.0
libgdb.so.0 libmemory.la libtclapi.so.0.0.0
libgdb.so.0.0.0 libmemory.so libtimers.a
libgloss.a libmemory.so.0 libtimers.la
libgloss.la libmemory.so.0.0.0 libtimers.so
libgloss.so libmepfamily.a libtimers.so.0
libgloss.so.0 libmepfamily.la libtimers.so.0.0.0
libgloss.so.0.0.0 libmepfamily.so libuart.a
libglue.a libmepfamily.so.0 libuart.la
libglue.la libmepfamily.so.0.0.0 libuart.so
libglue.so libmmu.a libuart.so.0
libglue.so.0 libmmu.la libuart.so.0.0.0
libglue.so.0.0.0 libmmu.so libx86.a
libhd44780u.a libmmu.so.0 libx86.la
libhd44780u.la libmmu.so.0.0.0 libx86.so
libhd44780u.so libparport.a libx86.so.0
libhd44780u.so.0 libparport.la libx86.so.0.0.0
libhd44780u.so.0.0.0 libparport.so
libide.a libparport.so.0
Best Regards
Suleman
next prev parent reply other threads:[~2007-08-16 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 10:57 suleman
2007-08-14 11:05 ` Frank Ch. Eigler
2007-08-16 1:51 ` suleman
2007-08-16 2:04 ` Frank Ch. Eigler
2007-08-16 13:47 ` suleman [this message]
2007-08-15 13:06 suleman
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=1187272031.6249.7.camel@skmhome \
--to=sulemankm@gmail.com \
--cc=sid@sourceware.org \
/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).