From: Matthias Andree <matthias.andree@gmx.de>
To: insight@sourceware.org
Subject: Re: insight not compiling under cygwin.
Date: Tue, 18 May 2010 09:25:00 -0000 [thread overview]
Message-ID: <4BF25CE2.8030607@gmx.de> (raw)
In-Reply-To: <AANLkTimWlSvF8UzW-50M9W9eKfpfQ4xyqaZr6pCUdePy@mail.gmail.com>
Am 18.05.2010 04:21, schrieb vikas gupta:
> I tried compiling insight 6.8-1 for cygwin, got the following
> compilation errors:-
> Please help:-
> /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../insigh
> t-6.8-1/bfd -I. -I. -I../../insight-6.8-1/bfd -I../../insight-6.8-1/bfd/../inclu
> de -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c -o el
> flink.lo ../../insight-6.8-1/bfd/elflink.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../insight-6.8-1/bfd -I. -I. -I.
> ./../insight-6.8-1/bfd -I../../insight-6.8-1/bfd/../include -W -Wall -Wstrict-pr
> ototypes -Wmissing-prototypes -Werror -g -O2 -c ../../insight-6.8-1/bfd/elflink.
> c -o elflink.o
> ../../insight-6.8-1/bfd/elflink.c:5237: warning: unused parameter 'info'
> make[4]: *** [elflink.lo] Error 1
> make[4]: Leaving directory `/cygdrive/c/insight-6.8-1/insight/bfd'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/cygdrive/c/insight-6.8-1/insight/bfd'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/cygdrive/c/insight-6.8-1/insight/bfd'
> make[1]: *** [all-bfd] Error 2
> make[1]: Leaving directory `/cygdrive/c/insight-6.8-1/insight'
> make: *** [all] Error 2
>
> my gdb version is gdb 6.8.0.
I reported this short after Cygwin 1.7 release I believe in January, no response
since then :-(
You can use configure options to suppress -Werror, but then building the tcl/tk
stuff fails later on.
--
Matthias Andree
prev parent reply other threads:[~2010-05-18 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 2:28 vikas gupta
2010-05-18 9:25 ` Matthias Andree [this message]
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=4BF25CE2.8030607@gmx.de \
--to=matthias.andree@gmx.de \
--cc=insight@sourceware.org \
/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).