public inbox for
 help / color / mirror / Atom feed
From: Keith Seitz <>
Cc: "'insight'" <>
Subject: Re: FW: Can't build Insight with Cygwin
Date: Sat, 24 Dec 2005 14:00:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <000a01c607ec$374605d0$0300a8c0@Albinoni>

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.]


  reply	other threads:[~2005-12-23 23:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cmu-lmtpd-21756-1135354673-4@impala>
2005-12-23 18:52 ` Peter Rockett
2005-12-23 21:41   ` Peter Rockett
2005-12-24 14:00     ` Keith Seitz [this message]
2005-12-23 21:47   ` Spen
     [not found] <>
2005-12-23 23:19 ` Keith Seitz
2005-12-24  0:55   ` Peter Rockett
2005-12-24 18:00   ` Spen
     [not found] <cmu-lmtpd-20522-1135363936-1@impala>
2005-12-23 22:58 ` Peter Rockett
     [not found] <>
2005-12-23 18:10 ` Eric Weddington
2005-12-23 16:17 wilfried.fauvel
2005-12-23 16:21 ` FW: " Peter Rockett
2005-12-23 16:24 ` Spen
  -- strict thread matches above, loose matches on Subject: below --
2005-12-23 16:09 Peter Rockett

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:

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

  git send-email \ \ \ \ \

* 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).