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

Synopsis: Insight build error under cygwin, gcc 3.4.4

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Thu Apr 26 01:13:58 2007
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->closed
State-Changed-By: kseitz
State-Changed-When: Thu Apr 26 01:13:58 2007
State-Changed-Why:
    This is a problem in bfd, not insight. The distinction is minutia, for sure, but that's the way it all works. Your best bet is to ask on the mailing list for BFD (binutils at sourceware dot org).
    
    Was the output of your 'make' log truncated too much? I don't see any errors there -- just warnings. I don't recall if the standard build has "-Werror" set, but if you only have build warnings, you might try disabling this build flag. Otherwise, your best bet is BFD folk.

http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=311


             reply	other threads:[~2007-04-26  0:13 UTC|newest]

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

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=20070426001358.31177.qmail@sourceware.org \
    --to=kseitz@sources.redhat.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=nobody@sources.redhat.com \
    --cc=peter.dhoye@advalvas.be \
    /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).