octave-maintainers
[Top][All Lists]
Advanced

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

Re: : error building nsis installer with mxe-octave


From: John W. Eaton
Subject: Re: : error building nsis installer with mxe-octave
Date: Mon, 12 Jan 2015 15:45:08 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0

On 01/12/2015 03:17 PM, JohnD wrote:


-----Original Message-----
From: JohnD [mailto:address@hidden
Sent: Monday, January 12, 2015 3:55 PM
To: address@hidden; address@hidden
Subject: Re: : error building nsis installer with mxe-octave



Message: 5
Date: Mon, 12 Jan 2015 13:50:59 -0600
From: "John W. Eaton" <address@hidden>
To: octave maintainers mailing list <address@hidden>
Subject: error building nsis installer with mxe-octave
Message-ID: <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

I'm seeing the following error when attempting to build an nsis
installer
with the
current mxe-octave build tools.  Does anyone else have this problem?
Full
nsis
build log is attached.

i686-w64-mingw32-g++ -o build/release/stub_bzip2/stub_bzip2.exe -s
-mwindows -nostdlib -Wl,--exclude-libs,msvcrt.a
-Wl,--file-alignment,512
-Wl,-e,address@hidden -Wl,-Map,build/release/stub_bzip2/stub_bzip2.map -T
SCons/Config/linker_script build/release/stub_bzip2/bgbg.o
build/release/stub_bzip2/components.o build/release/stub_bzip2/exec.o
build/release/stub_bzip2/fileform.o build/release/stub_bzip2/Main.o
Cut .....
make[1]: *** [build-only-nsis] Error 2
make[1]: Leaving directory '/scratch/jwe/src/mxe-octave-hg'

real    0m14.608s
user    0m11.608s
sys     0m1.728s


I haven't seen it on my system - done a full build of stable-octave with
latest pull
of mxe this morning on my fedora box with no issues and a default-octave
build
last night

By current I am assuming with the mxe pull with the change for uuid ? Or is
that the change that is breaking the build for you?


Sorry, I should have included the hg id.  I'm at

  80b2b5cfde0f tip @

But like I said, it seems to have been a transient problem, possibly due to old files from an earlier build.

jwe




reply via email to

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