--- Comment #7 from lennart dot borgman at gmail dot com 2009-07-03 00:35
---
I think I found an answer to my last question here:
http://www.mingw.org/wiki/IncludePathHOWTO
Now I only need to understand how to parse that output...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=
--- Comment #6 from lennart dot borgman at gmail dot com 2009-07-02 18:34
---
Thanks, I see. How can one then figure out the include path that a user has?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40624
--- Comment #5 from pinskia at gcc dot gnu dot org 2009-07-02 18:32 ---
Because the FSF does not supply the binaries you are using so it is not a bug
with GCC rather than the way it was configured. when configuring with
--prefix=/mingw, it have to mean C:/mingw. Also GCC binaries are r
--- Comment #4 from lennart dot borgman at gmail dot com 2009-07-02 18:31
---
Ah, sorry, I did not see your comment. Could you advice how the MinGW team
should configure the compilation?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40624
--- Comment #3 from lennart dot borgman at gmail dot com 2009-07-02 18:29
---
pinskia, please explain why you marked this bug as invalid!
--
lennart dot borgman at gmail dot com changed:
What|Removed |Added
--- Comment #2 from pinskia at gcc dot gnu dot org 2009-07-02 18:27 ---
Since the output of gcc -v depends on how GCC was configured, this is not a bug
with GCC and really a bug with the way mingw's gcc was configured.
--
pinskia at gcc dot gnu dot org changed:
What|R
