public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/19461] hidden __eprintf referenced by DSO, gas+gld
Date: Fri, 21 Jan 2005 17:40:00 -0000 [thread overview]
Message-ID: <20050121173827.18409.qmail@sourceware.org> (raw)
In-Reply-To: <20050115184713.19461.hp@gcc.gnu.org>
------- Additional Comments From hp at gcc dot gnu dot org 2005-01-21 17:38 -------
Digging further, there *is* a __eprintf reference in
/tmp/hptmp/obj/sparc-sun-solaris2.8/libstdc++-v3/src/.libs/libstdc++.so,
the one supposedly complained about when building the test-application.
Now, how did it get there?
Ah, it's in debug.o, from libstdc++-v3/src/debug.cc.
Apparently from the asserts there, likely from the gcc-2.95.2
installation? Perhaps we need to fixinclude away all __eprintf usage?
Strange that libstdc++.so could be created but not used (linked to).
Supposedly because there's another, non-hidden __eprintf somewhere?
I seem to recall a related problem discussed some time the last few
months. I don't remember the resolution. Maybe it was seen on darwin?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19461
next prev parent reply other threads:[~2005-01-21 17:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 18:47 [Bug bootstrap/19461] New: " hp at gcc dot gnu dot org
2005-01-15 19:08 ` [Bug bootstrap/19461] " pinskia at gcc dot gnu dot org
2005-01-15 19:15 ` ebotcazou at gcc dot gnu dot org
2005-01-15 19:20 ` ebotcazou at gcc dot gnu dot org
2005-01-15 20:17 ` hp at gcc dot gnu dot org
2005-01-15 20:20 ` hp at gcc dot gnu dot org
2005-01-15 20:22 ` pinskia at gcc dot gnu dot org
2005-01-15 22:06 ` ebotcazou at gcc dot gnu dot org
2005-01-15 22:31 ` hp at gcc dot gnu dot org
2005-01-19 7:28 ` ebotcazou at gcc dot gnu dot org
2005-01-19 9:34 ` hp at gcc dot gnu dot org
2005-01-20 16:37 ` hp at gcc dot gnu dot org
2005-01-20 17:01 ` ebotcazou at gcc dot gnu dot org
2005-01-21 2:08 ` hp at gcc dot gnu dot org
2005-01-21 5:19 ` ebotcazou at gcc dot gnu dot org
2005-01-21 16:49 ` hp at gcc dot gnu dot org
2005-01-21 17:09 ` hp at gcc dot gnu dot org
2005-01-21 17:12 ` hp at gcc dot gnu dot org
2005-01-21 17:28 ` ebotcazou at gcc dot gnu dot org
2005-01-21 17:40 ` hp at gcc dot gnu dot org [this message]
2005-01-21 17:42 ` hp at gcc dot gnu dot org
2005-05-18 21:04 ` hp at gcc dot gnu dot org
2005-07-15 22:02 ` pinskia at gcc dot gnu dot org
2005-07-15 22:12 ` ebotcazou at gcc dot gnu dot org
[not found] <bug-19461-507@http.gcc.gnu.org/bugzilla/>
2005-10-24 2:32 ` pinskia at gcc dot gnu dot org
2005-10-24 2:37 ` hp at gcc dot gnu dot org
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=20050121173827.18409.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).