public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* About libstdc++ link staticlly
@ 2000-03-08 13:17 greg zhang
  2000-03-08 17:20 ` Bill C Riemers
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: greg zhang @ 2000-03-08 13:17 UTC (permalink / raw)
  To: help-gcc

Dear sir,

There is a problem when I compile my project with
C++(gcc).

Now, my project is a shared project, but I want to
link libstdc++(2.8.1.1) staticlly, avoiding release
this project with libstdc++, But I fail to do it.

To a normal project(I mean exe module), I can do it
with just removing libstdc++.so.2.8.1.1.,  gcc will
link libstdc++.a archive file automaticlly.

To this shared object, I failed, and gave me a tip:

Text relocation remains            reference file
 against symbol      
<unknown>                          ..../XXX.o
fprintf                            ..../XXX.o

ld: fatal: relocation remains against allocatable but
non-writable sections.

I don't know how to fix it?

Could you help me?

Thanks.

I am very appricate if you reply me to this email address.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: About libstdc++ link staticlly
  2000-03-08 13:17 About libstdc++ link staticlly greg zhang
@ 2000-03-08 17:20 ` Bill C Riemers
  2000-04-01  0:00   ` Bill C Riemers
  2000-03-09 16:59 ` Alexandre Oliva
  2000-04-01  0:00 ` greg zhang
  2 siblings, 1 reply; 6+ messages in thread
From: Bill C Riemers @ 2000-03-08 17:20 UTC (permalink / raw)
  To: greg zhang; +Cc: help-gcc

I'd love to here an answer to this one.  Dynamic libstdc++.so 
has been an end less source of troubles.  Usually I modify
the gcc Makefile's manually before building anything to avoid
the problem.  I have one machine where someone else has installed
the compiler, and I've yet to remove the libstdc++.so dependency.

			Bill


greg zhang wrote:
> 
> Dear sir,
> 
> There is a problem when I compile my project with
> C++(gcc).
> 
> Now, my project is a shared project, but I want to
> link libstdc++(2.8.1.1) staticlly, avoiding release
> this project with libstdc++, But I fail to do it.
> 
> To a normal project(I mean exe module), I can do it
> with just removing libstdc++.so.2.8.1.1.,  gcc will
> link libstdc++.a archive file automaticlly.
> 
> To this shared object, I failed, and gave me a tip:
> 
> Text relocation remains            reference file
>  against symbol
> <unknown>                          ..../XXX.o
> fprintf                            ..../XXX.o
> 
> ld: fatal: relocation remains against allocatable but
> non-writable sections.
> 
> I don't know how to fix it?
> 
> Could you help me?
> 
> Thanks.
> 
> I am very appricate if you reply me to this email address.
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: About libstdc++ link staticlly
  2000-03-08 13:17 About libstdc++ link staticlly greg zhang
  2000-03-08 17:20 ` Bill C Riemers
@ 2000-03-09 16:59 ` Alexandre Oliva
  2000-04-01  0:00   ` Alexandre Oliva
  2000-04-01  0:00 ` greg zhang
  2 siblings, 1 reply; 6+ messages in thread
From: Alexandre Oliva @ 2000-03-09 16:59 UTC (permalink / raw)
  To: greg zhang; +Cc: help-gcc

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

On Mar  8, 2000, greg zhang <gregzh@yahoo.com> wrote:

> To a normal project(I mean exe module), I can do it
> with just removing libstdc++.so.2.8.1.1.,  gcc will
> link libstdc++.a archive file automaticlly.

> Text relocation remains            reference file
>  against symbol      
> <unknown>                          ..../XXX.o
> fprintf                            ..../XXX.o

> ld: fatal: relocation remains against allocatable but
> non-writable sections.

> I don't know how to fix it?

You'd have to compile all objects of the static libstdc++ with -fPIC
to be able to link a shared library with it.

-- 
Alexandre Oliva     http://www.ic.unicamp.br/~oliva/     Enjoy Guaraná
Cygnus Solutions, a Red Hat company        aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist    CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me

^ permalink raw reply	[flat|nested] 6+ messages in thread

* About libstdc++ link staticlly
  2000-03-08 13:17 About libstdc++ link staticlly greg zhang
  2000-03-08 17:20 ` Bill C Riemers
  2000-03-09 16:59 ` Alexandre Oliva
@ 2000-04-01  0:00 ` greg zhang
  2 siblings, 0 replies; 6+ messages in thread
