octave-maintainers
[Top][All Lists]
Advanced

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

Re: mxe-octave error on Ubuntu 12.04


From: Philip Nienhuis
Subject: Re: mxe-octave error on Ubuntu 12.04
Date: Thu, 13 Mar 2014 18:48:18 +0100
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:25.0) Gecko/20100101 Firefox/25.0 SeaMonkey/2.22.1

<John Donoghue added in To:>

Tatsuro MATSUOKA wrote:
--- On Thu, 2014/3/13, Philip Nienhuis wrote:

tmacchant wrote
Hello

I have tried to build mxe-octave on Ubuntu 12.04 (32bit)  by the following
instruction

http://wiki.octave.org/Windows_Installer

In building native-gcc, I have met the following error.

g++ -c   -g -O2 -DIN_GCC   -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
:
<looong snip>
:
cc1plus: warning: unrecognized command line option "-Wno-narrowing"
[enabled by default]
make[4]: *** [build/genconstants.o] Error 1
make[4]: Leaving directory
`/home/tatsuromatsuoka/work/octave/mxe-octave/tmp-native-gcc/gcc-4.8.2.build/gcc'
make[3]: *** [all-gcc] Error 2
make[3]: Leaving directory
`/home/tatsuromatsuoka/work/octave/mxe-octave/tmp-native-gcc/gcc-4.8.2.build'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/tatsuromatsuoka/work/octave/mxe-octave/tmp-native-gcc/gcc-4.8.2.build'
make[1]: *** [build-only-native-gcc] Error 2
make[1]: Leaving directory `/home/tatsuromatsuoka/work/octave/mxe-octave'

Any suggestions?

Maybe reading this thread will help:

http://octave.1599824.n4.nabble.com/mxe-octave-cross-build-errors-when-building-native-gcc-tt4662612.html
John D attached some patches there.
:
Philip

With native-gcc4.patch obtained from the thread suggeted by you, the native-gcc 
was successfully built and finally octave-3.8.1 installer was bbtained.

I appreciate for your advise.

BTE, will the patch by John D be included in the hg repository?

I don't know if it is specific to some Linux distros.
But as you needed it on Ubuntu, John D on Fedora, and me on Mageia, I'd say it is needed somehow.

Philip



reply via email to

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