public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mancilla at cse dot unsw.edu.au" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/48879] Compilation cannot find file asm/errno.h
Date: Thu, 05 May 2011 22:13:00 -0000 [thread overview]
Message-ID: <bug-48879-4-OmrAuWaSPO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48879-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48879
Blanca Mancilla <mancilla at cse dot unsw.edu.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c++ |bootstrap
--- Comment #5 from Blanca Mancilla <mancilla at cse dot unsw.edu.au> 2011-05-05 22:09:28 UTC ---
(In reply to comment #2)
> Shouldn't this be Component=bootstrap not c++ ?
Yes, sorry.
> I assume the linux-libc-dev package is installed? That provides asm/errno.h
Yes that is installed.
> What compiler are you using to bootstrap? If it's the standard system compiler
> it should know to look in /usr/include/x86_64-linux-gnu, if not then it's a bug
> in the Ubuntu gcc package
4.5.2, which came with the distribution.
> What is the output of "gcc -v -x c /dev/null -c" ?
Is is attached.
A bug in the Ubuntu gcc package confirms the fact that problems started after
the upgrade. Thanks for clearing things out.
Regards,
Blanca
next prev parent reply other threads:[~2011-05-05 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 5:15 [Bug c++/48879] New: " mancilla at cse dot unsw.edu.au
2011-05-05 8:50 ` [Bug c++/48879] " mancilla at cse dot unsw.edu.au
2011-05-05 9:24 ` redi at gcc dot gnu.org
2011-05-05 10:49 ` rguenth at gcc dot gnu.org
2011-05-05 22:13 ` mancilla at cse dot unsw.edu.au [this message]
2011-05-05 22:28 ` mancilla at cse dot unsw.edu.au
2011-11-15 21:48 ` [Bug bootstrap/48879] " davek at 6thstreetradio dot org
2012-07-03 16:13 ` aric999 at gmail dot com
2013-10-21 8:34 ` branko.drevensek at gmail 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-48879-4-OmrAuWaSPO@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).