This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/49209] unresolved references to fatal() while linking xgcc and cpp
- From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 28 May 2011 21:07:50 +0000
- Subject: [Bug bootstrap/49209] unresolved references to fatal() while linking xgcc and cpp
- Auto-submitted: auto-generated
- References: <bug-49209-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49209
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2011.05.28 21:07:21
CC| |ebotcazou at gcc dot
| |gnu.org
Summary|Solaris10/SPARC: gcc.c has |unresolved references to
|unresolved references to |fatal() while linking xgcc
|fatal() while linking xgcc |and cpp
|and cpp |
Ever Confirmed|0 |1
Build| |sparc-sun-solaris2.10
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-05-28 21:07:21 UTC ---
> I just tried to bootstrap gcc-4.6.0 on Solaris10 and got this:
GCC is known to bootstrap flawlessly on this platform, so this is unexpected.
> I fixed this by copying the fatal() from gcc/errors.c to gcc/diagnostic.c.
> However, it is not clear to me why the link succeeds on Debian Lenny (x64) and
> fails on Solaris10.
Yes, please find out where this reference to 'fatal' comes from.
> I also recognized that there is some code duplication in diagnostic.c and
> errors.c, maybe they're candidates for a cleanup?
See the comment at the beginning of the errors.c file.