I was wondering if anyone knew if there was any rationale behind the behavior of pike -x module with respect to environment variables. The current behavior is for any environment variables that were in effect for the original build process to take precedent over any in the current environment. This means that it's not possible to use CPPFLAGS and the like to help configure find new libraries and headers. Obviously, that's rather inconvenient. Shouldn't it be the other way around? Maybe the behavior should be more sophisticated (ie combine them)? Any thoughts?
Bill