From: Jakub Jelinek <jakub@redhat.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Andreas Jaeger <aj@suse.de>, gcc@gcc.gnu.org
Subject: Re: GCC Bootstrap currently broken
Date: Sat, 15 Dec 2001 12:58:00 -0000 [thread overview]
Message-ID: <20011215152216.Z4087@devserv.devel.redhat.com> (raw)
In-Reply-To: <20011215190908.GA14890@codesourcery.com>; from zack@codesourcery.com on Sat, Dec 15, 2001 at 11:09:08AM -0800
On Sat, Dec 15, 2001 at 11:09:08AM -0800, Zack Weinberg wrote:
> On Sat, Dec 15, 2001 at 03:00:10PM +0100, Andreas Jaeger wrote:
> >
> > Jakub,
> > Bootstrap of GCC on i686-linux currently fails with the following
> > messages. We include some files twice there.
>
> Appended patch seems to cure it. Jakub must have only tested with CVS
> glibc.
Yes, I only have glibc-2.2.4 on my box.
Sorry.
It can be fixed either like you've done, or by using a different define
for skipping #includes in unwind-dw2-fde.c which would be unconditionally
defined in unwind-dw2-fde.c. Your patch is shorter...
> * unwind-dw2-fde-glibc.c: #define _Unwind_Find_FDE to itself
> before including unwind-dw2-fde.c, if we are not using the
> special code in this file.
>
> ===================================================================
> Index: unwind-dw2-fde-glibc.c
> --- unwind-dw2-fde-glibc.c 2001/12/15 11:49:18 1.1
> +++ unwind-dw2-fde-glibc.c 2001/12/15 19:07:31
> @@ -287,5 +287,6 @@ _Unwind_Find_FDE (void *pc, struct dwarf
> }
>
> #else
> +#define _Unwind_Find_FDE _Unwind_Find_FDE
> #include "unwind-dw2-fde.c"
> #endif
Jakub
next prev parent reply other threads:[~2001-12-15 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 6:27 Andreas Jaeger
2001-12-15 11:34 ` Zack Weinberg
2001-12-15 12:58 ` Jakub Jelinek [this message]
2001-12-15 15:25 ` Andreas Jaeger
2001-12-15 17:30 ` Richard Henderson
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=20011215152216.Z4087@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.com \
/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).