From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Miller Subject: Re: octave license is incompatible with openssl Date: Wed, 10 Aug 2016 23:26:27 -0700 Message-ID: <20160811062627.mbaiqhssaejwh4hw@galago.mtmxr.com> References: <87h9b0ij9x.fsf@gmail.com> <87wpjvhfpg.fsf@elephly.net> <87eg62d5p4.fsf@gmail.com> <20160808200018.GA20179@jasmine> <871t1yvsn8.fsf@gmail.com> <20160809172728.b6wijrzccd5wdv37@galago.mtmxr.com> <87k2fpktsi.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42862) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bXjRt-0003dO-5S for guix-devel@gnu.org; Thu, 11 Aug 2016 02:26:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bXjRs-0002se-3V for guix-devel@gnu.org; Thu, 11 Aug 2016 02:26:37 -0400 Content-Disposition: inline In-Reply-To: <87k2fpktsi.fsf@gmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Alex Vong Cc: guix-devel@gnu.org, help-octave@gnu.org On Wed, Aug 10, 2016 at 14:43:57 +0800, Alex Vong wrote: > I thought it was an optional dependency because when I run > `./configure --help', it contains the following help: > > --with-openssl use libcrypto hash routines. Valid ARGs are: 'yes', > 'no', 'auto' => use if available, 'optional' => use > if available and warn if not available; default is > 'no' > > > Perhaps someone unaware of the issue adds this? Should I open a bug > report on this? Thanks for pointing that out. I wasn't aware of this until now. This configure option actually comes directly from the gnulib project. You'll notice that the default is "no", which is exactly as it should be. Octave provides some standard hash functions that are built on GPL compatible functions provided by gnulib. As a side effect of enabling these gnulib modules, gnulib automatically adds the `--with-openssl` option to allow the user to specify that the OpenSSL libcrypto functions should be used instead. I couldn't find this described or documented anywhere, just had to go digging through the configuration macros, e.g. http://git.savannah.gnu.org/cgit/gnulib.git/tree/m4/gl-openssl.m4 http://git.savannah.gnu.org/cgit/gnulib.git/tree/m4/sha1.m4 Cheers, -- mike