Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Finalizing fix committed for "[PATCH] sim: make sure to include strsignal prototype"
Date: Sun, 25 Mar 2012 14:03:00 -0000	[thread overview]
Message-ID: <alpine.BSF.2.00.1203250937530.31061@dair.pair.com> (raw)
In-Reply-To: <201203250414.30369.vapier@gentoo.org>

On Sun, 25 Mar 2012, Mike Frysinger wrote:
> On Saturday 24 March 2012 16:54:50 Hans-Peter Nilsson wrote:
> > On Sat, 24 Mar 2012, Mike Frysinger wrote:
> > > On Saturday 24 March 2012 06:55:28 Hans-Peter Nilsson wrote:
> > > > This patch was missing the critical include of cconfig.h so you
> > > > should still have seen warnings about implicit declarations of
> > > > strsignal when testing.
> > >
> > > as i mentioned earlier, there are no warnings for me because my glibc
> > > conforms to the 2008 POSIX spec
> >
> > I saw that, but that didn't apply
>
> yes, it did.  because as i also explained previously, string.h is getting
> implicitly included by other files.

FWIW: not so on *this* non-outdated system, a system different
from my autotester which broke.  You qualified your observation
as for mips-elf only; "the mips' sim-main.h code eventually
includes string.h for me".  Hm, I see the identical warnings
output for mips-elf as for cris-elf here.

>  i never saw a warning related to this, nor
> crashes in the sim, and i still didn't after my change regardless of the
> config.h includes.  quoting behavior that *you* see on your outdated glibc has
> really no bearing whatsoever on my build system.

The lastest quote was from a different system, one with a glibc
that didn't need _GNU_SOURCE defined for strerror when including
string.h.  But apparently one where string.h also isn't included
elsewhere for neither mips-elf nor cris-elf, still different
from yours.

JFTR.  Moving on.

brgds, H-P


  reply	other threads:[~2012-03-25 14:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  4:23 [PATCH] sim: make sure to include strsignal prototype Mike Frysinger
2012-03-23  4:35 ` Mike Frysinger
2012-03-23  5:24 ` Hans-Peter Nilsson
2012-03-23 15:43   ` Mike Frysinger
2012-03-23 22:12     ` Hans-Peter Nilsson
2012-03-23 22:43       ` Mike Frysinger
2012-03-24  5:34     ` Mike Frysinger
2012-03-24  4:12   ` Mike Frysinger
2012-03-24  5:53     ` Hans-Peter Nilsson
2012-03-24  6:12       ` Mike Frysinger
2012-03-24  6:49         ` Hans-Peter Nilsson
2012-03-24 18:18           ` Mike Frysinger
2012-03-24 10:55   ` Finalizing fix committed for "[PATCH] sim: make sure to include strsignal prototype" Hans-Peter Nilsson
2012-03-24 18:24     ` Mike Frysinger
2012-03-24 20:55       ` Hans-Peter Nilsson
2012-03-25  8:14         ` Mike Frysinger
2012-03-25 14:03           ` Hans-Peter Nilsson [this message]
2012-03-25  7:40       ` Mike Frysinger
2012-03-25  7:54         ` Mike Frysinger
2012-03-25 14:26           ` Hans-Peter Nilsson
2012-03-24  5:39 ` [PATCH] sim: make sure to include strsignal prototype Mike Frysinger

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=alpine.BSF.2.00.1203250937530.31061@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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