------- You are receiving this mail because: ------- You are the QA contact for the bug.
http://bugs.exim.org/show_bug.cgi?id=139 --- Comment #38 from Phil Pennock <[email protected]> 2011-01-14 04:57:28 --- Comments sought upon two commits in http://git.exim.org/users/pdp/exim.git : Avoid the GNU-specific "export" make(1) directive. Build with BSD Make once more. http://git.exim.org/users/pdp/exim.git/commit/5065f9e716d9e2441099ca431a6ffe7436812539 http://git.exim.org/users/pdp/exim.git/commit/52f3d00bdede5990dab7d44165d18683a08c1bab Together, they restructure things so that the build-*/src/lookups/Makefile is generated using the existing version and a new script, which inserts build rules. This avoids portability issues of GNU ifdef vs BSD .ifdef in make(1) rules. Downside is that new modules also need a one word addition to the shell script to be eligible for building. I've defined the new variable CFLAGS_DYNAMIC which is exported down, which should contain the flags for building .so code on your platform. FreeBSD/amd64 requires -fPIC in addition to the hardcoded assumed flags that were previously present. These patches just leave the definition of this variable up to EDITME, but it's an obvious candidate for going into the OS/Makefile-* fragments. I'm tempted to then adjust the buildconfig (or the new script) so that if a lookup is defined as 2 but CFLAGS_DYNAMIC is unset then error out. Thoughts? -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
