public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35707] Search /usr/local/include and /usr/include for .mod files
Date: Mon, 18 Aug 2008 20:57:00 -0000 [thread overview]
Message-ID: <20080818205606.13590.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35707-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from dfranke at gcc dot gnu dot org 2008-08-18 20:56 -------
Reminder: libbackend.a(cpp_include_defaults) seems to be the place where
standard include paths for targets are available -- including, but not limited
to, /usr/include.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35707
next prev parent reply other threads:[~2008-08-18 20:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 14:18 [Bug fortran/35707] New: " burnus at gcc dot gnu dot org
2008-03-28 23:20 ` [Bug fortran/35707] " dfranke at gcc dot gnu dot org
2008-04-06 0:21 ` dfranke at gcc dot gnu dot org
2008-05-08 18:19 ` jkrahn at nc dot rr dot com
2008-05-14 10:48 ` fxcoudert at gcc dot gnu dot org
2008-08-18 20:57 ` dfranke at gcc dot gnu dot org [this message]
2008-12-07 19:39 ` dfranke at gcc dot gnu dot org
2008-12-08 11:35 ` burnus at gcc dot gnu dot org
2008-12-08 12:52 ` dfranke at gcc dot gnu dot org
2008-12-08 14:26 ` mikael at gcc dot gnu dot org
2009-01-03 23:26 ` dfranke at gcc dot gnu dot org
2009-03-28 15:46 ` fxcoudert at gcc dot gnu dot org
2010-05-02 14:03 ` dfranke at gcc dot gnu dot org
2010-05-02 14:32 ` burnus at gcc dot gnu dot org
2010-05-09 19:41 ` dfranke at gcc dot gnu dot org
[not found] <bug-35707-4@http.gcc.gnu.org/bugzilla/>
2013-06-20 10:22 ` dominiq at lps dot ens.fr
2013-06-20 10:29 ` burnus at gcc dot gnu.org
2013-06-20 14:27 ` dominiq at lps dot ens.fr
2015-10-10 12:30 ` dominiq at lps dot ens.fr
2015-10-10 12:30 ` dominiq at lps dot ens.fr
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=20080818205606.13590.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).