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
Well, if the Pike binary was compiled with some special flags, it might be necessary to compile modules with the same flags for them to be compatible (think different ABIs like 32/64 bit for example). Combining flags would probably be best, but it's nontrivial to do "right"...
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2004-07-29 21:03: Subject: external module building and environment
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
/ Brevbäraren
pike-devel@lists.lysator.liu.se
-
Bill Welliver -
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum