Re: Is --enable-64 still experimental?

[chechu]

Good morning everyone,

During last week we have built mxe-octave on three different linux
environments, using the  suggestions from mxe-octave wiki and
http://savannah.gnu.org/bugs/index.php?43319
i#comment 13.
We are trying to use image package with 64bit indexing on Linux.

On mxe-octave stable-branch we can't build image 2.4.0; it needs octave
4.0.0>=
We have not succeded on those builds, the problem remains, maybe we have
done something wrong.  We are not succeeding on Linux 64bit addressing with
image package without "modifying" the includes containing the "typos" that
fail, either with mxe-octave :(

Any suggestions? Thanks so much in advance.

-----------------
----- Logs of the results obtained


RedHatEnterprise Linux 7: gcc-4.9.2


---stable-octave: 3.8.2 with image package 2.2.2:

Builds stable-octave successfully with 64bit addressing ---->image 2.2.2  it
fails at spatial_filtering complaining about ambiguous assumption as with an
standard octave build:


__spatial_filtering__.cc:193:25: note: candidates are:

               
/mnt/extra1/mxe-octave-006263ce4905/usr/include/octave-3.8.2/octave/../octave/oct-inttypes.h:884:3:
note: octave_int<T>::operator float() const [with T = unsigned char]
   operator float (void) const { return float_value (); }
   ^
/mnt/extra1/mxe-octave-006263ce4905/usr/include/octave-3.8.2/octave/../octave/oct-inttypes.h:882:3:
note: octave_int<T>::operator double() const [with T = unsigned char]
   operator double (void) const { return double_value (); }
   ^
/mnt/extra1/mxe-octave-006263ce4905/usr/include/octave-3.8.2/octave/../octave/oct-inttypes.h:878:3:
note: octave_int<T>::operator T() const [with T = unsigned char]




---default-octave: 4.0.0rc3 with octave-forge image package 2.4.0:

Builds default-octave successfully with 64bit addressing ---->image 2.4.0 
it fails at spatial_filtering complaining about ambiguous assumption as with
the octave stable-build out or within of mxe-octave



Debian 8.0 Jessie:  gcc-4.9.2


---stable-octave: 3.8.2 with image package 2.2.2:

Builds stable-octave successfully with 64bit addressing ---->image 2.2.2  it
fails at spatial_filtering complaining about ambiguous assumption.



---default-octave: 4.0.0rc3 with octave-forge image package 2.4.0:

Builds default-octave successfully with 64bit addressing ---->image 2.4.0 
it fails at spatial_filtering complaining about ambiguous assumption



Fresh install of Ubuntu 14.04 LTS: gcc-4.8.2-19 ubuntu


---stable-octave: 3.8.2 with image package 2.2.2:

Builds stable-octave successfully with 64bit addressing ---->image 2.2.2  it
fails at spatial_filtering complaining about ambiguous assumption.


---default-octave: 4.0.0rc3 with octave-forge image package 2.4.0:

Fails on Building default-octave; because of libosmesa -gui- errors



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Is-enable-64-still-experimental-tp4669274p4670112.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.