From: greg zhang @ 2000-04-01  0:00 UTC (permalink / raw)
  To: help-gcc

Dear sir,

There is a problem when I compile my project with
C++(gcc).

Now, my project is a shared project, but I want to
link libstdc++(2.8.1.1) staticlly, avoiding release
this project with libstdc++, But I fail to do it.

To a normal project(I mean exe module), I can do it
with just removing libstdc++.so.2.8.1.1.,  gcc will
link libstdc++.a archive file automaticlly.

To this shared object, I failed, and gave me a tip:

Text relocation remains            reference file
 against symbol      
<unknown>                          ..../XXX.o
fprintf                            ..../XXX.o

ld: fatal: relocation remains against allocatable but
non-writable sections.

I don't know how to fix it?

Could you help me?

Thanks.

I am very appricate if you reply me to this email address.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: About libstdc++ link staticlly
  2000-03-08 17:20 ` Bill C Riemers
@ 2000-04-01  0:00   ` Bill C Riemers
  0 siblings, 0 replies; 6+ messages in thread
From: Bill C Riemers @ 2000-04-01  0:00 UTC (permalink / raw)
  To: greg zhang; +Cc: help-gcc

I'd love to here an answer to this one.  Dynamic libstdc++.so 
has been an end less source of troubles.  Usually I modify
the gcc Makefile's manually before building anything to avoid
the problem.  I have one machine where someone else has installed
the compiler, and I've yet to remove the libstdc++.so dependency.

			Bill


greg zhang wrote:
> 
> Dear sir,
> 
> There is a problem when I compile my project with
> C++(gcc).
> 
> Now, my project is a shared project, but I want to
> link libstdc++(2.8.1.1) staticlly, avoiding release
> this project with libstdc++, But I fail to do it.
> 
> To a normal project(I mean exe module), I can do it
> with just removing libstdc++.so.2.8.1.1.,  gcc will
> link libstdc++.a archive file automaticlly.
> 
> To this shared object, I failed, and gave me a tip:
> 
> Text relocation remains            reference file
>  against symbol
> <unknown>                          ..../XXX.o
> fprintf                            ..../XXX.o
> 
> ld: fatal: relocation remains against allocatable but
> non-writable sections.
> 
> I don't know how to fix it?
> 
> Could you help me?
> 
> Thanks.
> 
> I am very appricate if you reply me to this email address.
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: About libstdc++ link staticlly
  2000-03-09 16:59 ` Alexandre Oliva
@ 2000-04-01  0:00   ` Alexandre Oliva
  0 siblings, 0 replies; 6+ messages in thread
From: Alexandre Oliva @ 2000-04-01  0:00 UTC (permalink / raw)
  To: greg zhang; +Cc: help-gcc

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

On Mar  8, 2000, greg zhang <gregzh@yahoo.com> wrote:

> To a normal project(I mean exe module), I can do it
> with just removing libstdc++.so.2.8.1.1.,  gcc will
> link libstdc++.a archive file automaticlly.

> Text relocation remains            reference file
>  against symbol      
> <unknown>                          ..../XXX.o
> fprintf                            ..../XXX.o

> ld: fatal: relocation remains against allocatable but
> non-writable sections.

> I don't know how to fix it?

You'd have to compile all objects of the static libstdc++ with -fPIC
to be able to link a shared library with it.

-- 
Alexandre Oliva     http://www.ic.unicamp.br/~oliva/     Enjoy Guaraná
Cygnus Solutions, a Red Hat company        aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist    CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2000-04-01  0:00 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-03-08 13:17 About libstdc++ link staticlly greg zhang
2000-03-08 17:20 ` Bill C Riemers
2000-04-01  0:00   ` Bill C Riemers
2000-03-09 16:59 ` Alexandre Oliva
2000-04-01  0:00   ` Alexandre Oliva
2000-04-01  0:00 ` greg zhang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).