Fedora - InstallationThis forum is for the discussion of installation issues with Fedora.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Check where the tcl package has installed the shared library:
Code:
rpm -ql tcl | grep lib
and see if it is in the library cache:
Code:
/sbin/ldconfig -p | grep libtcl
otherwise the RPM package can be broken or the system did not update the library cache correctly. If you find out that the tcl library is not in a standard place or does not appear in the cache, usually you can specify the correct location using some option of the configure script. Or eventually add the path to the library using the LDFLAGS environment variable and specify the library name using LIBS. Look at
Code:
./configure --help
to see which is the more suitable solution to the software you're going to compile. Another option is to update tcl to version 8.5, if the package is available for your system.
Edit: the configure script of scilab accepts the --with-tcl-library=DIR option.
klearview, I can't find scilab in my repository, although I know that the search doesn't always programs that I know are in the repository, but, anyway, I can't find it.
Hmmm... given the output of the suggested commands, apparently there is no reason why the scilab configuration should not find the tcl library, unless scilab is a 32-bit application and is looking for the 32-bit version of libtcl. You can try to install it. If the Add/Remove Software is not able to find the tcl packages for the reason you will investigate later, you can try
Code:
yum list tcl tcl-devel
from the command line and see if a 32-bit version is available for your system.
Having 32-bit and 64-bit libraries installed at the same time is possible, since they will be placed in different directories, e.g. /usr/lib vs. /usr/lib64, and the library cache will take in account the difference. As demonstrated by the error in ./configure.
Please note that mine was just a guess. I mean scilab being a 32-bit application. Anyway you can give it a try and eventually (if still not works) uninstall the 32-bit version of tcl.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.