public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: BrianMcGinley@BiometricSolutions.com
To: insight-gnats@sources.redhat.com
Subject: insight/184: build fails at WINDRES step
Date: Tue, 05 Nov 2002 14:43:00 -0000	[thread overview]
Message-ID: <20021105224218.4286.qmail@sources.redhat.com> (raw)


>Number:         184
>Category:       insight
>Synopsis:       build fails at WINDRES step
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 05 14:43:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Brian McGinley
>Release:        Insight 5.2.x
>Organization:
>Environment:
Windows XP with latest cygwin
>Description:
I tried to build Insight on a Windows XP system, using cygwin, which I got by following the instructions on this page   http://sources.redhat.com/cygwin/

I performed the build after having successfully built my arm tools following the instructions on this page   http://sources.redhat.com/ecos/tools/win-arm-elf.html

To build Insight, I followed the instructions on this page  http://sources.redhat.com/insight/cygwin.html

Unfortunately, I got the following error, which I was unable to find any reference to on any of the mailing lists.

gcc -c   -DWIN32 -D_WIN32 -D_MT -D_DLL -I../../../src/tk/win/../win -I../../../s
rc/tk/win/../generic -I../../../src/tk/win/../bitmaps -I../../../src/tk/win/../x
lib -I../../../src/tk/win/../../tcl/generic  -g -O2 ../../../src/tk/win/../gener
ic/tkWindow.c
In file included from ../../../src/tk/generic/tkPort.h:27,
                 from ../../../src/tk/generic/tkWindow.c:18:
../../../src/tk/win/tkWinPort.h:52:1: warning: "OPEN_MAX" redefined
In file included from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/limits.h:132,
                 from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/syslimits.h:7,

                 from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/include/limits.h:11,
                 from ../../../src/tk/win/tkWinPort.h:32,
                 from ../../../src/tk/generic/tkPort.h:27,
                 from ../../../src/tk/generic/tkWindow.c:18:
/usr/include/limits.h:143:1: warning: this is the location of the previous defin
ition
windres --include ../../../src/tk/win/../win/rc --include ../../../src/tk/win/..
/generic --define VS_VERSION_INFO=1 ../../../src/tk/win/../win/rc/tk.rc tkres.o
windres: ../../../src/tk/win/../win/rc/cursor5e.cur: read of 77824 returned 0
make[2]: *** [tkres.o] Error 1
make[2]: Leaving directory `/insight/tk/win'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/insight/tk'
make: *** [all-tk] Error 2

Can someone please help me resolve this problem?

Thanks,
Brian
>How-To-Repeat:
follow Description
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-11-05 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 14:43 BrianMcGinley [this message]
2002-11-19 20:18 kseitz
2003-01-06 15:33 Rolf Berg

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=20021105224218.4286.qmail@sources.redhat.com \
    --to=brianmcginley@biometricsolutions.com \
    --cc=insight-gnats@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).