/usr/bin/ld: cannot find -lCstd

[TsanChung]

How to fix the following error?

# make
....
g++ -o src/prog ./src/addSrv.o ./src/createClntCert_main.o ./src/
createSupportFile.o ./src/deleteSrv.o ./src/replaceSrv.o ./src/
examineClntCert.o ./src/examineClntCert_main.o ./src/listSrvs.o ./src/
registerSrv.o ./src/registerSrv_main.o ./src/verify.o ./src/
DynamicLibrary.o -L../../open_ssl_lib/openssl-0.9.7m/out/linux -
L../../util_lib/linux -lUtil -lssl -lcrypto -lCstd -lCrun -lsocket -
lnsl -lposix4 -lm -lw -lc -ldl
/usr/bin/ld: cannot find -lCstd
collect2: ld returned 1 exit status

$ g++ -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --
infodir=/usr/share/info --enable-shared --enable-threads=posix --
enable-checking=release --with-system-zlib --enable-__cxa_atexit --
disable-libunwind-exceptions --enable-libgcj-multifile --enable-
languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --
disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.4.2-
gcj-1.4.2.0/jre --with-cpu=generic --host=i386-redhat-linux
Thread model: posix
gcc version 4.1.2 20070626 (Red Hat 4.1.2-13)

$ uname -a
Linux tulip 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686
i686 i386 GNU/Linux

 

[Antoninus Twink]

How to fix the following error?

/usr/bin/ld: cannot find -lCstd

Put the library file libCstd.a or libCstd.so somewhere the linker can
find it: either a standard system directory, or one you tell it about
using a -L command line option or an environment variable like
LD_LIBRARY_PATH.

I think the library is part of Sun's compiler collection.

 

[Flash Gordon]

Antoninus Twink wrote, On 11/08/08 22:00:

Put the library file libCstd.a or libCstd.so somewhere the linker can
find it: either a standard system directory, or one you tell it about
using a -L command line option or an environment variable like
LD_LIBRARY_PATH.

I think the library is part of Sun's compiler collection.

Hmm. I wonder what Sun's compiler collection has to do with using gcc on
Linux (which the OP was doing based on the the information snipped by
Antoninus Twink).

To the OP, g++ is a C++ compiler not a C compiler so this has nothing to
do with C. It would probably not be topical on comp.lang.c++ either. I
suggest either a Linux group, a GNU group, or somewhere dealing with the
specific application you are trying to build. Where ever you post you
will need to provide more information.

 

[Martin Ambuhl]

How to fix the following error?

Quite apart from the likelihood that you have a Linux or make problem,
neither of which is topical in comp.lang.c,

g++ -o src/prog ./src/addSrv.o ./src/createClntCert_main.o ./src/

suggests that you are confused about the programming language you are
using. g++ is a C++ compiler, which compiles a different language from
C, which language is off-topic in comp.lang.c

 

[Antoninus Twink]

Antoninus Twink wrote, On 11/08/08 22:00:

Hmm. I wonder what Sun's compiler collection has to do with using gcc on
Linux (which the OP was doing based on the the information snipped by
Antoninus Twink).

A very pertinent question.

It's quite likely that the OP is trying to use a Makefile intended for
something like Slowlaris on Linux and running into problems - e.g.
because the configure script was run on a different machine to the one
he's compiling on.

To the OP, g++ is a C++ compiler not a C compiler so this has nothing
to do with C.

g++ will compile a large percentage of C programs without any problems,
and quite possibly produce valuable extra diagnostics that a C compiler
wouldn't. (Yes, yes, we all know that the clc "regulars" can cook up
contrived examples where the semantics are subtly different.)

 

[Flash Gordon]

Antoninus Twink wrote, On 11/08/08 23:12:

A very pertinent question.

<snip>

The pertinent part being that it makes your advise almost certainly the
wrong thing to do. Again.

g++ will compile a large percentage of C programs without any problems,
and quite possibly produce valuable extra diagnostics that a C compiler
wouldn't. (Yes, yes, we all know that the clc "regulars" can cook up
contrived examples where the semantics are subtly different.)

It is used far more to compile C++ code that is radically different.
With a provided make-file it almost certainly means that the code was
written as C++ not as C. Are you now claiming that C++ is topical here?

 

[Richard Bos]

Antoninus Twink wrote, On 11/08/08 23:12:

<snip>

The pertinent part being that it makes your advise almost certainly the
wrong thing to do. Again.

The most pertinent part being that it illustrates something, not so much
about Mr. Twink (who needs no illumination), but about why it is a bad
idea to answer off-topic questions here in general.

Richard

 

[CBFalconer]

Given that there are infinitely many possible C programs, how can
you make any meaningful claim about the percentage of them that
any particular compiler can compile?

--
+-------------------+ .:\:\:/:/:.
| PLEASE DO NOT F :.:\:\:/:/:.:
| FEED THE TROLLS | :=.' - - '.=:
| | '=(\ 9 9 /)='
| Thank you, | ( (_) )
| Management | /`-vvv-'\
+-------------------+ / \
| | @@@ / /|,,,,,|\ \
| | @@@ /_// /^\ \\_\
@x@@x@ | | |/ WW( ( ) )WW
\||||/ | | \| __\,,\ /,,/__
\||/ | | | jgs (______Y______)
/\/\/\/\/\/\/\/\//\/\\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
==============================================================

fix (vb.): 1. to paper over, obscure, hide from public view; 2.
to work around, in a way that produces unintended consequences
that are worse than the original problem. Usage: "Windows ME
fixes many of the shortcomings of Windows 98 SE". - Hutchinson

 

[Richard Tobin]

g++ will compile a large percentage of C programs without any problems,

[/QUOTE]

Given that there are infinitely many possible C programs, how can you make
any meaningful claim about the percentage of them that any particular
compiler can compile?

He didn't say a large percentage of possible C programs.

-- Richard