Well, given cosign hasn't been updated in 4 years, my guess would be the script isn't compatible with 10.11 or it's not compatible with newer SSL versions. I didn't realize it hadn't been touched in that long. Maybe it doesn't need to be, but in context of other open source stuff that has died over the years it makes me hesitant. That said, I also see that ssl is not enabled by default in apache2 on Mac OS. Have you enabled it? If not, it could be that the configure script can't find SSL because apache is not loading it.

https://getgrav.org/blog/mac-os-x-apache-setup-ssl

-------------------------------------------------------------------
  Yadin Flammer - Systems Administrator
  College of Arts & Architecture, Penn State University
  220 Borland Building              Office Phone: 814-865-0990
  University Park, PA 16802         Dept. Phone:  814-865-1571
  Email: [email protected]               Dept. Fax:    814-863-6227

On 9/3/16 9:42 AM, Steve Maser wrote:
That’s part of what is confusing me.   I get what you say I should get:

mockingbird:~ root# which openssl
/usr/bin/openssl
mockingbird:~ root# openssl version
OpenSSL 0.9.8zh 14 Jan 2016
mockingbird:~ root#


- Steve


On Sep 3, 2016, at 12:20 AM, Yadin Flammer <[email protected]> wrote:

Never compiled on a Mac, but your log says it can't find ssl libraries, which 
is curious since they are built in to the OS.
If you do "which openssl" is should say it's in /usr/bin/openssl
If you do "openssl version" it should say it's OpenSSL 0.9.8zh 14 Jan 2016

If not, somehow your system is damaged?

-------------------------------------------------------------------
   Yadin Flammer - Systems Administrator
   College of Arts & Architecture, Penn State University
   220 Borland Building              Office Phone: 814-865-0990
   University Park, PA 16802         Dept. Phone:  814-865-1571
   Email:
[email protected]               Dept. Fax:    814-863-6227
On 9/2/16 11:57 PM, Steve Maser wrote:
Hey all…

Simple question:   what needs to be modified to run “configure” on Mac OSX 
10.11?

when I try it with System Integrity Protection *disabled* (using xCode 7.2.1 
with the command line tools) and cosign 3.2.0, I get this:

./configure --enable-apache2=/usr/sbin/apxs --enable-krb --with-gss
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... i686-apple-darwin15.6.0
checking host system type... i686-apple-darwin15.6.0
checking for inet_ntoa in -lnsl... no
checking for socket in -lsocket... no
apache 1.3 not enabled
checking for apache 2... using apxs2 as '/usr/sbin/apxs'
apache 2 filter will be built
lighttpd not enabled
checking for krb... Kerberos found at /usr
mysql not enabled
checking for gss... /usr
checking for ssl... configure: error: cannot find ssl libraries


(trying it with SIP enabled, barely got anywhere…)


I tried to search through the archives, but didn’t find anything explicit about 
this error with the ssl libraries.

Anybody have any suggestions?   And if they fixed this part, is there anything 
additional that needs modifying to make it work on 10.11?

Thanks!

- Steve


------------------------------------------------------------------------------
_______________________________________________
Cosign-discuss mailing list

[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

------------------------------------------------------------------------------
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to