RE: GCC Build Status for SCO OS 5.0.5

["Rakshit Karnavat, Gurgaon" <rakshit@ggn.hcltech.com>]

  You confused me there. Without the libstdc++.so(which is created only when
the
   --enable-shared option is given), for some of the applications, gcc is
not able to find 
   some symbols during linking. This is precisely the problem I am facing.
    If I try to make share objects with the archive version of
std(libstdc++.a), certains symbols are not resolved by the linker. Those
symbols are not of the application itself, because I am able to make the
shared object using the native cc(unfortunately, that gives core dumps when
binaries are made out of it).
   There was another problem I had faced. For making the shared library, gcc
asks for pic/libgcc.a,
  which was not to be found. To overcome it, I made a soft link by that
name. Is there another 
    way to do it(the correct way)?
Thanks
Rakshit.
  

> ----------
> From: 	Robert Lipe[SMTP:robertlipe@usa.net]
> Sent: 	Wednesday, November 28, 2001 7:57 PM
> To: 	Rakshit Karnavat , Gurgaon
> Cc: 	gcc@gcc.gnu.org
> Subject: 	Re: GCC Build Status for SCO OS 5.0.5
> 
> Rakshit Karnavat , Gurgaon wrote:
> 
> >   I was unable to make gcc 3.0.1 using the --enable-shared option in
> > the i386 environment. Without that option, everything runs fine. But
> > then, I am unable to make shared libraries using gcc. I make shared
> 
> Those two concepts shouldn't have anything to do with each other.
> "--enable-shared" controls whether gcc's own libraries are built as
> shared libes or not, not whether gcc can generate shared libraries.
> 
> > Is it possible to make shared libraries with gcc on SCO OS 5.*
> 
> Yes.
> 
> RJL
>