From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bill C Riemers <bcr@feynman.com>
To: greg zhang <gregzh@yahoo.com>
Cc: help-gcc@gnu.org
Subject: Re: About libstdc++ link staticlly
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-ID: <38C6FC1B.BFF8A65D@feynman.com>
References: <20000308211734.7974.qmail@web1610.mail.yahoo.com>
X-SW-Source: 2000-q1/msg00350.html
Message-ID: <20000401000000.5SGvIttuW2uJIyvTITw0SAThb61Q5fsSeYsHVfA_1fs@z>

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