<div dir="auto">As I doubt anyone is actually building for Windows besides you, I would just make a Windows build. If it crops up in any other environments, then you can cut the new full release.</div><div class="gmail_extra"><br><div class="gmail_quote">On Aug 20, 2017 1:22 PM, "Karl Kleinpaste" <<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<font face="FreeSerif">I need an opinion.<br>
<br>
I have found the problem where Windows upchucks during first-time
user module install, after refreshing crosswire. It's not a bug in
the code. It's that I have to invoke the compilers with
-fno-delete-null-pointer-<wbr>checks. The code is fine, *IF* the @#$%
compiler would stop arbitrarily "optimizing" certain checks into
oblivion.<br>
<br>
In principle, this bug should affect all builds, because both
regular and MinGW compilers on my Fedora boxes are 6.3.1, but
experientially it seems to have affected Windows builds only. Do I
put out an entire new release, 4.0.7, to be safe? Or just a
Windows release, as e.g. 4.0.6a?<br>
<br>
Comments welcome.</font><br>
</div>
<br>______________________________<wbr>_________________<br>
xiphos-devel mailing list<br>
<a href="mailto:xiphos-devel@crosswire.org">xiphos-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/xiphos-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/<wbr>mailman/listinfo/xiphos-devel</a><br>
<br></blockquote></div></div>