public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rrr6399 at futuretek dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/12611] Gcc doesn't handle SGI's modularized compiler setup
Date: Thu, 13 Nov 2003 01:57:00 -0000	[thread overview]
Message-ID: <20031113015713.17791.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031014025253.12611.rrr6399@futuretek.com>


------- Additional Comments From rrr6399 at futuretek dot com  2003-11-13 01:57 -------

(In reply to comment #10)

> I think I need some more details on how to appropriate way to modify 
> cppdefault.c suggested by:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12611#c5
> 
> I'm not sure what to put in the STANDARD_INCLUDE_DIR macro.

I wanted to clarify this more. I actually need to specify both 
/usr/include and /opt/MIPSpro/74/usr/include in this macro (or some
related macro). I doubt its going to like a space delimitted path, but I could
be wrong. What is the best approach to include both of these paths?


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|3.3.1                       |3.3.2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12611


  parent reply	other threads:[~2003-11-13  1:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14  2:52 [Bug bootstrap/12611] New: " rrr6399 at futuretek dot com
2003-10-14  3:08 ` [Bug bootstrap/12611] " rrr6399 at futuretek dot com
2003-10-14  3:37 ` pinskia at gcc dot gnu dot org
2003-10-14  4:46 ` rrr6399 at futuretek dot com
2003-10-14  4:49 ` pinskia at gcc dot gnu dot org
2003-10-22  6:06 ` wilson at specifixinc dot com
2003-10-24 23:27 ` dhazeghi at yahoo dot com
2003-10-25  1:39 ` pinskia at gcc dot gnu dot org
2003-10-28  2:50 ` rrr6399 at futuretek dot com
2003-10-28  2:56 ` rrr6399 at futuretek dot com
2003-11-08 21:09 ` dhazeghi at yahoo dot com
2003-11-11 14:09 ` rrr6399 at futuretek dot com
2003-11-12 21:52 ` ro at techfak dot uni-bielefeld dot de
2003-11-13  1:57 ` rrr6399 at futuretek dot com [this message]
2004-01-21 18:19 ` dhazeghi at yahoo dot com
2004-02-21 15:39 ` rrr6399 at futuretek 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=20031113015713.17791.qmail@sources.redhat.com \
    --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).