From: "Peter Rockett" <p.rockett@sheffield.ac.uk>
To: <insight@sources.redhat.com>
Subject: RE: Can't build Insight with Cygwin
Date: Sat, 24 Dec 2005 18:09:00 -0000 [thread overview]
Message-ID: <005501c60892$77d234b0$0200a8c0@Albinoni> (raw)
Success!!!!
Not sure what I was doing but I think the files may have been left in some
sort of limbo state by my first attempts at building when I didn't have
bison and flex installed. (Although I thought I had cleaned and periodically
recreated the directory from the .bz2 file... but it's all beginning to blur
now.) Having delved into it, it's obvious now that I needed bison and flex
but it wasn't in the beginning.
Basically, I recreated the insight-6.4 directory and downloaded the cygwin
tools afresh. For cygwin, I opted for the default (base) selection together
with gcc, make, bison, flex, tcl/tk, autoconf and automake as well as any
dependencies the cygwin installer threw up. Then it built first time! Maybe
this list of packages could creep back into the docs as a recommended cygwin
install?
(BTW: Just discovered that Insight 6.3.50 is included prebuilt in the cygwin
stuff under the gdb package as well as in the mingw downloads).
Final point: Why does the Windows firewall chuck-up a message box when I
start Insight? What is Insight trying to do that should concern the
firewall?
Many thanks for all the help, guys!
Peter
> -----Original Message-----
> From: Keith Seitz [mailto:keiths@redhat.com]
> Sent: 23 December 2005 23:19
> To: p.rockett@sheffield.ac.uk
> Cc: 'insight'
> Subject: Re: FW: Can't build Insight with Cygwin
>
>
> Peter Rockett wrote:
>
> > Can anybody confirm that they have definitely built Insight
> 6.4 with
> > the latest cygwin tools (gcc v3.4.4)?
>
> In case it gets lost, I have definitely built Cygwin native on Win2k
> using latest (this AM) cygwin & gcc (using the patches mentioned
> earlier. Now onto your other problem...
>
> > undefined reference to `_cp_demangled_name_to_comp' undefined
> > reference to `_cp_comp_to_string'
>
> Both are from cp-names.y and declared in cp-support.h.
>
> > undefined reference to `_objc_parse'
> > undefined reference to `_objc_error'
> > undefined reference to `_c_error'
>
> All from in c-exp.y and declared in objc_lang.h and c_lang.h.
>
> > undefined reference to `_ada_parse'
>
> From ada-exp.y and ada-lang.h.
>
> Do you have yacc or bison installed? Do the files
> BUILDDIR/gdb/{ada,c,cp,jv}-exp.c exist? Are build errors around this?
> [Try removing those C files from the build dir and then make again.]
>
> Keith
>
next reply other threads:[~2005-12-24 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 18:09 Peter Rockett [this message]
2005-12-24 18:10 ` Keith Seitz
2005-12-24 23:39 ` Keith Seitz
2005-12-25 5:44 ` Christopher Faylor
2006-01-05 12:20 ` Dave Korn
-- strict thread matches above, loose matches on Subject: below --
2005-12-23 13:37 wilfried.fauvel
2005-12-22 23:40 Peter Rockett
2005-12-22 23:45 ` Peter Rockett
2005-12-23 11:58 ` Keith Seitz
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='005501c60892$77d234b0$0200a8c0@Albinoni' \
--to=p.rockett@sheffield.ac.uk \
--cc=insight@sources.redhat.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).