Unset cflags and cxxflags before building?

[chaubold]

When building ilastik with buildem, one can run into the problem that NumPy does not compile and complains about several Python Symbols not being found for the respective architecture. It took us quite a while to find out that this was caused by some CFLAGS being set, that overwrote the default numpy settings. (found here)

Experienced this on OSX Mavericks 10.9, with CFLAGS="-march=core2" set.

Should we unset the cflags and cxxflags for building with buildem? Or at least tell the user to do so.

[stuarteberg]

Just to clarify: do you believe that CFLAGS was set by a BuildEM script? Or was it set elsewhere in your environment? Is it enough to simply check the value of $ENV{CFLAGS} in BuildEM's numpy.cmake and provide a warning/error to the user?

[chaubold]

CFLAGS was set in the bash_profile of the Mac that we encountered the error on.
So, I guess that checking and warning the user should be sufficient. But I am not sure whether this only applies to numpy, or other packages as well. It might be worth checking in BuildSupport.cmake?

[stuarteberg]

I'm also not sure if it affects other projects. Let's start by just adding a warning (or maybe an error) in numpy.cmake if $ENV{CFLAGS} is set.

[chaubold]

All right, agree!