public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: John Dubchak <lists@johndubchak.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Compile error: 'siginfo_t' is not declared using gcc-4.8.2 on RedHat, 6.4
Date: Tue, 28 Jan 2014 18:42:00 -0000	[thread overview]
Message-ID: <CAH6eHdQ=JbZEtFTf1R1KRSqJj3pB92zTO=Kgnn4noRGqbF9q4A@mail.gmail.com> (raw)
In-Reply-To: <52E7F275.6020809@johndubchak.com>

On 28 January 2014 18:09, John Dubchak wrote:
> That's what brings me to the list, I am verifying if I have built gcc
> incorrectly or trying to determine other potential causes of this error.

It's far more likely to be user error rather than a problem with your
GCC build (although I have to wonder why you passed so many redundant
options to the GCC configure script, including specifying
--with-arch_32 at the same time as --disable-multilib).

> Also, in the preprocessed output from yesterday, I verified that siginfo_t
> is being defined:

In  that case one possibility is that you haven't closed a namespace
properly. e.g. if you #include <signal.h> inside a namespace block,
then #include <sys/wait.h> outside the block, it won't be able to find
siginfo_t, because it was declared as something like foo::siginfo_t.

Trying to debug your code from incomplete snippets is impossible.
Please reduce your code to the smallest example that reproduces the
problem, and then show us that.  If you can't reproduce the problem
with a reduced example, examine what's different between it and your
real code.

  parent reply	other threads:[~2014-01-28 18:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 21:57 John Dubchak
2014-01-27 22:20 ` Marc Glisse
2014-01-27 22:39   ` John Dubchak
2014-01-27 22:44     ` Jonathan Wakely
     [not found]       ` <52E6E3CB.3050503@johndubchak.com>
     [not found]         ` <CAH6eHdSnAaFvtopT_UsLfStWPaVqfLX8vei4OO8H=a=XC=1OLg@mail.gmail.com>
     [not found]           ` <52E6EE2E.5040909@johndubchak.com>
     [not found]             ` <CAH6eHdQ=QnbjN4VHexhbbZuOK3P4eAeYfXefcC1DqfkDxbUB5w@mail.gmail.com>
2014-01-28  0:20               ` John Dubchak
2014-01-28  1:51                 ` Jonathan Wakely
2014-01-28 18:10                   ` John Dubchak
2014-01-28 18:22                     ` John Dubchak
2014-01-28 18:47                       ` Jonathan Wakely
2014-01-28 18:42                     ` Jonathan Wakely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-27 21:57 John Dubchak

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='CAH6eHdQ=JbZEtFTf1R1KRSqJj3pB92zTO=Kgnn4noRGqbF9q4A@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=lists@johndubchak.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).