Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Since these are fairly standard locations, what happens
if you just
./configure --with-openssl
without any extra paths? If that doesn't work, try just giving
ssl's prefix (no include)
./configure --with-openssl=/usr
gcc -DHAVE_CONFIG_H -I, -I, -I../include -I../include -I../include -I/usr/include -g -02 -Wall -c `test -f rfc2617.c || echo './'`rfc2617.c
In file included from rfc2617.c:52:
../include/md5.h:18:2: #error Cannot find OpenSSL headers
Then it gives some other md5 related errors......
I notice this part of the statement changes based on my --with-openssl=
gcc -DHAVE................. -I/usr/include
if I put --with-openssl=/usr/include/openssl
The line above becomes:
-I/usr/include/openssl/include
if I put --with-openssl=/foo
The line becomes -I/fo/include
so it is alway adding include to the end of the path for some reason.....I think that's what the problem is anyways.....but I can't figure out how to fix it
I fixed it, I should have tried this first.
In between each attempt, I was running make clean.
I decided just to deete the squid directory and extract it from the tarball again, ran configure with just --enable-ssl and it worked like a charm....I gues my source tree was foobar. Thanks for your help....
hi there... i also have a question about compiling squid... i posted it a few days ago but i've had no luck getting a reply, and i was wondering if perhaps you guys could help me... i think you guys know a lot about this... basically, i'm just trying to find-out how to compile squid on slackware 9.1 using the compiler from slackware 8.1... here's the thread i started:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.