Re: Confusion over library names

2000-12-28 Thread Colin Watson
"Michael and Ricia Banther" <[EMAIL PROTECTED]> wrote: >I've just recently started using Debian Linux. I've been trying out a >"Hello, world" C++ program, and I've noticed what seems to be an odd naming >disconnect with the files in /usr/lib. > >The ld program supports a -l command line option. T

Re: Confusion over library names

2000-12-28 Thread D-Man
When libraries are named, the developer picks some sort of version number for it. That version number goes after the .so part of the filename. My guess for that libstdc++ you have is that it is for g++ 2.7.2 (old!). You probably have another one for 2.95.2. If you need to build a program yours

Re: Confusion over library names

2000-12-28 Thread Richard Cobbe
Lo, on Thursday, December 28, Michael and Ricia Banther did write: > The ld program supports a -l command line option. Why are you calling ld directly? g++ should do that for you--especially with respect to libstdc++ (see below). (Of course, gcc/g++ supports the same parameter.) > Playing arou

Confusion over library names

2000-12-28 Thread Michael and Ricia Banther
Hi, I've just recently started using Debian Linux. I've been trying out a "Hello, world" C++ program, and I've noticed what seems to be an odd naming disconnect with the files in /usr/lib. The ld program supports a -l command line option. This option, as I understand it, instructs ld to search