public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rainer at emrich-ebersheim dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/41943] include search path composition is bogus
Date: Fri, 04 Dec 2009 08:24:00 -0000 [thread overview]
Message-ID: <20091204082412.13373.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41943-11564@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from rainer at emrich-ebersheim dot de 2009-12-04 08:24 -------
Subject: Re: include search path composition is bogus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ktietz at gcc dot gnu dot org schrieb:
> ------- Comment #4 from ktietz at gcc dot gnu dot org 2009-12-03 21:56 -------
> Would it be a solution (at least for -w64- targets) to remove the
> <sys-root>/mingw part and default to <sysroot>/include & <sysroot>/lib instead.
> At least for the -w64- targets there is no real need of this /mingw subfolder.
>
> Kai
>
>
I'm fine with such a solution!
Rainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAksYxxMACgkQoUhjsh59BL4zKQCfYIyhzc8De0cE7D5xjG9QCYg1
z6MAnjvLRVeV/a0bSks4jFHf0cwt27VY
=bekw
-----END PGP SIGNATURE-----
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41943
next prev parent reply other threads:[~2009-12-04 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 21:16 [Bug preprocessor/41943] New: " rainer at emrich-ebersheim dot de
2009-11-04 21:19 ` [Bug preprocessor/41943] " pinskia at gcc dot gnu dot org
2009-11-05 8:17 ` rainer at emrich-ebersheim dot de
2009-11-07 11:05 ` rainer at emrich-ebersheim dot de
2009-11-29 20:47 ` ktietz at gcc dot gnu dot org
2009-12-03 21:56 ` ktietz at gcc dot gnu dot org
2009-12-04 8:24 ` rainer at emrich-ebersheim dot de [this message]
2009-12-06 11:47 ` ktietz at gcc dot gnu dot org
2009-12-06 20:01 ` ktietz at gcc dot gnu dot org
2010-07-23 18:32 ` ktietz at gcc dot gnu dot org
2010-08-31 14:31 ` ktietz at gcc dot gnu dot 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=20091204082412.13373.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).