Error installing Apache from port with NSS

[edflecko]

I'm trying to install Apache 2.4 in an ezjail using the port.

I issued the following command from the jail /usr/ports/www/apache24
directory to begin:

make config-recursive install clean

and I chose to use the NSS option when installing.

The error message I eventually get is:

"configure: error: Crypto was requested but no crypto library could be
enabled; specify the location of a crypto library using --with-openssl,
--with-nss, and/or --with-commoncrypto."

I then ran: make deinstall clean for the Apache port, installed NSS from
the port, and re-ran my Apache install and I still get the same error.

I see the error message clearly says to " specify the location of a crypto
library using --with-openssl, --with-nss..." but I don't know how to do
that.

Suggestions?

Thank you,
Ed

[Polytropon]

Post by edflecko
"configure: error: Crypto was requested but no crypto library could be
enabled; specify the location of a crypto library using --with-openssl,
--with-nss, and/or --with-commoncrypto."
I then ran: make deinstall clean for the Apache port, installed NSS from
the port, and re-ran my Apache install and I still get the same error.
I see the error message clearly says to " specify the location of a crypto
library using --with-openssl, --with-nss..." but I don't know how to do
that.
Suggestions?

This is an error message primarily intended for using the
"configure" script (in the classic sense of "./configure &&
make && make install" way of installing things). Those options
will instruct "configure" how to generate the Makefile that
will control the build.

You should be able to use something like this:

# ./configure --with-nss
# make
# make install

from within the port's work directory (just check where
the configure script is).

However, the FreeBSD ports infrastructure should be the
preferred means so you do not have to do this. :-)

[edflecko]

Thank you.

Oddly, there is no "configure" file. There are Makefile, Makefile.options
and Makefile.options.desc.

Perhaps there's a Makefile option that needs to be altered?

Post by edflecko

Post by edflecko
"configure: error: Crypto was requested but no crypto library could be
enabled; specify the location of a crypto library using --with-openssl,
--with-nss, and/or --with-commoncrypto."
I then ran: make deinstall clean for the Apache port, installed NSS from
the port, and re-ran my Apache install and I still get the same error.
I see the error message clearly says to " specify the location of a

crypto

Post by edflecko
library using --with-openssl, --with-nss..." but I don't know how to do
that.
Suggestions?

This is an error message primarily intended for using the
"configure" script (in the classic sense of "./configure &&
make && make install" way of installing things). Those options
will instruct "configure" how to generate the Makefile that
will control the build.
# ./configure --with-nss
# make
# make install
from within the port's work directory (just check where
the configure script is).
However, the FreeBSD ports infrastructure should be the
preferred means so you do not have to do this. :-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

[Polytropon]

Post by edflecko
Oddly, there is no "configure" file. There are Makefile, Makefile.options
and Makefile.options.desc.

Check deeper in the port's directory. You should be able
to find it in a subdirectory after "make extract", i. e.,
when all the sources are in place. THe manual method is:

# make fetch
# make extract
# make patch

Then you can locate the "configure" script and call it with
the options. Afterwards, regular "make" (from the top of
this port's directory tree) should work.

Post by edflecko
Perhaps there's a Makefile option that needs to be altered?

The Makefiles will often be generated or altered "dynamically"
(by the "configure" step). But of course you can check if the
Makefile (which calls "configure" as one of the first steps)
can be temporarily changed to reflect the option in question,
as selecting the required option in "make configure" should
typically cause all dependencies to be considered accordingly.

Again, this is all "stuff you shouldn't do". ;-)

[edflecko]

Thank you.

Nope...there is no "configure" file at all.

:-(

Ed