How do I specify location of openssl headers?

39 views
Skip to first unread message

David Kirkby

unread,
Sep 1, 2012, 6:22:18 PM9/1/12
to sage-devel
I'm trying to build Sage on Solaris 10 (March 2005 edition), which has
worked many times before. But I see someone has now made it necessary
to have openssl. Well the headers are present on my system in
/usr/sfw/include/openssl, but how do I tell the Makefile where to find
them? I tried adding -I option, but that did not work.

Perhaps we can make Sage look there, as its the standard place for
OpenSSL on Solaris.

Dave

John H Palmieri

unread,
Sep 1, 2012, 8:08:44 PM9/1/12
to sage-...@googlegroups.com

First, I don't know the answer to your question: how to specify the location of these headers. However:

1. The dependency on OpenSSL should go away soon -- see trac tickets #13121 and #13385.

2. In the meantime, you can try this: from SAGE_ROOT, run "./sage -i patch" and "./sage -i http://sagemath.org/packages/optional/openssl-1.0.1c.p0.spkg". Then run "make".

3. Having Sage look in this directory on Solaris (and OpenSolaris?) sounds like a good idea. Someone who knows what they're doing should implement this.

--
John

David Kirkby

unread,
Sep 2, 2012, 7:13:57 AM9/2/12
to sage-...@googlegroups.com
On 2 September 2012 01:08, John H Palmieri <jhpalm...@gmail.com> wrote:
>
> On Saturday, September 1, 2012 3:22:21 PM UTC-7, Dr. David Kirkby wrote:
>>
>> I'm trying to build Sage on Solaris 10 (March 2005 edition), which has
>> worked many times before.

I should have said this was SPARC.
>
>
> First, I don't know the answer to your question: how to specify the location
> of these headers. However:
>
> 1. The dependency on OpenSSL should go away soon -- see trac tickets #13121
> and #13385.

Sort of good. (I'm not sure about the GPL aspect of this), but many
systems will not have this by default.

> 2. In the meantime, you can try this: from SAGE_ROOT, run "./sage -i patch"
> and "./sage -i
> http://sagemath.org/packages/optional/openssl-1.0.1c.p0.spkg". Then run
> "make".

I'll give that a go.

> 3. Having Sage look in this directory on Solaris (and OpenSolaris?) sounds
> like a good idea. Someone who knows what they're doing should implement
> this.

Really though, I think there should be a way to specify a place to
look for headers - not just for SSL, but perhaps something that could
work for any library. Some of the optional libraries that can improve
Sage (but are not Sage options) might be installed by one user without
root access.

Dave

Keshav Kini

unread,
Sep 2, 2012, 8:56:52 AM9/2/12
to sage-...@googlegroups.com
David Kirkby <david....@onetel.net> writes:
> On 2 September 2012 01:08, John H Palmieri <jhpalm...@gmail.com> wrote:
>>
>> On Saturday, September 1, 2012 3:22:21 PM UTC-7, Dr. David Kirkby wrote:
>>>
>>> I'm trying to build Sage on Solaris 10 (March 2005 edition), which has
>>> worked many times before.
>
> I should have said this was SPARC.
>>
>>
>> First, I don't know the answer to your question: how to specify the location
>> of these headers. However:
>>
>> 1. The dependency on OpenSSL should go away soon -- see trac tickets #13121
>> and #13385.
>
> Sort of good. (I'm not sure about the GPL aspect of this), but many
> systems will not have this by default.

We're making the dependency on OpenSSL go away by not using OpenSSL
anymore, not by packaging anything. I assume this can only cause us to
break GPL less than we currently are (if we currently are).

-Keshav

----
Join us in #sagemath on irc.freenode.net !

Reply all
Reply to author
Forward
0 new messages