This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Problems in Building Insight 5.0 on NT 4.0 sp6a
- To: <insight at sourceware dot cygnus dot com>
- Subject: Problems in Building Insight 5.0 on NT 4.0 sp6a
- From: "Mark Van De Vyver" <mvdv at bigfoot dot com>
- Date: Mon, 9 Oct 2000 14:37:54 +0800
- Reply-To: <mvdv at bigfoot dot com>
Hi,
Typing gdb in bash (latest release cygwin) fires up an app that describes
it's self as the Insight Debugger. So the following is not really a
'problem' i.e. I can still work on getting to where I want to be... However
I would like to build Insight on this machine as an excercise. I'm not that
familiar with Unix/Cygwin/ and the toolchain so you may need to be patient.
If you want me to give additional info just let me know what cmds to issue.
I've been trying to build Insight 5.0 on NT 4.0 sp 6a, using the
instructions on the ecos page (this seemed to be the only place describing a
build?)
http://sources.redhat.com/ecos/tools/win-i386-elf.html
I've not tried to build binutiuls or gcc and the only part I was unable to
do that is described there was 'touch'ing the source files after applying
their patch (which applied without complaint). Output lines are sandwiched
between +++'s
my mount table looks like this:
/ $ mount
Device Directory Type Flags
c:\cygwin\usr\local /usr/local/obj system binmode
d:\gnu\insight /insight system binmode
C:\cygwin\bin /usr/bin system textmode
C:\cygwin\lib /usr/lib system textmode
c:\cygwin\obj /obj system binmode
c:\cygwin\src /src system textmode
c:\cygwin\usr /usr system binmode
C:\cygwin / system textmode
d: /d system textmode
f: /dvd system textmode
g: /cdw system textmode
/ $
The configure cmd I used was:
/tmp/build/gdb $
/src/gdb/insight-5.0/configure --target=i686-pc-cygwin --prefix=/usr/bin --
exec-prefix=/usr/bin/i686-pc-cygwin -v 2>&1 | tee configure1.out
Is the following msg 'normal/expected' during the configure phase.
+++++++++++++++++++++++++++++++++++++++++
not updating unwritable cache ../config.cache
+++++++++++++++++++++++++++++++++++++++++
Is the overriding mode 0644? prompt and sometimes a similar prompt proper
behaviour?
Any idea what to do to fix it? I did have some problems with setting up
ntsec and the passwd files, if that gives a clue. This was the only prompt
received during configure.
+++++++++++++++++++++++++++++++++++++++++
creating Makefile
Configuring utils...
Created "Makefile" in /tmp/build/gdb/utils
mv: replace `Makefile', overriding mode 0644? y
Configuring spu...
Created "Makefile" in /tmp/build/gdb/utils/spu
/tmp/build/gdb $
+++++++++++++++++++++++++++++++++++++++++
Then the make command I ran was
/tmp/build/gdb $ make -w all install 2>&1 | tee make.out
+++++++++++++++++++++++++++++++++++++++++
touch stamp-lib
make[3]: Leaving directory `/tmp/build/gdb/opcodes'
make[2]: Leaving directory `/tmp/build/gdb/opcodes'
make[1]: Leaving directory `/tmp/build/gdb/opcodes'
make[1]: Entering directory `/tmp/build/gdb/tcl'
make[2]: Entering directory `/tmp/build/gdb/tcl/win'
gcc -c -DWIN32 -D_WIN32 -D_MT -D_DLL -I/src/gdb/insight-5.0/tcl/win/../win
-I/
src/gdb/insight-5.0/tcl/win/../generic -D__WIN32__ -g -O2
/src/gdb/insight-5.0/
tcl/win/tclAppInit.c
windres --include /src/gdb/insight-5.0/tcl/win/../generic --include
/src/gdb/ins
ight-5.0/tcl/win/../win --define __WIN32__ --define VS_VERSION_INFO=1
/src/gdb/i
nsight-5.0/tcl/win/tclsh.rc tclshres.o
0 [main] windres 16373 handle_exceptions: Exception:
STATUS_ACCESS_VIOLATI
ON
6288 [main] windres 16373 stackdump: Dumping stack trace to
windres.exe.stack
dump
Signal 11
make[2]: *** [tclshres.o] Error 139
make[2]: Leaving directory `/tmp/build/gdb/tcl/win'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/build/gdb/tcl'
make: *** [all-tcl] Error 2
make: Leaving directory `/tmp/build/gdb'
/tmp/build/gdb $
+++++++++++++++++++++++++++++++++++++++++
Thanks in advance.
Mark Van De Vyver
http://www.bigfoot.com/~mvdv
Mailto:mvdv@bigfoot.com