public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cryptooctoploid at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug build/13966] Some elf tests fail with "fatal error: cstdio: No such file or directory" on trunk
Date: Thu, 19 Apr 2012 21:26:00 -0000 [thread overview]
Message-ID: <bug-13966-131-lvB7Cgljhk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13966-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13966
Octoploid <cryptooctoploid at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |INVALID
--- Comment #4 from Octoploid <cryptooctoploid at gmail dot com> 2012-04-19 21:25:37 UTC ---
(In reply to comment #3)
> On Tue, 10 Apr 2012, carlos_odonell at mentor dot com wrote:
>
> > I don't know how this worked in the past.
> >
> > Compiling a C++ application with -nostdinc is not going to work.
>
> If you don't use --with-headers - if you use your system's default kernel
> headers - then you don't get -nostdinc used, so don't see this. (And
> that also covers the case of building a cross compiler and preinstalling
> the kernel headers into its default sysroot.)
Thanks for the head-up. I just didn't know that "--with-headers=/usr/include"
is not only redundant, but also the root cause this issue.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-04-19 21:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 9:47 [Bug build/13966] New: " cryptooctoploid at gmail dot com
2012-04-10 10:14 ` [Bug build/13966] " cryptooctoploid at gmail dot com
2012-04-10 17:55 ` carlos_odonell at mentor dot com
2012-04-19 20:01 ` joseph at codesourcery dot com
2012-04-19 21:26 ` cryptooctoploid at gmail dot com [this message]
2012-04-20 7:47 ` schwab@linux-m68k.org
2012-04-20 10:31 ` cryptooctoploid at gmail dot com
2012-04-20 12:17 ` schwab@linux-m68k.org
2012-04-20 12:23 ` schwab@linux-m68k.org
2012-04-20 12:28 ` cryptooctoploid at gmail dot com
2012-05-17 14:10 ` carlos_odonell at mentor dot com
2012-06-27 22:33 ` jsm28 at gcc dot gnu.org
2012-07-12 12:39 ` wbrana at gmail dot com
2012-09-02 13:33 ` allan at archlinux dot org
2012-09-02 17:09 ` cryptooctoploid at gmail dot com
2012-09-02 22:30 ` allan at archlinux dot org
2012-09-05 14:19 ` allan at archlinux dot org
2012-11-01 14:13 ` cryptooctoploid at gmail dot com
2012-11-01 14:25 ` allan at archlinux dot org
2012-11-01 14:54 ` schwab@linux-m68k.org
2012-11-01 15:53 ` cryptooctoploid at gmail dot com
2013-09-05 22:48 ` jack.carter at imgtec dot com
2013-09-06 0:31 ` joseph at codesourcery dot com
2013-09-06 9:35 ` jack.carter at imgtec dot com
2014-06-25 11:19 ` 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-13966-131-lvB7Cgljhk@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.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).