About libstdc++ link staticlly

Bill C Riemers bcr@feynman.com
Wed Mar 8 17:20:00 GMT 2000

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.


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++( 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.,  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

More information about the Gcc-help mailing list