<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Gcc 4.2 runs into the same ITK bug with explicit instantiation too.</div><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 21, 2016, at 3:35 PM, Matthew McCormick (thewtex) <<a href="mailto:matt@mmmccormick.com" class="">matt@mmmccormick.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Thu, Jan 21, 2016 at 3:27 PM, Bradly Lowekamp <<a href="mailto:blowekamp@mail.nih.gov" class="">blowekamp@mail.nih.gov</a>> wrote:<br class=""><blockquote type="cite" class="">It’s certainly would be great if I could rely on using gcc 4.8+ for building<br class="">the distributions for SimpleITK. But my understanding for several situations<br class="">4.1 is still essentially required.<br class=""></blockquote><br class="">What are the situations? GCC 4.1 is not required by PEP 513.<br class=""></div></div></blockquote><div><br class=""></div><div>Anaconda Python 2.7, OSX <a href="http://python.org" class="">Python.org</a> distribution and OSX system, need apple’s gcc 4.2</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><br class=""><blockquote type="cite" class="">Your blog post solution for static linking in un-accetable as I don’t want<br class="">to use a GPL license. Along with static linking not being recommended with<br class="">PEP 513, and lastly it can cause conflicts when used in a loaded module with<br class="">an older libc version.<br class=""></blockquote><br class="">My blog post does not say static linking is required or the GPL is required.<br class=""></div></div></blockquote><br class=""><div><span id="docs-internal-guid-4f41e2fa-9712-cc24-4295-3f4bd2c68b54" style="padding: 0px; margin: 0px; color: rgb(51, 51, 51); font-family: Arial, sans-serif; text-align: justify;" class=""><span style="padding: 0px; margin: 0px; text-decoration: underline; font-size: 14.666666666666666px; font-family: Arial; color: rgb(17, 85, 204); vertical-align: baseline; white-space: pre-wrap;" class="">"<a href="https://github.com/thewtex/CastXMLSuperbuild/blob/1c938cdf0c4a1fc295b968d2b89765b1f8abc370/CMakeLists.txt#L105-L108" style="padding: 0px; margin: 0px; text-decoration: none;" class="">Statically linking libstdc++</a></span><span style="padding: 0px; margin: 0px; font-size: 14.666666666666666px; font-family: Arial; color: rgb(0, 0, 0); vertical-align: baseline; white-space: pre-wrap;" class=""> avoids version compatibility issues.”</span></span></div><div><span style="padding: 0px; margin: 0px; color: rgb(51, 51, 51); font-family: Arial, sans-serif; text-align: justify;" class=""><span style="padding: 0px; margin: 0px; font-size: 14.666666666666666px; font-family: Arial; color: rgb(0, 0, 0); vertical-align: baseline; white-space: pre-wrap;" class=""><br class=""></span></span></div><div><span style="padding: 0px; margin: 0px; color: rgb(51, 51, 51); font-family: Arial, sans-serif; text-align: justify;" class=""><span style="padding: 0px; margin: 0px; font-size: 14.666666666666666px; font-family: Arial; color: rgb(0, 0, 0); vertical-align: baseline; white-space: pre-wrap;" class="">Statically, linking an LGPL library such as libstdc++ is “messy”. </span></span></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><br class=""><blockquote type="cite" class="">PEP 513 clearly says:<br class=""><br class="">GCC <= 4.2.0<br class=""></blockquote><br class="">This excludes GCC 4.1.<br class=""></div></div></blockquote><div><br class=""></div><div>4.1 <= 4.2, so it’s included.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><br class="">Matt<br class=""></div></div></blockquote></div><br class=""></body></html>