public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: christian.bruel@st.com, gcc-patches@gcc.gnu.org, antonb@au1.ibm.com
Subject: Re: [PATCH]. Fix HAVE_SYS_SDT_H for cross-compilation
Date: Thu, 22 Aug 2013 18:39:00 -0000	[thread overview]
Message-ID: <1377195633.17827.6.camel@oc8801110288.ibm.com> (raw)
In-Reply-To: <20130822174700.GE1814@tucnak.redhat.com>

On Thu, 2013-08-22 at 19:47 +0200, Jakub Jelinek wrote:
> On Thu, Aug 22, 2013 at 09:39:48AM -0500, Bill Schmidt wrote:
> > Hi Christian and Jakub,
> > 
> > I'm curious whether there was ever any resolution for:
> > http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01124.html.
> 
> The last mail I remember didn't make any sense:
> #include "tconfig.h"
> 
> that includes it:
> 
> #ifndef GCC_TCONFIG_H
> #define GCC_TCONFIG_H
> #ifndef USED_FOR_TARGET
> # define USED_FOR_TARGET
> #endif
> #include "auto-host.h"
> 
> in which there is :
> 
> #ifndef USED_FOR_TARGET
> #define HAVE_SYS_SDT_H 1
> #endif
> 
> That means USED_FOR_TARGET is defined and thus HAVE_SYS_SDT_H is never
> defined, which is not desirable.
> 
> 	Jakub
> 

Yes, that doesn't seem right at all.  OK, thanks.  I'll stick this on a
list as a low-priority item to fix one of these days.

Thanks,
Bill

  reply	other threads:[~2013-08-22 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 14:40 Bill Schmidt
2013-08-22 17:51 ` Jakub Jelinek
2013-08-22 18:39   ` Bill Schmidt [this message]
2013-08-29  8:38   ` Christian Bruel
  -- strict thread matches above, loose matches on Subject: below --
2012-12-18 14:42 Christian Bruel
2012-12-18 14:48 ` Jakub Jelinek
2012-12-18 15:00   ` Christian Bruel

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=1377195633.17827.6.camel@oc8801110288.ibm.com \
    --to=wschmidt@linux.vnet.ibm.com \
    --cc=antonb@au1.ibm.com \
    --cc=christian.bruel@st.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).