octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GSL in octave


From: Tatsuro MATSUOKA
Subject: Re: GSL in octave
Date: Wed, 20 Jul 2016 11:22:42 +0900 (JST)

>From: Julien Bect <address@hidden>
>To: address@hidden 
>Date: 2016/7/20, Wed 05:43
>Subject: Re: GSL in octave
> 
>
>Le 19/07/2016 à 04:09, Susi Lehtola a écrit :
>
>On 07/18/2016 02:03 PM, Julien Bect wrote: 
>>
>>I have pushed most of your changes to the OF repo.  You will notice that 
>>>I have folded several of your changesets into one for clarity.
        Perhaps 
>>>should you restart now from a fresh clone of the OF repo. 
>>>
>>What do you mean by "most"? 
>Most, really.  I haven't pushed (yet) a few minor things:
> * your changes to DESCRIPTION -> we'll change that when release
    approaches
> * your changes to the test files (loading package at the begining)
    -> shouldn't we turn them into real unit tests?
> * changes to the cleaning rule in Makefile -> I'll look into
    this later, perhaps should we call src/Makefile clean recursively?
>
>Since my previous email, I have pushed all your recent changesets
    and added a few of my own.
>
>I again had to fold some of your changesets for clarity.  When you
    have several consecutive changesets that address the same logical
    change (typically, you realize that you forgot to commit something,
    or you discover that you made a typo) please don't leave them like
    them.  Instead, fold them using hg's mq extension.  Of course, you
    have to do that *before* you push to the public repo (i.e., the
    changesets must be in "draft" phase).
>
>It seems that there is something wrong with your latest changes to
    legendre_sphPlm_array.cc (see log below).
>
>@++
>Julien
>
>
>
>g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
    -I/usr/include/octave-4.0.3/octave/..
    -I/usr/include/octave-4.0.3/octave -I/usr/include/hdf5/serial
    -I/usr/include/mpi -pthread -fopenmp -g -O2 -fstack-protector-strong
    -Wformat -Werror=format-security    -DHAVE_OCTAVE_40
    legendre_sphPlm_array.cc -o legendre_sphPlm_array.o


> DEFUN_DLD(legendre_array, args, nargout, "\
> ^
>legendre_sphPlm_array.cc: In function ‘octave_value_list
    Flegendre_array(const octave_value_list&, int)’:
>legendre_sphPlm_array.cc:148:69: error: invalid conversion from
    ‘int’ to ‘gsl_sf_legendre_t’ [-fpermissive]
>     gsl_sf_legendre_array_e (norm, lmax, x, csphase,
    y.fortran_vec());
>                                                                    
    ^
>In file included from /usr/include/gsl/gsl_sf.h:28:0,
>                 from legendre_sphPlm_array.cc:21:
>/usr/include/gsl/gsl_sf_legendre.h:325:5: note:   initializing
    argument 1 of ‘int gsl_sf_legendre_array_e(gsl_sf_legendre_t,
    size_t, double, double, double*)’
> int gsl_sf_legendre_array_e(const gsl_sf_legendre_t norm,
>     ^
>Makefile:20 : la recette pour la cible « legendre_sphPlm_array.oct »
    a échouée
>make: *** [legendre_sphPlm_array.oct] Erreur 1


I have tried on windows 10 on octave-4.0.3 with gsl-2.1.

The same error appeared

In file included from c:\octave\octave-4.0.3-x64\include\gsl\gsl_sf.h:28:0,
                 from legendre_sphPlm_array.cc:21:
c:\octave\octave-4.0.3-x64\include\gsl\gsl_sf_legendre.h:325:5: note: 
initializing argument 1 of
 'int gsl_sf_legendre_array_e(gsl_sf_legendre_t, size_t, double, double, 
double*)'
 int gsl_sf_legendre_array_e(const gsl_sf_legendre_t norm,
     ^
make: *** [legendre_sphPlm_array.oct] Error 1
make: Leaving directory `/tmp/oct-YvPGvD/gsl-1.1.0/src'

However, this is noticed by Susi and I would like say that this is platform 
independent.

Tatsuro



reply via email to

[Prev in Thread] Current Thread [Next in Thread]