<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>Jay,</div>
<div>my initial compile issue manifested by using the win32- script, but I did the divide-and-conquer compiliations in msys with the same results. It shouldn't make any difference (and didn't to me), becuase the win32-packager script actually executes the shell commands in a msys bash shell, so it's the same basic setup either way.
</div></blockquote><div><br>Ok well I think I may have figured it out. In the configure step can you take out --cpu=k8 and then retry? That seems to be what is causing the issues for me. I think this flag should not be in the script because not everyone is running an AMD processor. I am using an Intel Pentium M and a Pentium D.
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>FYI - there are still some minor tweeks needed with the win32-packager script, so be warned that a "from scratch" setup isn't entirely hands-off just yet, but it's not doing anything wrong AFAIK, it just "drops out" when it can't figure out what to do next, which I believe is the right thing to do.
</div></blockquote></div><br>I agree that it should drop out when something unexpected happens. <br>