From: Masaki Muranaka <monaka@monami-software.com>
To: Nick Clifton <nickc@redhat.com>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org,
Thiemo Seufer <ths@networkno.de>
Subject: Re: Can't build mips-elf-run on OSX
Date: Fri, 08 Jan 2010 00:18:00 -0000 [thread overview]
Message-ID: <49770B89-E933-4802-B70B-A286187EF7F6@monami-software.com> (raw)
In-Reply-To: <4B460DD1.8080209@redhat.com>
Hello Nick,
Thanks for your comment. I figured out after sending that mail, so I already sent a patch to gdb-patches ML.
As you say, this issue is caused by sim/mips.
Thanks,
On 2010/01/08, at 1:37, Nick Clifton wrote:
> Hi Masaki,
>
>> It is required config.h by bfd/sysdep.h. This should be bfd/config.h.
>> But gcc (at least apple's genuine build) includes sim/mips/config.h.
>> So definitions in bfd/config.h like HAVE_DECL_STPCPY is not defined.
>
> This sounds like a problem with the configure script in the sim/mips directory - presumably it should be including a check of the stpcpy function.
>
>> To begin with, sim/mips/interp.c needs bfd/sysdep.h? I could built interp.c successfully without bfd/sysdep.h on my environment.
>
> Me too - so it would appear to be unnecessary. Please note however that I cannot approved such a change - you need a GDB maintainer for that. Thiemo is listed as the sim/mips maintainer...
>
> Cheers
> Nick
>
>
prev parent reply other threads:[~2010-01-08 0:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 11:28 Masaki Muranaka
2010-01-07 0:09 ` [patch] " Masaki Muranaka
2010-01-18 0:41 ` [ping] " Masaki Muranaka
2010-01-18 3:27 ` Joel Brobecker
2010-01-18 4:14 ` Masaki Muranaka
2010-01-18 4:17 ` Joel Brobecker
2010-01-07 16:43 ` Nick Clifton
2010-01-08 0:18 ` Masaki Muranaka [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=49770B89-E933-4802-B70B-A286187EF7F6@monami-software.com \
--to=monaka@monami-software.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.com \
--cc=ths@networkno.de \
/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