From: "H.J. Lu" <hjl.tools@gmail.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [RFA] fix bfd multi-arch compilation failure
Date: Wed, 18 Mar 2009 00:08:00 -0000 [thread overview]
Message-ID: <6dc9ffc80903171659t2319301ey2b78f39aa4ae1d7c@mail.gmail.com> (raw)
In-Reply-To: <005001c9a757$db6bacb0$92430610$@u-strasbg.fr>
On Tue, Mar 17, 2009 at 4:26 PM, Pierre Muller <muller@ics.u-strasbg.fr> wrote:
> Hi,
> I tried to do a compilation of
> gdb with --enable-targets=all --enable-64-bits-bfd
> on OpenSolaris 2008.11.
>
> I found two problems in bfd directory,
> related to uses of alloca without
> including <alloca.h>
>
> I added
> #include <alloca.h>
> garded by #ifdef HAVE_ALLOCA_H
> as I suppose that on some systems
> alloca is builtin and thus does not require any header.
>
>
> Is this OK to check in?
>
>
> Pierre Muller
> Pascal language support maintainer for GDB
>
>
>
> ChangeLog entry:
>
> 2009-03-18 Pierre Muller <muller@ics.u-strasbg.fr>
>
> * elf32-m68hc1x.c: Add alloca header.
> * xsym.c: Ditto.
>
>
> Index: bfd/elf32-m68hc1x.c
> ===================================================================
> RCS file: /cvs/src/src/bfd/elf32-m68hc1x.c,v
> retrieving revision 1.33
> diff -u -p -r1.33 elf32-m68hc1x.c
> --- bfd/elf32-m68hc1x.c 12 Mar 2008 08:36:59 -0000 1.33
> +++ bfd/elf32-m68hc1x.c 17 Mar 2009 23:18:58 -0000
> @@ -20,6 +20,9 @@
> Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston,
> MA 02110-1301, USA. */
>
> +#ifdef HAVE_ALLOCA_H
> +#include <alloca.h>
> +#endif
> #include "sysdep.h"
> #include "bfd.h"
> #include "bfdlink.h"
That is wrong. Please see how it is handled in elf64-hppa.c.
--
H.J.
next prev parent reply other threads:[~2009-03-17 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 23:59 Pierre Muller
2009-03-18 0:08 ` H.J. Lu [this message]
2009-03-18 11:46 ` Alan Modra
2009-03-18 13:05 ` Alan Modra
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=6dc9ffc80903171659t2319301ey2b78f39aa4ae1d7c@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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