public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/17007] Check Scanf15 bits/syscall.h No such file
Date: Tue, 03 Jun 2014 16:41:00 -0000 [thread overview]
Message-ID: <bug-17007-131-bt7h1l7NQt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17007-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17007
--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 3 Jun 2014, naroyce at hotmail dot com wrote:
> Hmmm, that "_LIBC" definition seems to contradict with "stubs-hard.h"
> $ ../glibc/configure --prefix="/usr" --disable-profile --enable-kernel=3.8.13
> --libexecdir="${newPartition_ROOT}/usr/lib/glibc" --enable-obsolete-rpc
> --with-headers="${newPartition_ROOT}/usr/include" CFLAGS="-O3 -pipe -mfpu=neon
> -mtune=cortex-a9 -march=armv7-a -mfloat-abi=hard" CXXFLAGS="-O3 -pipe
> -mfpu=neon -mtune=cortex-a9 -march=armv7-a -mfloat-abi=hard"
> $ make
> *****
> In file included from /armv7l-unknown-linux-gnueabihf/include/gnu/stubs.h:10:0,
> from /armv7l-unknown-linux-gnueabihf/include/features.h:389,
The glibc build should never be using the installed headers; those in
include/ in the source tree should take precedence (which includes the
dummy gnu/stubs.h file in include/).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-03 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-17007-131@http.sourceware.org/bugzilla/>
2014-06-03 10:35 ` naroyce at hotmail dot com
2014-06-03 11:02 ` schwab@linux-m68k.org
2014-06-03 11:33 ` naroyce at hotmail dot com
2014-06-03 16:41 ` joseph at codesourcery dot com [this message]
2014-06-04 11:16 ` naroyce at hotmail dot com
2014-06-12 19:10 ` 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-17007-131-bt7h1l7NQt@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).