From: "Nick Kelsey" <nickk@ubicom.com>
To: "blakjak" <blakjak@singnet.com.sg>
Cc: <insight@sources.redhat.com>
Subject: Re: Compilation of 5.3 on Cygwin under Win2000
Date: Sun, 15 Dec 2002 09:28:00 -0000 [thread overview]
Message-ID: <002a01c2a45f$2bff8690$0a00a8c0@nkelseyhome> (raw)
In-Reply-To: <redirect-4820036@silicondust.com>
Hi,
#4 - The Cygwin install uses a newer version of Bison that doesn't seam to
like gcc or gdb much. Run the cygwin install again and under Devel, Bison,
choose version 1.35-1.
I havn't looked in to the root cause at all though.
Nick
----- Original Message -----
From: "blakjak" <blakjak@singnet.com.sg>
To: <jafa@silicondust.com>
Sent: Sunday, December 15, 2002 1:07 AM
Subject: Compilation of 5.3 on Cygwin under Win2000
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> I have faced many problems trying to compile the latest Insight GDB
> under Cygwin on the Win2K platform.
>
> I found workarounds for some but I am now stuck and seeking advise.
>
> Here are the problems I found and solved:
>
> 1) tk/win/rc
>
> File cursor5e.cur is corrupt in the CVS update. I found it somewhere
> else on the web and updated my source.
>
> 2) itcl/itk/win/rc
>
> Files cursor3a.cur, cursor54.cur, cursor56.cur, cursor5e.cur and
> cursor76.cur are corrupt in the CVS update. I copied them over from
> my tk/win/rc directory.
>
> 3) expect/pty_termios.c
>
> Produces errors on compile. For my PC configuration lines 135 and
> 174 were both accessed resulting in a duplicate declaration of the
> variable 'slave_name'. (Solved by commenting out one of the
> declarations.)
>
> The second error encountered was that 'slave_name' is always declared
> as a static char* and it therefore cannot be assigned to another
> address. This causes a problem in line 377 :
>
> if ((slave_name = (char *)ptsname(master)) == NULL || unlockpt(master))
{
>
> always throws up a compile error saying incompatible types in
assignment.
>
> This can be fixed by removing the static keyword in the declaration of
> slave_name.
>
>
> Finally the problem I cannot solve:
>
> 4) gdb/c-exp.y
>
> When encountering the line in the makefile:
>
> /bin/sh ../../src-5.2.1/gdb/../ylwrap "bison -y"
> ../../src-5.2.1/gdb/c-exp.y y.tab.c c-exp.tmp --
>
> I get the following error:
>
> conflicts: 14 shift/reduce, 20 reduce/reduce
>
>
/cygdrive/c/sdk/insight/output/gdb/../../src-5.2.1/gdb/c-exp.y:846.2-847.49:
> war
> ning: rule never reduced because of conflicts: typebase: SIGNED_KEYWORD
> LONG LONG
> make: *** [c-exp.tab.c] Error 1
>
>
> Any help or direction you could offer me would be appreciated.
>
>
> Regards,
> BlakJak :]
>
>
next parent reply other threads:[~2002-12-15 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redirect-4820036@silicondust.com>
2002-12-15 9:28 ` Nick Kelsey [this message]
2002-12-15 1:07 blakjak
2002-12-15 10:31 ` Compilation of 5.3 on cygwin " Christopher Faylor
2002-12-16 3:34 ` blakjak
2002-12-16 8:55 ` Christopher Faylor
2002-12-19 6:41 ` blakjak
2002-12-19 8:03 ` Keith Seitz
2002-12-19 8:25 ` blakjak
2002-12-19 8:51 ` Keith Seitz
[not found] ` <redirect-4820052@silicondust.com>
2002-12-15 10:54 ` Jafa
2002-12-15 10:59 ` Christopher Faylor
[not found] ` <redirect-4820057@silicondust.com>
2002-12-15 11:07 ` Jafa
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='002a01c2a45f$2bff8690$0a00a8c0@nkelseyhome' \
--to=nickk@ubicom.com \
--cc=blakjak@singnet.com.sg \
--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).