From: "Frank Ch. Eigler" <fche@redhat.com>
To: Andre <armcc@lycos.com>
Cc: sid@sources.redhat.com
Subject: Re: 'bridge-tk unknown' when trying to run demo
Date: Wed, 25 Jul 2001 09:40:00 -0000 [thread overview]
Message-ID: <20010725124014.E18044@redhat.com> (raw)
In-Reply-To: <3B4DB97D.A616E537@lycos.com>
Hi -
On Thu, Jul 12, 2001 at 10:51:41AM -0400, Andre wrote:
: [...]
: > Right. The bridge-tk component requires among other things that
: > the tcl-bridge component be available as a shared library
: > (in $prefix/lib/sidcomp) or statically linked into the
: > $prefix/bin/sid executable,
:
: What would trigger the configure script to try one over the other ??
The sid/configure{.in} script looks for the existence of
a libstdc++ shared library (.so or .dll). It looks like for
your machine, full shared + static library building is triggered.
The log/ls-lR files you sent over suggest that everything built
and installed as expected.
: [...]
: > (Also, please be aware that this old demo is not frequently tested
: > any more.)
:
: Does this mean there is a newer demo somewhere ?? I have no special
: interest in a voice-pager - I simply wanted something to verify that
: everything is working :-)
Running "make check" in the sid build directory is one way to ensure
that the system is built well enough. Actually using it, by running
or debugging some cross-compiled applications (see the new documentation
or the online FAQ), is the the best way.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7XvZuVZbdDOm/ZT0RAqLfAJ48HXITN/CHeENGSqyvemyQiCx1XgCeOvOX
0fRY4grQsYC6bLG1q7qncUI=
=ed6q
-----END PGP SIGNATURE-----
next parent reply other threads:[~2001-07-25 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B4DB97D.A616E537@lycos.com>
2001-07-25 9:40 ` Frank Ch. Eigler [this message]
2001-07-08 4:51 Andre
2001-07-11 13:59 ` Frank Ch. Eigler
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=20010725124014.E18044@redhat.com \
--to=fche@redhat.com \
--cc=armcc@lycos.com \
--cc=sid@sources.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).