public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: peter.dhoye@advalvas.be
To: insight-gnats@sources.redhat.com
Subject: insight/311: Insight build error under cygwin, gcc 3.4.4
Date: Tue, 03 Apr 2007 23:23:00 -0000	[thread overview]
Message-ID: <20070403232059.28948.qmail@sourceware.org> (raw)


>Number:         311
>Category:       insight
>Synopsis:       Insight build error under cygwin, gcc 3.4.4
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 04 00:23:01 BST 2007
>Closed-Date:
>Last-Modified:
>Originator:     peter.dhoye@advalvas.be
>Release:        unknown-1.0
>Organization:
>Environment:
cygwin
gcc 3.4.4
>Description:
installing Insight under cygwin (gcc 3.4.4) fails, last lines are:

../../bfd/elflink.c: In function `compute_bucket_count':
../../bfd/elflink.c:5080: warning: unused variable `dynsymcount'
../../bfd/elflink.c:5083: warning: unused variable `amt'
../../bfd/elflink.c: At top level:
../../bfd/elflink.c:5077: warning: unused parameter 'hashcodes'
make[4]: *** [elflink.lo] Error 1
make[4]: Leaving directory `/home/Peter/insight/build/bfd'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/Peter/insight/build/bfd'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/Peter/insight/build/bfd'
make[1]: *** [all-bfd] Error 2
make[1]: Leaving directory `/home/Peter/insight/build'
make: *** [all] Error 2
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2007-04-03 23:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 23:23 peter.dhoye [this message]
2007-04-04 19:23 Peter D'Hoye
2007-04-26  0:13 kseitz

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=20070403232059.28948.qmail@sourceware.org \
    --to=peter.dhoye@advalvas.be \
    --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).