From: Honggyu Kim <hong.gyu.kim@lge.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] BFD: Fix unmatched #ifndef and #endif
Date: Sun, 29 May 2016 08:01:00 -0000 [thread overview]
Message-ID: <20160529080220.GA11688@kvt> (raw)
In-Reply-To: <m2mvn9e2zx.fsf@linux-m68k.org>
On Sun, May 29, 2016 at 09:29:22AM +0200, Andreas Schwab wrote:
> Honggyu Kim <hong.gyu.kim@lge.com> writes:
>
> > bfd/bfd-in.h has '#ifndef __BFD_H_SEEN__' statement at the beginning of
> > the header file but do not have '#endif' at the end.
>
> It is closed in bfd-in2.h, which is generated from bfd-in.h.
>
> Andreas.
>
Yes, you're right. I didn't know that bfd-in.h just generates
bfd-in2.h. But I had a compilation problem so somehow thought that
bfd-in.h could be a problem. I posted the issue on the link below:
https://sourceware.org/bugzilla/show_bug.cgi?id=20106
Do you mind if I ask you to check the issue? I think that gdb has to
be normally compiled in any other build environment.
Please correct me if I'm wrong.
Thanks,
Honggyu
prev parent reply other threads:[~2016-05-29 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 1:28 Honggyu Kim
2016-05-29 7:29 ` Andreas Schwab
2016-05-29 8:01 ` Honggyu Kim [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=20160529080220.GA11688@kvt \
--to=hong.gyu.kim@lge.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.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