From: Daniel Jacobowitz <drow@false.org>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 6.5 RTEMS patch
Date: Mon, 09 Oct 2006 19:11:00 -0000 [thread overview]
Message-ID: <20061009191056.GA22848@nevyn.them.org> (raw)
In-Reply-To: <44DCF2F0.6010504@oarcorp.com>
Sorry about dropping the ball on this again. This was about this
change:
> >> #if !HAVE_DECL_STRSTR
> >>-extern char *strstr ();
> >>+/* extern char *strstr (); */
> >> #endif
On Fri, Aug 11, 2006 at 04:13:20PM -0500, Joel Sherrill wrote:
> I just ran into a configuration tripping the need for this again. I am
> in a chroot'ed
> RH73 environment building RPMs. gcc is from the RPM gcc-2.96-113. Apparently
> strstr is a macro on this configuration. When compiling the interp.c
> file from some
> of the simulators, you get this error.
>
> ../../../gdb-6.5/bfd/sysdep.h:138:22: macro "strstr" requires 2
> arguments, but only 1 given
>
> I think this is the macro is in /usr/include/bits/string2.h causing this:
The macro itself isn't a problem. The problem is that we didn't find
the prototype for the actual function, or the macro, during configure.
I would recommend taking a look at the config.log for the gdb
subdirectory, and searching for the strstr test. There should be a
failed program logged; maybe it's not included some header that it
ought to have.
A guess: does adding ACX_HEADER_STRING to gdb/configure.ac and
regenerating configure help?
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-10-09 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 20:41 Joel Sherrill
2006-07-24 20:28 ` Daniel Jacobowitz
2006-07-24 20:40 ` Joel Sherrill
2006-08-08 18:57 ` Daniel Jacobowitz
2006-08-14 15:43 ` Joel Sherrill
2006-10-09 19:11 ` Daniel Jacobowitz [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=20061009191056.GA22848@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=joel.sherrill@oarcorp.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