On Tue, Nov 20, 2007 at 02:36:11AM -0800, Arvind Srinivasan wrote: > When Apache 2.2.6 was integrated, one of the changes made to the Apache2 > (and its modules) build was to remove the dependence on having Apache2 > installed on the machine. So now, modperl uses apxs from the proto > directory of the build as opposed to expecting apxs to be in > /usr/apache2/2.2/bin/apxs.The code review request/diffs were posted here > and on webstack:
That's fine; I just didn't see any discussion on sfwnv-discuss about it, and am not subscribed to webstack-discuss, so I didn't see that. My concern is that any RPATHs embedded in the modules could be specific to the workspace they were built in. I took a look at the build 78 mod_perl.so, and it doesn't seem to link against any apache libraries, so perhaps this isn't a problem, or at least isn't a problem yet. But using apxs to pass -I and -L flags that point to the build workspace is great. Danek
