public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/15711] Endless loop building misc/bits/syscall.d in glibc 2.17
Date: Mon, 15 Jul 2013 18:04:00 -0000	[thread overview]
Message-ID: <bug-15711-131-qKPwOR1xvH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15711-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15711

--- Comment #6 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to joseph@codesourcery.com from comment #5)
> I don't see any -I options at all in the make output quoted in this bug - 
> in particular, none that would cause source tree headers to be used.  (The 
> makefile rules use $(sysincludes), presumably so that the kernel headers 
> can be found if --with-headers is used to locate them.)

Thanks, that's a good point I hadn't noticed yet.

In fact the search paths are only:
 /usr/lib/gcc/x86_64-redhat-linux/4.7.2/include
 /home/carlos/install-linux/include

Which is the system headers and the linux headers used for the build.

Given that this header doesn't need include/stdc-predef.h the best solution is
to use -ffreestanding instead of including more include directories from the
source tree.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-07-15 18:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 16:20 [Bug build/15711] New: " carlos.velasco at nimastelecom dot com
2013-07-01 17:00 ` [Bug build/15711] " joseph at codesourcery dot com
2013-07-05 11:21 ` carlos at redhat dot com
2013-07-08 11:00 ` bnelson at nelsonbe dot com
2013-07-15 17:15 ` carlos at redhat dot com
2013-07-15 17:25 ` joseph at codesourcery dot com
2013-07-15 18:04 ` carlos at redhat dot com [this message]
2013-07-16 22:03 ` carlos at redhat dot com
2013-07-16 22:05 ` carlos at redhat dot com
2014-06-13 13:25 ` fweimer at redhat dot com

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=bug-15711-131-qKPwOR1xvH@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).