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: Wed, 08 Mar 2000 17:20:00 -0000 [thread overview]
Message-ID: <38C6FC1B.BFF8A65D@feynman.com> (raw)
In-Reply-To: <20000308211734.7974.qmail@web1610.mail.yahoo.com>
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
WARNING: multiple messages have this Message-ID
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 [thread overview]
Message-ID: <38C6FC1B.BFF8A65D@feynman.com> (raw)
Message-ID: <20000401000000.5SGvIttuW2uJIyvTITw0SAThb61Q5fsSeYsHVfA_1fs@z> (raw)
In-Reply-To: <20000308211734.7974.qmail@web1610.mail.yahoo.com>
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
next prev parent reply other threads:[~2000-03-08 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-08 13:17 greg zhang
2000-03-08 17:20 ` Bill C Riemers [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38C6FC1B.BFF8A65D@feynman.com \
--to=bcr@feynman.com \
--cc=gregzh@yahoo.com \
--cc=help-gcc@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).