Title: Are these Openssl path correct?
Post by: happytommy on March 15, 2004, 06:40:17 PM
Post by: happytommy on March 15, 2004, 06:40:17 PM
I found these in netqmail source.
In update_tmprsadh.sh, I see: export PATH="$PATH:/usr/local/bin/ssl"
Also, in Makefile-cert.mk: PATH=$$PATH:/usr/local/ssl/bin
Also in Makefile, I see: -L/usr/local/ssl/lib -lssl -lcrypto
But in FreeBSD, these are not where the default openssl bin and lib directories reside.
Are these done on purpose or the TLS patch would work with incorrect path on compile anyway? In Linux, these are the default path for openssl.
In update_tmprsadh.sh, I see: export PATH="$PATH:/usr/local/bin/ssl"
Also, in Makefile-cert.mk: PATH=$$PATH:/usr/local/ssl/bin
Also in Makefile, I see: -L/usr/local/ssl/lib -lssl -lcrypto
But in FreeBSD, these are not where the default openssl bin and lib directories reside.
Are these done on purpose or the TLS patch would work with incorrect path on compile anyway? In Linux, these are the default path for openssl.
Title: Re: Are these Openssl path correct?
Post by: matt on March 15, 2004, 10:12:10 PM
Post by: matt on March 15, 2004, 10:12:10 PM
| happytommy |
I found these in netqmail source. In update_tmprsadh.sh, I see: export PATH="$PATH:/usr/local/bin/ssl" Also, in Makefile-cert.mk: PATH=$$PATH:/usr/local/ssl/bin Also in Makefile, I see: -L/usr/local/ssl/lib -lssl -lcrypto But in FreeBSD, these are not where the default openssl bin and lib directories reside. Are these done on purpose or the TLS patch would work with incorrect path on compile anyway? In Linux, these are the default path for openssl. |
Very observant.
When toaster_setup builds net-qmail, it first applies all the patches (unaltered). After the patches are applied, I rewrite several of the config files with the correct values. That's how it can compile correctly. This also lets me very easily compile net-qmail, with the same patches, on several platforms.Matt