[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: C++ transition stumbling blocks?

On Thu, Jan 23, 2003 at 08:59:28AM +0100, Marcelo E. Magallon wrote:
>  /bin/sh ../libtool --mode=link g++  -g -O2  -o libGLU.la -rpath /usr/local/lib -version-info 4:500:3 -L../src dummy.lo -lGL 	libnurbs/interface/libNIFac.la 	libnurbs/internals/libNInt.la 	libnurbs/nurbtess/libNTess.la 	libtess/libtess.la 	libutil/libutil.la 
>  rm -fr .libs/libGLU.la .libs/libGLU.* .libs/libGLU.*
>  gcc -shared  dummy.lo -Wl,--whole-archive libnurbs/interface/.libs/libNIFac.al libnurbs/internals/.libs/libNInt.al libnurbs/nurbtess/.libs/libNTess.al libtess/.libs/libtess.al libutil/.libs/libutil.al -Wl,--no-whole-archive  -L/usr/X11R6/lib -L/build/buildd/mesa-5.0.0/build/swr/src /build/buildd/mesa-5.0.0/build/swr/src/.libs/libGL.so  -Wl,-soname -Wl,libGLU.so.1 -o .libs/libGLU.so.1.3.500
>  Any clue as to why that happens?

The mysteries of libtool are well beyond me, but perhaps just adding
-lsupc++ (if it's sufficient, otherwise -lstdc++) would help?

Colin Watson                                  [cjwatson@flatline.org.uk]
Basically, people got tired of portability problems in building shared
libraries so they hid them all inside a multi-thousand line shell script
where no one can ever find them because everyone who tries goes blind.
 -- Russ Allbery

Reply to: