Re: g++ 3.1: libstdc++.so.3 problem

[Oliver Kullmann <O dot Kullmann at Swansea dot ac dot uk>]

On Wednesday 10 July 2002 13:48, you wrote:
> Oliver Kullmann wrote:
> >Hi,
> >
> >I have build gcc 3.1, and mostly it seems to be alright,
> >my programs compile without any messages and most of them
> >also run, except of one, where I get the error message:
> >
> >error while loading shared libraries: libstdc++.so.3: cannot open shared
> >object file: No such file or directory
> >
> >Where should this libstdc++.so.3 be?! It's not in the
> >implementation lib-directory, which only contains
> >
> >gcc-lib        libiberty.a   libstdc++.so        libsupc++.a
> >libgcc_s.so    libstdc++.a   libstdc++.so.4      libsupc++.la
> >libgcc_s.so.1  libstdc++.la  libstdc++.so.4.0.0
> >
> >As I said, the compilation doesn't give any warnings, so it shouldn't
> >be a deprecated header. What is the problem here?!
> >
> >Any help is greatly appreciated!
> >
> >Oliver
>
> Login as root and make a soft link as follows:
>  $ ln  -s  libstdc++.so.4.0.0  libstdc++.so.3
> then refresh share library info using ldconfig:
> $ ldconfig
>   This maybe help you.
>
> Good Luck.

Thanks a lot! Unfortunately, I don't have root access to this
(remote) machine --- I 	have requested the changes, but according
to my experiences this may never happen.

Therefore I do static compilation, and give the link to the library:

/GCC/gcc31/bin/g++ -static -L/GCC/gcc31/lib/ program.cpp

where GCC/gcc31 is the installation directory.
Since I can not change the dynamic linking, it seems necessary
to avoid any dynamic linking. How can I force g++ to really do
no dynamic linking?!

-- 
Dr. Oliver Kullmann
Computer Science Department
University of Wales Swansea
Faraday Building, Singleton Park
Swansea SA2 8PP, UK
http://cs-svr1.swan.ac.uk/~csoliver/