public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: ultan@cix.compulink.co.uk (Ultan Henry)
To: insight@sourceware.cygnus.com
Cc: ultan@cix.compulink.co.uk
Subject: Problems building Insight
Date: Sun, 02 Apr 2000 18:39:00 -0000	[thread overview]
Message-ID: <memo.34957@cix.compulink.co.uk> (raw)

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.

             reply	other threads:[~2000-04-02 18:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-02 18:39 Ultan Henry [this message]
2000-04-02 18:44 ` Chris Faylor
2000-04-03  3:54 Ultan Henry
2000-04-03 13:18 ` Chris Faylor
2000-04-04  9:01   ` Jim Blandy
2000-04-04 10:40     ` Chris Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=memo.34957@cix.compulink.co.uk \
    --to=ultan@cix.compulink.co.uk \
    --cc=insight@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).