And also we might need to consider this situation and change build scripts permantently to cater to this situation. ( i.e. changing from --enable-rampart to --with-rampart). Even if we don't change it, we should at least check whether openssl is present so that the user gets the signal before actually compiling the rampart module.
if test -d '/usr/include/openssl'; then
AC_MSG_NOTICE([openssl present yes])
else
AC_MSG_ERROR(could not find openssl stop)
fi
-Nabeel
On 11/12/06,
Dinesh Premalal <[EMAIL PROTECTED]> wrote:
"Nabeel Yoosuf" <[EMAIL PROTECTED]> writes:
> configure --with-rampart=/usr/local/ssh/include...still I am not sure which
> makefiles I need to modify.
I'm not sure weather this a correct solution. If you have time try
this one also. (Until exact solution comes :))
AFAIU openssl needs only for omxmlsec and utils in rampart.(grep -r
openssl * , in rampart/src directory) Therefore you may need to add
@OPENSSLINC@ in to INCLUDES of
omxmlsec/Makefile.am
omxmlsec/openssl/Makefile.am
util/Makefile.am
for build with apache2 , we have similar kind of approach in build
system. (I'm sure you are aware of that :))
This might be a some kind of hack to the build system. Please bare
with me.
thanks,
Dinesh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
