From: Loren James Rittle <rittle@latour.rsch.comm.mot.com>
To: gcc-patches@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: PATCH: Re: Another 3.0-branch bootstrap failure
Date: Tue, 17 Apr 2001 17:05:00 -0000 [thread overview]
Message-ID: <200104180005.f3I05VP64299@latour.rsch.comm.mot.com> (raw)
In-Reply-To: <Pine.BSF.4.33.0104170853020.96026-100000@taygeta.dbai.tuwien.ac.at>
Hi Gerald,
> ...this time for i386-unknown-freebsd4.2. This really shouldn't happen
> that late during a release cycle: [...missing N_OPT symbol...]
Already on it. Although an obvious fix, I conferred with Zack and
waited until my bootstraps completed. Patch just installed on both
mainline and 3.0 with Zack's approval.
I bow my head that I didn't look at Zack's patch closely before he
applied it.
Regards,
Loren
2001-04-17 Loren J. Rittle <ljrittle@acm.org>
* dbxout.c (N_OPT): Define if not available from <stab.h>
Index: gcc/dbxout.c
===================================================================
RCS file: /cvs/gcc/egcs/gcc/dbxout.c,v
retrieving revision 1.77
diff -c -8 -r1.77 dbxout.c
*** dbxout.c 2001/04/16 18:30:31 1.77
--- dbxout.c 2001/04/17 01:30:44
***************
*** 178,193 ****
--- 178,198 ----
#include "gstab.h" /* If doing DBX on sysV, use our own stab.h. */
#else
#include <stab.h>
/* This is a GNU extension we need to reference in this file. */
#ifndef N_CATCH
#define N_CATCH 0x54
#endif
+
+ /* This is a Solaris extension we need to reference in this file. */
+ #ifndef N_OPT
+ #define N_OPT 0x3c
+ #endif
#endif
#ifdef __GNU_STAB__
#define STAB_CODE_TYPE enum __stab_debug_code
#else
#define STAB_CODE_TYPE int
#endif
prev parent reply other threads:[~2001-04-17 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 0:07 Gerald Pfeifer
2001-04-17 0:22 ` Zack Weinberg
2001-04-17 17:05 ` Loren James Rittle [this message]
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=200104180005.f3I05VP64299@latour.rsch.comm.mot.com \
--to=rittle@latour.rsch.comm.mot.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@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).