Ok, but where does it put the lib? It's not the root that's causing
problems, it's the middle part.
--with-ossl-root=/usr/local/ssl would be a valid prefix if the .hs are in
.../include/openssl and the .so in .../lib
"You define the openssl build options in a clear fashion, so the user built
matches Your expectations." is cr*p.
According to the INSTALL file distributed w/ 0.9.7a, the parameters are:
--prefix=DIR Install in DIR/bin, DIR/lib, DIR/include/openssl.
Configuration files used by OpenSSL will be in DIR/ssl
or the directory specified by --openssldir.
--openssldir=DIR Directory for OpenSSL files. If no prefix is specified,
the library files and binaries are also installed there.
That's what ntop's configure IS ALREADY tuned for.
Look, the dang thing is supposed to be a system library. So it's SUPPOSED
to be available via a standard gcc compile/link.
gcc -lssl file.c
That's it. That's all I have to do for a libpcap test program or whatever.
If you set --prefix=/usr or --prefix=/usr/local it works. The --openssldir
is for the configuration files, which ntop doesn't give a rat's furry behind
about.
It's only openSSL under some stupid OS/packagers that installs itself in
fried locations and expects the compile line to jump through hoops.
Handling this stuff is already 6% of the TOTAL lines in configure.in -- how
many more stupid places do we have to look? Splitting the option would
DOUBLE or TRIPLE the # of lines (I'd have to add --with-ossl-libroot and
maybe a --with-ossl-hroot).
If you don't tell us a specific place to look, we already check -- BEYOND
the usual AC_CHECK_HEADER() and AC_CHECK_LIB tests that should find it
routinely:
/usr/include
/usr/include/openssl
/usr/include/ssl
/usr/local/include
/usr/local/include/openssl
/usr/local/include/ssl
/usr/lib/libssl.so || /usr/lib/libssl.a
/usr/local/lib/libssl.so || /usr/local/lib/libssl.a
/usr/lib64/libssl.so || /usr/lib64/libssl.a
If you DO tell us where to look, we check, based off --with-ossl-root value:
./include
./include/openssl
./include/ssl
and .so || .a in:
.
./lib
./lib/openssl
WHY ISN'T THAT ENOUGH????
-----Burton
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
Of Falk Hayn
Sent: Thursday, February 27, 2003 9:35 AM
To: [EMAIL PROTECTED]
Subject: [Ntop-dev] ntop and openSSL 0.9.7: expectet directory structure
Burton,
thanks for Your discussions thread.
I downloaded the source from http://www.openssl.org and
just did a complete build from scratch.
To be near the defaults of openssl I said
./Configure hpux-gcc
Burton, You said:
my == Falk's ./configure line of
$ ./configure --with-ossl-root=/usr/local/ssl --no-create --no-recursion
and expected the files in
/usr/local/ssl/openssl/ssl.h (without include )
But: After my user built with defaults, the .h files are in
/usr/local/ssl/include/openssl
That means -in dependency of options- openssl places the files on different
platforms in different places.
possible Remedy:
1.) You have to add more places to search
---> a more global solution
2.) You define the openssl build options in a clear fashion, so the user
built matches Your expectations.
---> may prohibit the usage of some prebuilt packages.
Regards, F.
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
