From: ultan@cix.compulink.co.uk (Ultan Henry)
To: cgf@cygnus.com
Cc: ultan@cix.compulink.co.uk, insight@sourceware.cygnus.com
Subject: Re: Problems building Insight
Date: Mon, 03 Apr 2000 03:54:00 -0000 [thread overview]
Message-ID: <memo.43420@cix.compulink.co.uk> (raw)
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$
next reply other threads:[~2000-04-03 3:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 3:54 Ultan Henry [this message]
2000-04-03 13:18 ` Chris Faylor
2000-04-04 9:01 ` Jim Blandy
2000-04-04 10:40 ` Chris Faylor
-- strict thread matches above, loose matches on Subject: below --
2000-04-02 18:39 Ultan Henry
2000-04-02 18:44 ` 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.43420@cix.compulink.co.uk \
--to=ultan@cix.compulink.co.uk \
--cc=cgf@cygnus.com \
--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).