Problems building Insight

Problems building Insight

[Ultan Henry]

I've been trying to compile the 20000318 Insight snapshot under Win 98 for 
native use.

I'm using the 'full' download of Cygwin b20.1 with 19990115 patches (for 
Win95 make/fork problems) plus Cygwin 20000325 snapshot (to provide 
imagehlp.h and psapi.h files as mentioned elsewhere on this list).

The build fails during Win32-nat.c: 

win32-nat.c:1297: warning: implicit declaration of function `StackWalk'
win32-nat.c:1297: `IMAGE_FILE_MACHINE_I386' undeclared (first use in this 
function)
win32-nat.c:1297: (Each undeclared identifier is reported only once
win32-nat.c:1297: for each function it appears in.)
win32-nat.c:1298: `SymFunctionTableAccess' undeclared (first use in this 
function)
win32-nat.c: In function `child_init_frame':
win32-nat.c:1312: warning: unused parameter `leaf'
win32-nat.c: At top level:
win32-nat.c:1279: warning: `sfta' defined but not used
make[1]: *** [win32-nat.o] Error 1
make: *** [all-gdb] Error 2

This seems to indicate an incompatibility between some of the files in the 
snapshots I'm using. Is there a compination of Cygwin files and Insight 
snaphot that is known to be compatible and build correctly?

Thanks.

Re: Problems building Insight

[Chris Faylor]

On Mon, Apr 03, 2000 at 02:39:00AM +0100, Ultan Henry wrote:
>I've been trying to compile the 20000318 Insight snapshot under Win 98 for 
>native use.
>
>I'm using the 'full' download of Cygwin b20.1 with 19990115 patches (for 
>Win95 make/fork problems) plus Cygwin 20000325 snapshot (to provide 
>imagehlp.h and psapi.h files as mentioned elsewhere on this list).
>
>The build fails during Win32-nat.c: 
>
>win32-nat.c:1297: warning: implicit declaration of function `StackWalk'
>win32-nat.c:1297: `IMAGE_FILE_MACHINE_I386' undeclared (first use in this 
>function)
>win32-nat.c:1297: (Each undeclared identifier is reported only once
>win32-nat.c:1297: for each function it appears in.)
>win32-nat.c:1298: `SymFunctionTableAccess' undeclared (first use in this 
>function)
>win32-nat.c: In function `child_init_frame':
>win32-nat.c:1312: warning: unused parameter `leaf'
>win32-nat.c: At top level:
>win32-nat.c:1279: warning: `sfta' defined but not used
>make[1]: *** [win32-nat.o] Error 1
>make: *** [all-gdb] Error 2
>
>This seems to indicate an incompatibility between some of the files in the 
>snapshots I'm using. Is there a compination of Cygwin files and Insight 
>snaphot that is known to be compatible and build correctly?

Do you see a definition of "StackWalk" or IMAGE_FILE_MACHINE_I386 in
your imagehlp.h file?  If not, then you are either using the wrong
version of the file or you have your include file layout messed up
somehow.

FWIW, the StackWalk stuff should be gone in the most recent snapshots so
it might just be worthwhile to download the most recent insight snapshot
and use that.

cgf

Re: Problems building Insight

[Ultan Henry]

In-Reply-To: < 20000402214432.A25061@cygnus.com >

Thanks, I hadn't copied the files from the 'i686..' directory in the 
Cygwin snapshot into the 'i586..' directory. With the correct directory 
structure, things were much better!

Unfortunately, I still can't compile Insight. The build now fails 
complaining about '_ctype_' as shown below. I've seen several messages on 
the Cygwin mailing list about this that say that ctype is exported from 
the Cygwin1.DLL in recent snapshots and that it is important to make sure 
all the files are compatible.

I've tried again with a clean 'full' b20.1 Cygwin install, Cygwin 20000325 
snapshot and Insight 20000318 snapshot but still get the same results. 

(The Cygwin snapshot is necessary to provide the PSAPI.H and IMAGEHLP.H 
files, but just adding these files to a clean b20.1 Cygwin install 
produces other errors).

I'm not sure if this is a Cygwin or Insight problem, but any help would be 
appreciated!

gcc -g -O2 -W -Wall  -DCYGWIN_ALTTCL  -o expect.exe exp_main_exp.o 
libexpect526.a ../tcl/cygwin/libtcl_cygwin.a    -lm -luser32
libexpect526.a(exp_command.o): In function `human_write':
/temp/cygnus/insight+dejagnu-20000318/expect/exp_command.c:1726: undefined 
reference to `_ctype_'
/temp/cygnus/insight+dejagnu-20000318/expect/exp_command.c:1729: undefined 
reference to `_ctype_'
libexpect526.a(exp_command.o): In function `exp_new_i_complex':
/temp/cygnus/insight+dejagnu-20000318/expect/exp_command.c:1894: undefined 
reference to `_ctype_'
libexpect526.a(exp_command.o): In function `exp_i_parse_fds':
/temp/cygnus/insight+dejagnu-20000318/expect/exp_command.c:1949: undefined 
reference to `_ctype_'
/temp/cygnus/insight+dejagnu-20000318/expect/exp_command.c:1949: undefined 
reference to `_ctype_'
libexpect526.a(exp_command.o):/temp/cygnus/insight+dejagnu-20000318/expect
/exp_command.c:1952: more undefined references to `_ctype_' follow
collect2: ld returned 1 exit status
make[1]: *** [expect.exe] Error 1
make: *** [all-expect] Error 2
BASH.EXE-2.02$    

Re: Problems building Insight

[Chris Faylor]

On Mon, Apr 03, 2000 at 11:54:00AM +0100, Ultan Henry wrote:
>Unfortunately, I still can't compile Insight. The build now fails 
>complaining about '_ctype_' as shown below. I've seen several messages on 
>the Cygwin mailing list about this that say that ctype is exported from 
>the Cygwin1.DLL in recent snapshots and that it is important to make sure 
>all the files are compatible.

Well, this is correct.  You should make sure that you are using the latest
version of the header files and libraries and recompile (not relink) everything.

If you have further problems, please send email to the cygwin mailing list.

Thanks,
cgf

Re: Problems building Insight

[Jim Blandy]

What sad representatives of today's quick-fix, immediate gratification
culture you all are.  The only true way to build Insight is through
reflection, study, and humility.

Re: Problems building Insight

[Chris Faylor]

On Tue, Apr 04, 2000 at 11:00:58AM -0500, Jim Blandy wrote:
>What sad representatives of today's quick-fix, immediate gratification
>culture you all are.  The only true way to build Insight is through
>reflection, study, and humility.

This one shows much promise.  Observe him.  Learn from him.  Use consistent
stub libraries and DLLs...

cgf