RE: GCC Build Status for SCO OS 5.0.5

RE: GCC Build Status for SCO OS 5.0.5

[Rakshit Karnavat , Gurgaon]

   As an example, I made a shared library using gcc.
  When I tried to use this library with my another example cpp,
  the error it gives is
    Undefied symbol
file
    __gcc_personality_v0
/usr/tmp/ccuDJkKd.o
  The message it gives is : symbol referencing error.
     No clue what it is.
Rakshit.


> ----------
> From: 	Phil Edwards[SMTP:pedwards@disaster.jaj.com]
> Sent: 	Thursday, November 29, 2001 12:52 AM
> To: 	Rakshit Karnavat , Gurgaon
> Cc: 	Robert Lipe; gcc@gcc.gnu.org
> Subject: 	Re: GCC Build Status for SCO OS 5.0.5
> 
> On Wed, Nov 28, 2001 at 09:13:00PM +0530, Rakshit Karnavat , Gurgaon
> wrote:
> >     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,
> 
> Which symbols are they, i.e., what are their names?
> 
> Phil
> 
> -- 
> If ye love wealth greater than liberty, the tranquility of servitude
> greater
> than the animating contest for freedom, go home and leave us in peace.  We
> seek
> not your counsel, nor your arms.  Crouch down and lick the hand that feeds
> you;
> and may posterity forget that ye were our countrymen.            - Samuel
> Adams
> 

Re: GCC Build Status for SCO OS 5.0.5

[Phil Edwards]

On Thu, Nov 29, 2001 at 11:40:10AM +0530, Rakshit Karnavat , Gurgaon wrote:
> 
>    As an example, I made a shared library using gcc.
>   When I tried to use this library with my another example cpp,

If you write C++ code, then you must use g++ to perform the linking.

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

RE: GCC Build Status for SCO OS 5.0.5

[Rakshit Karnavat, Gurgaon]

   As an example, I made a shared library using gcc.
  When I tried to use this library with my another example cpp,
  the error it gives is
    Undefied symbol
file
    __gcc_personality_v0
/usr/tmp/ccuDJkKd.o
  The message it gives is : symbol referencing error.
     No clue what it is.
Rakshit.


> ----------
> From: 	Phil Edwards[SMTP:pedwards@disaster.jaj.com]
> Sent: 	Thursday, November 29, 2001 12:52 AM
> To: 	Rakshit Karnavat , Gurgaon
> Cc: 	Robert Lipe; gcc@gcc.gnu.org
> Subject: 	Re: GCC Build Status for SCO OS 5.0.5
> 
> On Wed, Nov 28, 2001 at 09:13:00PM +0530, Rakshit Karnavat , Gurgaon
> wrote:
> >     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,
> 
> Which symbols are they, i.e., what are their names?
> 
> Phil
> 
> -- 
> If ye love wealth greater than liberty, the tranquility of servitude
> greater
> than the animating contest for freedom, go home and leave us in peace.  We
> seek
> not your counsel, nor your arms.  Crouch down and lick the hand that feeds
> you;
> and may posterity forget that ye were our countrymen.            - Samuel
> Adams
> 

Re: GCC Build Status for SCO OS 5.0.5

[Phil Edwards]

On Thu, Nov 29, 2001 at 11:40:10AM +0530, Rakshit Karnavat , Gurgaon wrote:
> 
>    As an example, I made a shared library using gcc.
>   When I tried to use this library with my another example cpp,

If you write C++ code, then you must use g++ to perform the linking.

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

Re: GCC Build Status for SCO OS 5.0.5

[Phil Edwards]

On Wed, Nov 28, 2001 at 09:13:00PM +0530, Rakshit Karnavat , Gurgaon wrote:
>     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,

Which symbols are they, i.e., what are their names?

Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

RE: GCC Build Status for SCO OS 5.0.5

[Rakshit Karnavat, Gurgaon]

  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
> 

Re: GCC Build Status for SCO OS 5.0.5

[Robert Lipe]

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

GCC Build Status for SCO OS 5.0.5

[Rakshit Karnavat, Gurgaon]

  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 libraries
using the native cc.
   But it is not serving the purpose. Any help on this front??
 Is it possible to make shared libraries with gcc on SCO OS 5.*

Rakshit.

Re: GCC Build Status for SCO OS 5.0.5

[Phil Edwards]

On Wed, Nov 28, 2001 at 09:13:00PM +0530, Rakshit Karnavat , Gurgaon wrote:
>     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,

Which symbols are they, i.e., what are their names?

Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

RE: GCC Build Status for SCO OS 5.0.5

[Rakshit Karnavat , Gurgaon]

  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
> 

Re: GCC Build Status for SCO OS 5.0.5

[Robert Lipe]

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

GCC Build Status for SCO OS 5.0.5

[Rakshit Karnavat , Gurgaon]

  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 libraries
using the native cc.
   But it is not serving the purpose. Any help on this front??
 Is it possible to make shared libraries with gcc on SCO OS 5.*

Rakshit.