Greetings all,
While trying to build a shared library that makes use of the STL
with the SunWorkshop C++ compiler 4.2 on Solaris 2.6, I have found
the Sun's CC does not work quite right if, when building the shared
library, .lo files are specified as the objects to link. The compiler
does not r
>
> > > Also, almost everything works after changing all the .lo's to .o's.
> >
> > Yup. In the multi-language branch, IIRC, the .lo file is placed in
> > the .libs directory, named `.o', and the .lo file is created as a
> > wrapper script, just like the .la files.
>
> Yes indeed. :-)
Is th
ED]>
>
> Hi Christopher,
>
> On Thu, Mar 23, 2000 at 10:39:39AM -0600, Christopher Knight wrote:
> > Is the multi-language-branch at a state that I could check it out and use it
> > to build?
>
> The short answer is that if you only need to use the core libtool
> f
Greetings all,
I'm now using libtool-ml to build my project and now need to somehow force
a single library (tcl, :( I know, I know) statically although the dynamic
library exists along side the static one (It would also be next to
impossible for me to remove this). With libtool 1.3 I simply dump
Ossama,
Is the multi-language-branch at a state that I could check it out and use it
to build?
Chris
> On Mar 23, 2000, Christopher Knight <[EMAIL PROTECTED]> wrote:
>
> > Is there any hack that anyone can think of to switch libtool's usage
> > of .lo's t
Hi Stephen,
Thanks for the info. I'll be sure to check out 1.5 and send in any patches when
I have them.
Assistant Vice President means Vice President before your company was eaten up
by a merger :-)
Take Care
Chris
> Christopher Knight wrote:
> >
> > Hi Ossama,
> >