[ITK-dev] Problems with Change in itkStaticConstMacro

[Bradly Lowekamp]

Gcc 4.2 runs into the same ITK bug with explicit instantiation too.

> On Jan 21, 2016, at 3:35 PM, Matthew McCormick (thewtex) <matt at mmmccormick.com> wrote:
> 
> On Thu, Jan 21, 2016 at 3:27 PM, Bradly Lowekamp <blowekamp at mail.nih.gov> wrote:
>> It’s certainly would be great if I could rely on using gcc 4.8+ for building
>> the distributions for SimpleITK. But my understanding for several situations
>> 4.1 is still essentially required.
> 
> What are the situations?  GCC 4.1 is not required by PEP 513.

Anaconda Python 2.7, OSX Python.org <http://python.org/> distribution and OSX system, need apple’s gcc 4.2

> 
> 
>> Your blog post solution for static linking in un-accetable as I don’t want
>> to use a GPL license. Along with static linking not being recommended with
>> PEP 513, and lastly it can cause conflicts when used in a loaded module with
>> an older libc version.
> 
> My blog post does not say static linking is required or the GPL is required.

"Statically linking libstdc++ <https://github.com/thewtex/CastXMLSuperbuild/blob/1c938cdf0c4a1fc295b968d2b89765b1f8abc370/CMakeLists.txt#L105-L108> avoids version compatibility issues.”

Statically, linking an LGPL library such as libstdc++ is “messy”. 

> 
> 
>> PEP 513 clearly says:
>> 
>> GCC <= 4.2.0
> 
> This excludes GCC 4.1.

4.1 <= 4.2, so it’s included.

> 
> 
> Matt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/insight-developers/attachments/20160121/57b6e8a9/attachment.html>