search

KnoooW / naclports

Automatically exported from code.google.com/p/naclports
0 stars 0 forks source link

Add Octave port #91

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Would you be interested in Octave port? In minimal configuration it requires at 
least these three aditional ports: f2c (fortran to c translator), libpgre and 
lapack. I have two additional questions:

Is it OK to require additional software to build the port? As it is now, Octave 
 requires the person building it to have f2c and fort77 (wrapper for f2c) 
installed. (Well, build.sh requires. Octave itself prefers gfortran but it can 
adapt)

Currently, my build breaks on this issue in libgnu 
http://lists.gnu.org/archive/html/bug-gnulib/2013-07/msg00032.html . They have 
a patch for it there. I haven't tested it yet because I am not sure of one 
thing: is it possible to include a GPL licensed patch into the port?

Original issue reported on code.google.com by jirkadan...@gmail.com on 26 Nov 2013 at 11:31

GoogleCodeExporter commented 9 years ago 
An octave port sounds great.  Thanks for the contribution!

In general the contributions to naclports (anything that gets checked in there)
need to be made in accordance with the google CLA
(https://developers.google.com/open-source/cla/individual).  I'm not sure how
an a GPL patch would fit in with this, but I will do some investigating.

In terms of requiring host tools, that should be fine in general.  As long as 
the
build script generates a useful error if it can't find the tool it needs.  It 
might
mean that we leave it out of the default build set.

I would go ahead with the port, and upload it to code review (using git cl 
upload)
and we can discuss it further there.

Original comment by sbc@google.com on 26 Nov 2013 at 5:23