octave-maintainers
[Top][All Lists]
Advanced

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

RE: cross-building with --enable-64: Assembly error


From: John D
Subject: RE: cross-building with --enable-64: Assembly error
Date: Fri, 15 Aug 2014 22:45:20 -0400


-----Original Message-----
From: John W. Eaton [mailto:address@hidden 
Sent: Friday, August 15, 2014 7:26 PM
To: John D; address@hidden; Philip Nienhuis
Cc: address@hidden
Subject: Re: cross-building with --enable-64: Assembly error

On 08/15/2014 12:59 PM, John D wrote:
> Message: 2
> Date: Thu, 14 Aug 2014 14:21:21 -0700 (PDT)
> From: PhilipNienhuis <address@hidden>
> To: address@hidden
> Subject: MXE: cross-building with --enable-64: Assembly error
>       libgcrypt
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> Tried to cross-build Octave for Windows with --enable-64, but got this 
> when builing libgcrypt:
>
> :
> libtool: compile:  x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I.. 
> -I../src -I../src 
> -I/home/philip/devel/octdev/mxe/mxe_082014_64/usr/x86_64-w64-mingw32/i
> nclude 
> -I/home/philip/devel/octdev/mxe/mxe_082014_64/usr/x86_64-w64-mingw32/i
> nclude -g -O2 -Wall -MT rndhw.lo -MD -MP -MF .deps/rndhw.Tpo -c 
> rndhw.c -DDLL_EXPORT -DPIC -o .libs/rndhw.o
> /tmp/ccDbQOKt.s: Assembler messages:
> /tmp/ccDbQOKt.s:53: Error: unsupported instruction `mov'
> make[4]: *** [rndhw.lo] Error 1
> make[4]: Leaving directory
> `/home/philip/devel/octdev/mxe/mxe_082014_64/tmp-libgcrypt/libgcrypt-1
> .6.1/r
> andom'
> :
>
> Is this due to too aggressive optimization? "mov" looks like one of 
> the most basic CPU instructions to me....
>
> My system: Mageia 2 32-bits (2 years old).
>
> Philip
>
>
> --
>
> Not that it helps any, but it compiles fine on my Fedora 20 box .
>
> According to the log, the -O2 optimization is used on mine.
>
> A quick look on the internet shows a few other people have had similar 
> issues when building gcrrypt.

I see now that the libcgrypt build completes if I use CFLAGS="".

So maybe it is a compiler bug?

I see that GCC 4.9.1 has been released.  I suppose we should try it and see
if the problem is fixed in that version.

jwe


gcc 4.9.1 changes pushed to mxe-octave




reply via email to

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