<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br></span>
Why is it "uncommitted" and not a part of clang source ?<br>
<br></blockquote><div><br></div><div>Because it hasn't been reviewed.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What does supporting mingw-64 have to do with the hardcoded path c:\mingw ?<br>
<br></blockquote><div><br></div><div>Clang driver has no official support for mingw. Just a bunch of hardcoded paths in the current driver. They break whenever new version of mingw is released as version numbers are hardcoded as well. They also don't work for mingw-w64 which as far as I know is more active than the original mingw project.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I do not understand how one obtains a patch from the link given, how one applies the patch, and to what the patch is supposed to be applied ( but I assume the patch is applied to the clang source somewhere ).<br>
<br></blockquote><div><br></div><div>Download raw diff will give you a patch file. You apply it to your local clang directory.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
<br>
2015-06-26 0:13 GMT+03:00 Edward Diener<br>
<<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a><br></span>
<mailto:<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a>>>:<span class=""><br>
<br>
On 6/25/2015 2:13 PM, Yaron Keren wrote:<br>
<br>
See <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D5268&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=CnzuN65ENJ1H9py9XLiRvC_UQz6u3oG6GUNn7_wosSM&m=dNG3HyoQulGecFyfZq24HIDVGy-_A5H4qJp4V__relo&s=3WB_bki2U9CTir99F85AJMt8_X9chUNsZXHHTVETX7Y&e=" rel="noreferrer" target="_blank">http://reviews.llvm.org/D5268</a><br></span>
<<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D5268&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=CnzuN65ENJ1H9py9XLiRvC_UQz6u3oG6GUNn7_wosSM&m=-ZW8tznEmhb5NHese2XpJkBMuo2l_Omp4pNY90r31gU&s=H5rNcz_aIhE0PghyOY7-YGlv69ay3I3K9Ce6FABMqLI&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D5268&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=CnzuN65ENJ1H9py9XLiRvC_UQz6u3oG6GUNn7_wosSM&m=-ZW8tznEmhb5NHese2XpJkBMuo2l_Omp4pNY90r31gU&s=H5rNcz_aIhE0PghyOY7-YGlv69ay3I3K9Ce6FABMqLI&e=</a>><span class=""><br>
<<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D5268&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=CnzuN65ENJ1H9py9XLiRvC_UQz6u3oG6GUNn7_wosSM&m=YgSrUuiAhPt76cF_h_LXb8Mg84W8p9nMvUiL3koHKP4&s=aW_6t6KDGfo5hO6NiTn5Hy9afNhzwfkX-BZHT9PtXmk&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D5268&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=CnzuN65ENJ1H9py9XLiRvC_UQz6u3oG6GUNn7_wosSM&m=YgSrUuiAhPt76cF_h_LXb8Mg84W8p9nMvUiL3koHKP4&s=aW_6t6KDGfo5hO6NiTn5Hy9afNhzwfkX-BZHT9PtXmk&e=</a>><br>
<br>
<br>
I don't understand what the above link means, or how it is connected<br>
to my suggestions below.<br>
<br>
<br>
<br>
<br>
2015-06-25 10:46 GMT+03:00 Edward Diener<br>
<<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a><br>
<mailto:<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a>><br></span>
<mailto:<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a><div><div class="h5"><br>
<mailto:<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a>>>>:<br>
<br>
For either the latest clang built from souce on Windows or<br>
a binary<br>
distribution of clang on Windows it appears that clang<br>
expects the<br>
supporting gcc include files and lib files to be in the<br>
hardcoded<br>
directory:<br>
<br>
c:\mingw<br>
<br>
and follow the mingw directory structure.<br>
<br>
1) Can this please be changed in the future so that some<br>
environment<br>
variable ( maybe CLANG_GCC ) can be set to the gcc installation<br>
rather than use a hardcoded path ?<br>
<br>
2) Can clang be updated to support the mingw-64 directory<br>
structure<br>
and not just the mingw directory structure ? The mingw-64<br>
distros<br>
seem now to be the preferred gcc distributions on Windows and<br>
support the latest versions of gcc.<br>
<br>
Do I need to make these suggestions on the clang bug<br>
tracker for the<br>
suggestions to be seriously considered ?<br>
<br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br></div></div>
<mailto:<a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a>><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><span class=""><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
</div></div></blockquote></div><br></div></div>