missing libraries

babelfish · 08-16-2001, 01:38 AM

I'm running SuSE 7.0 on a mac ppc g4. I'm pretty much new to linux, but lately I've learned a lot by trying and failing to install some downloaded software. The software is "PDP++", available as a free download from the website promoting a text called "Computational Explorations in Cognitive Neuroscience." It should be very cool. BUT every time I try to install it I find that I'm missing some library or another. The ones I really seem to be lacking are "libtermcap.so.2" and "libiostream". I've been back and forth to the GNU site... and I've downloaded gdb, glibc and terminal capabilities in my endless quest for these libraries. Now, I do have "libtermcap.a" ... is there some way to convert that to a shared object file? And I've got loads of files called "iostream" or "iostream.h". Just none called "libiostream." Again, is there some way to generate a library from these other files? Something tells me I need to download something else. Or use MacOs X...

I'll appreciate any help y'all can give. Even from coproscefalos, whose name in greek means "excrement head."

babelfish

isajera · 08-16-2001, 02:05 AM

it sounds like you didn't install some of the development libraries when you installed linux. go back with YaST and poke around the packages a bit more.

cinnix · 08-16-2001, 03:15 AM

the libtermcap dependency is from the libtermcap package. If you have that installed and PDP++ cannot find it then you may have to point it in the right direction by passing a flag to your configure script.

I am not too sure what the libiostream dependency is coming from but I did frind this info from the "G++ FAQ Frequently asked questions about the GNU C++ compiler" at http://fubphpc.tu-graz.ac.at/FAQ/g++FAQ.html

Quote:

The GNU Standard C++ Library (also called the "GNU ANSI C++ Library" in places in the code) is not libg++, though it is included in the libg++ distribution. Rather, it contains classes and functions required by the ANSI/ISO standard. The copyright conditions are the same as those for for the iostreams classes; the LGPL is not used (see section What are the rules for shipping code built with g++ and libg++?).

This library, libstdc++, is in the libg++ distribution in versions 2.6.2 and later. It requires at least gcc 2.6.3 to build the libg++-2.6.2 version; use at least gcc 2.7.0 to build the libg++ 2.7.0 version. It contains a hacked-up version of HP's implementation of the Standard Template Library (see section Does g++ support the Standard Template Library?). I've successfully used this Standard Template Library version to build a number of the demos you'll see on various web pages.

As of version 2.7.0, the streams classes are now in libstdc++ instead of libg++, and libiostream is being phased out (don't use it). The g++ program searches this library.

The maintainers of libg++ have de-emphasized work on the older libg++ classes in favor of enhancing libstdc++ to cover the full language, so while libg++ will always be available, enhancements to it should not be expected.

I also found a little info here that may relate to your problem. http://www.cnbc.cmu.edu/PDP++/discuss/msg00545.html

Good Luck.

babelfish · 08-16-2001, 08:19 PM

hi again.

i have been to yast and looked at the packages... now that i've installed gdb, glibc and termcap i really don't know what else i could install. however, i am curious about what you mean by "passing a flag." maybe you could give me some more details about what that is and how i could accomplish it? i'll check in that directory for the libiostream file. if it's not there, what might i install that would be likely to have it?

babelfish

cinnix · 08-17-2001, 02:49 AM

Quote:

libiostream still exists only because gcc2.6.3 is still around

Have you installed g++ because it looks like this 'libiostream.a' is part of that package. If it isn't then I would suggest contacting the PDP++ package maintainers to ask where this dependency is coming from.

As far as passing flags to configure go, you can see what flags are availble by looking at your configure script. In my experience a short explanation about each flag is listed at the end of the file.

an example of a flag would be something like..

./configure --with-mysql