Hi Patrick,
On Fri, Oct 27, 2000 at 05:58:33PM +0200, Patrick Guio wrote:
> For the KCC compiler I had to include in the configure.in
>
> CXX="KCC"
> CXX_OPTIMIZE_FLAGS="+K3 -O3"
> CXX_DEBUG_FLAGS="-g +K0 -DBZ_DEBUG"
> CXXFLAGS="--restrict --strict_warnings --one_instantiation_per_object
Hi Patrick,
On Fri, Oct 27, 2000 at 01:39:29PM +0200, Patrick Guio wrote:
> Actually when creating a library with KCC, the instruction should be
>
> KCC -o .libs/libmudfas3d.a libmudfas3d_la-init.o libmudfas3d_la-lop.o
> libmudfas3d_la-mudfas.o libmudfas3d_la-prolon.o libmudfas3d_la-qnc.o
>
Dear all
I think I got *nearly* it:-)
For the KCC compiler I had to include in the configure.in
CXX="KCC"
CXX_OPTIMIZE_FLAGS="+K3 -O3"
CXX_DEBUG_FLAGS="-g +K0 -DBZ_DEBUG"
CXXFLAGS="--restrict --strict_warnings --one_instantiation_per_object"
AR="KCC"
AR_FLAGS="-o"
and of cours decl
After 'configure' on HP-UX, the 'libtool' script contains the following
'hardcode' values:
hardcode_action=relink
hardcode_into_libs=no
hardcode_libdir_flag_spec="\${wl}+b \${wl}\$libdir"
hardcode_libdir_separator=":"
hardcode_direct=yes
hardcode_minus_L=yes
har
Small correction!
The archive command is
ar -rv
*not*
ar -ts
Otherwise I think that the problem is comin from the fact that there are
no .lo corresponding to the .o in the templates directory
maybe something like
foreach obj (repository/*.o
ln -fs $obj $obj:r.lo
end
before running bin/ksh ..
Dear all
As you know I am trying to use libtool :-) Now on a DEC machine when I am
trying to create a library, here what is happening:
The sources are well compiled, for example:
% source='argparsing.cpp'
object='libutilities_la-argparsing.lo' libtool=yes \
depfile='.deps/libutilities_la-argpars
Dear all
I try to use libtool to build a c++ library and I get the following
/bin/sh ../libtool --mode=link KCC --restrict --strict_warnings
-L/usr/local/numerics/blitz/blitz/lib -lblitz
-L/usr/local/hdf/4.1r3_hpux/lib -lmfhdf -ldf -ljpeg -lz -o libmudfas3d.la
-rpath /temp/lib -version-info 0:
