<div dir="ltr">Hum,<div><br></div><div>This fact didn't come to my mind. It is strange...</div><div>If <span style="font-family:arial,sans-serif;font-size:13px">stdint.h is not include when compiling with mingw on windows 32bits, where is </span><span style="font-family:arial,sans-serif;font-size:13px">int64_t </span><span style="font-family:arial,sans-serif;font-size:13px">defined</span><span style="font-family:arial,sans-serif;font-size:13px">?</span></div>
</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div>--</div>Patrik Dufresne<div><br></div></div></div>
<br><br><div class="gmail_quote">On Mon, Sep 9, 2013 at 2:27 PM, Ted Ralphs <span dir="ltr"><<a href="mailto:ted@lehigh.edu" target="_blank">ted@lehigh.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">OK, but I don't understand why you need to include stdint.h when compiling with 32-bit MINGW. This is not the case when you build on Windows. That's the reason why __MINGW64__ is used there.<span class="HOEnZb"><font color="#888888"><div>
<br>
</div><div>Ted</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 9, 2013 at 2:15 PM, Patrik Dufresne <span dir="ltr"><<a href="mailto:ikus060@gmail.com" target="_blank">ikus060@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Ted,<div><br></div><div>Just to clarify, I'm the one who report the bug. Replacing <span style="font-family:arial,sans-serif;font-size:13px">__MINGW64__ by </span><span style="font-family:arial,sans-serif;font-size:13px">__MINGW32__ is working as expected ans seams to be the long-term solution. </span><span style="font-family:arial,sans-serif;font-size:13px">__MINGW32__ and </span><span style="font-family:arial,sans-serif;font-size:13px">__MINGW64__ is defined by the ming-w64 compiler when the target is x86_64. </span><span style="font-family:arial,sans-serif;font-size:13px">__MINGW32__ is defined by the ming-w64 and mingw32 compilers. As I understand, </span><span style="font-family:arial,sans-serif;font-size:13px">__MINGW32__ should be used whenever the code is specific for mingw whatever it's 32 or 64 bits. </span><span style="font-family:arial,sans-serif;font-size:13px">__MINGW64__ should be used only when the code is not the same for a 64bits target.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">In any case, if you compile for 32bits target, you need to include </span><span style="font-family:arial,sans-serif;font-size:13px"><stdint.h> either by removing the </span><span style="font-family:arial,sans-serif;font-size:13px">#ifdef </span><span style="font-family:arial,sans-serif;font-size:13px">#endif as suggest in the bug or by replacing </span><span style="font-family:arial,sans-serif;font-size:13px">__MINGW64__ by </span><span style="font-family:arial,sans-serif;font-size:13px">__MINGW32__.</span></div>
<div><br></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div>--</div>Patrik Dufresne<div><br></div></div></div><div><div>
<br><br><div class="gmail_quote">On Mon, Sep 9, 2013 at 2:05 PM, Ted Ralphs <span dir="ltr"><<a href="mailto:ted@lehigh.edu" target="_blank">ted@lehigh.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Mon, Sep 9, 2013 at 1:45 PM, Patrik Dufresne <span dir="ltr"><<a href="mailto:ikus060@gmail.com" target="_blank">ikus060@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Ted,<br><br>Stefan (see <a href="https://projects.coin-or.org/BuildTools/ticket/103" target="_blank">https://projects.coin-or.org/BuildTools/ticket/103</a>) suggests to remove <span style="font-family:arial,sans-serif;font-size:13px">#ifdef __MINGW64__. </span></div>
</blockquote><div><br></div></div><div>That's not really a long-term solution, though---just to see if it works. In the long-term, we need to have a #define there or stdint.h will get included for other compilers, which it shouldn't.</div>
<div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">I ended up replacing it by </span><span style="font-family:arial,sans-serif;font-size:13px">#ifdef __MINGW32__ to have the same code base work for linux and windows 32bits and 64 bits. </span></div>
</blockquote><div><br></div></div><div>Well, this is the problem then I guess. It didn't work with __MINGW64__? The reporter of the bug said that what is not working is building MinGW 32-bit from 64-bit Linux. If both are 64-bit, it worked for him. So now I'm a little confused about exactly what problem you're having. Did you try with unmodified code first?</div>
<span><font color="#888888">
<div><br></div><div>Ted</div><div>-- <br></div></font></span></div><div>Dr. Ted Ralphs<br>Associate Professor, Lehigh University<br><a href="tel:%28610%29%20628-1280" value="+16106281280" target="_blank">(610) 628-1280</a><br>
ted 'at' lehigh 'dot' edu<br><a href="http://coral.ie.lehigh.edu/~ted" target="_blank">coral.ie.lehigh.edu/~ted</a><br>
</div></div></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Dr. Ted Ralphs<br>Associate Professor, Lehigh University<br><a href="tel:%28610%29%20628-1280" value="+16106281280" target="_blank">(610) 628-1280</a><br>ted 'at' lehigh 'dot' edu<br>
<a href="http://coral.ie.lehigh.edu/~ted" target="_blank">coral.ie.lehigh.edu/~ted</a><br>
</div>
</div></div></blockquote></div><br></div>