public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/35619] [4.3/4.4 Regression] fixed includes not being found if building in src dir
Date: Tue, 04 Nov 2008 00:42:00 -0000 [thread overview]
Message-ID: <20081104004051.26448.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35619-13037@http.gcc.gnu.org/bugzilla/>
------- Comment #24 from pinskia at gcc dot gnu dot org 2008-11-04 00:40 -------
*** Bug 37925 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kgjang at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35619
next prev parent reply other threads:[~2008-11-04 0:42 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 21:57 [Bug fortran/35619] New: gcc-4.3.0 build fails in gfortran section centos-4.6 bill at cse dot ucdavis dot edu
2008-03-17 22:01 ` [Bug target/35619] " pinskia at gcc dot gnu dot org
2008-03-17 22:05 ` bill at cse dot ucdavis dot edu
2008-03-17 22:07 ` bill at cse dot ucdavis dot edu
2008-03-17 22:09 ` pinskia at gcc dot gnu dot org
2008-03-17 22:14 ` bill at cse dot ucdavis dot edu
2008-03-17 22:59 ` pinskia at gcc dot gnu dot org
2008-03-17 23:44 ` bill at cse dot ucdavis dot edu
2008-03-18 0:04 ` bill at cse dot ucdavis dot edu
2008-03-19 20:39 ` bill at cse dot ucdavis dot edu
2008-03-22 21:58 ` bill at cse dot ucdavis dot edu
2008-03-22 22:01 ` bill at cse dot ucdavis dot edu
2008-03-22 22:02 ` bill at cse dot ucdavis dot edu
2008-03-22 22:09 ` pinskia at gcc dot gnu dot org
2008-03-23 0:39 ` bill at cse dot ucdavis dot edu
2008-04-21 7:19 ` ubizjak at gmail dot com
2008-05-28 1:14 ` [Bug bootstrap/35619] [4.3/4.4 Regression] fixed includes not being found if building in src dir pinskia at gcc dot gnu dot org
2008-05-28 1:14 ` pinskia at gcc dot gnu dot org
2008-05-28 1:16 ` pinskia at gcc dot gnu dot org
2008-05-28 1:16 ` pinskia at gcc dot gnu dot org
2008-06-06 15:05 ` rguenth at gcc dot gnu dot org
2008-06-13 21:41 ` mmitchel at gcc dot gnu dot org
2008-06-25 11:58 ` rguenth at gcc dot gnu dot org
2008-07-26 21:24 ` pinskia at gcc dot gnu dot org
2008-08-27 22:07 ` jsm28 at gcc dot gnu dot org
2008-09-17 19:09 ` pinskia at gcc dot gnu dot org
2008-11-04 0:42 ` pinskia at gcc dot gnu dot org [this message]
2009-01-24 10:23 ` rguenth at gcc dot gnu dot org
2009-05-20 23:42 ` [Bug bootstrap/35619] [4.3/4.4/4.5 " pinskia at gcc dot gnu dot org
2009-05-21 20:33 ` fxcoudert at gcc dot gnu dot org
2009-06-26 3:04 ` pinskia at gcc dot gnu dot org
2009-08-04 12:39 ` rguenth at gcc dot gnu dot org
2009-09-15 20:16 ` pinskia at gcc dot gnu dot org
2009-09-15 20:16 ` pinskia at gcc dot gnu dot org
2009-09-16 17:47 ` rwild at gcc dot gnu dot org
2009-09-19 8:30 ` rwild at gcc dot gnu dot org
2009-09-19 8:33 ` [Bug bootstrap/35619] [4.3/4.4 " rwild at gcc dot gnu dot org
2010-05-22 18:26 ` rguenth at gcc dot gnu dot org
[not found] <bug-35619-4@http.gcc.gnu.org/bugzilla/>
2011-03-28 0:37 ` karl at freefriends dot org
2011-06-27 13:29 ` rguenth at gcc dot gnu.org
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=20081104004051.26448.qmail@sourceware.org \
--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).