Insight CVS version Build failed on ubuntu9.04

Insight CVS version Build failed on ubuntu9.04

[ababab ababab]

All,

Where can I find the binary release for windows built from MinGW/MSYS system?
it seems only 6.6 version available from MinGW offical website!

I try to build latest CVS version on MinGW but failed. Maybe we need a
patch file!

BRs
zaqtiger
2010/01/03

Re: Insight CVS version Build failed on ubuntu9.04

[Keith Seitz]

On 01/03/2010 01:42 AM, ababab ababab wrote:

> Where can I find the binary release for windows built from MinGW/MSYS system?
> it seems only 6.6 version available from MinGW offical website!

I don't release binary releases -- only source. Sorry.

> I try to build latest CVS version on MinGW but failed. Maybe we need a
> patch file!

I've checked in a patch for the known build failure (which affects all 
hosts). I'm trying to build a cygwin version now. I am not yet set up to 
do mingw builds yet, but if I can get to it, I will give it a go.

What exactly was the build problem? Can you post the build output?

Keith

Re: Insight CVS version Build failed on ubuntu9.04

[ababab ababab]

My build steps on MinGW/MYSYS:

$  ../src/configure
$ make

Then below error happen:
gcc -shared -g -O2  -o tcl84.dll -mwin32                -Wl,--out-implib,libtcl8
4.a regcomp.o regexec.o regfree.o regerror.o tclAlloc.o tclAsync.o tclBasic.o tc
lBinary.o tclCkalloc.o tclClock.o tclCmdAH.o tclCmdIL.o tclCmdMZ.o tclCompCmds.o
 tclCompExpr.o tclCompile.o tclDate.o tclEncoding.o tclEnv.o tclEvent.o tclExecu
te.o tclFCmd.o tclFileName.o tclGet.o tclHash.o tclHistory.o tclIndexObj.o tclIn
terp.o tclIO.o tclIOCmd.o tclIOGT.o tclIOSock.o tclIOUtil.o tclLink.o tclLiteral
.o tclListObj.o tclLoad.o tclMain.o tclNamesp.o tclNotify.o tclObj.o tclPanic.o
tclParse.o tclParseExpr.o tclPipe.o tclPkg.o tclPosixStr.o tclPreserve.o tclProc
.o tclRegexp.o tclResolve.o tclResult.o tclScan.o tclStringObj.o tclStubInit.o t
clStubLib.o tclThread.o tclThreadAlloc.o tclThreadJoin.o tclTimer.o tclUtf.o tcl
Util.o tclVar.o tclWin32Dll.o tclWinChan.o tclWinConsole.o tclWinSerial.o tclWin
Error.o tclWinFCmd.o tclWinFile.o tclWinInit.o tclWinLoad.o tclWinMtherr.o tclWi
nNotify.o tclWinPipe.o tclWinSock.o tclWinThrd.o tclWinTime.o  strftime.o strtol
l.o strtoull.o tcl.res.o
Creating library file: libtcl84.a
tclWinChan.o: In function `Tcl_MakeFileChannel':
C:\msys\1.0\home\E12714\insight\build\tcl\win/../../../src/tcl/win/tclWinChan.c:
1052: undefined reference to `ESP'
C:\msys\1.0\home\E12714\insight\build\tcl\win/../../../src/tcl/win/tclWinChan.c:
1052: undefined reference to `EBP'
C:\msys\1.0\home\E12714\insight\build\tcl\win/../../../src/tcl/win/tclWinChan.c:
1067: undefined reference to `ESP'
C:\msys\1.0\home\E12714\insight\build\tcl\win/../../../src/tcl/win/tclWinChan.c:
1067: undefined reference to `EBP'
collect2: ld returned 1 exit status
make[3]: *** [tcl84.dll] Error 1
make[3]: Leaving directory `/home/E12714/insight/build/tcl/win'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/E12714/insight/build/tcl'
make[1]: *** [all-tcl] Error 2
make[1]: Leaving directory `/home/E12714/insight/build'
make: *** [all] Error 2
I have tried to apply 6.6 patch from MinGW offical website but failed:
 The link as below:
http://sourceforge.net/projects/mingw/files/GNU%20Source-Level%20Debugger/Release%20Candidate_%20gdb-6.6/mingw-insight-6.6-patch.zip/download

mingw-insight-6.6-patch.zip


BRs
zaqtiger
2010/01/06

On Tue, Jan 5, 2010 at 4:20 AM, Keith Seitz <keiths@redhat.com> wrote:
> On 01/03/2010 01:42 AM, ababab ababab wrote:
>
>> Where can I find the binary release for windows built from MinGW/MSYS
>> system?
>> it seems only 6.6 version available from MinGW offical website!
>
> I don't release binary releases -- only source. Sorry.
>
>> I try to build latest CVS version on MinGW but failed. Maybe we need a
>> patch file!
>
> I've checked in a patch for the known build failure (which affects all
> hosts). I'm trying to build a cygwin version now. I am not yet set up to do
> mingw builds yet, but if I can get to it, I will give it a go.
>
> What exactly was the build problem? Can you post the build output?
>
> Keith
>