[Bug c/40624] New: gcc -v does not give useful --prefix on w32

2009-07-02 Thread lennart dot borgman at gmail dot com
Product: gcc Version: 3.4.5 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: lennart dot borgman at gmail dot com http://gcc.gnu.org/bugzilla

[Bug c/40624] gcc -v does not give useful --prefix on w32

2009-07-02 Thread lennart dot borgman at gmail dot com
--- Comment #1 from lennart dot borgman at gmail dot com 2009-07-02 18:16 --- Hm, something went wrong when sending the bug report. It should have said When doing gcc -v the resulting prefix for me is --prefix=/mingw On w32 ... (the rest is correct) -- lennart dot borgman

[Bug driver/40624] gcc -v does not give useful --prefix on w32

2009-07-02 Thread lennart dot borgman at gmail dot com
--- 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

[Bug driver/40624] gcc -v does not give useful --prefix on w32

2009-07-02 Thread lennart dot borgman at gmail dot com
--- 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

[Bug driver/40624] gcc -v does not give useful --prefix on w32

2009-07-02 Thread lennart dot borgman at gmail dot com
--- 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

[Bug driver/40624] gcc -v does not give useful --prefix on w32

2009-07-02 Thread lennart dot borgman at gmail dot com
--- 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