public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: insight-prs@sources.redhat.com, kontakt@michaelstather.com,
	kseitz@sources.redhat.com, nobody@sources.redhat.com
Subject: Re: insight/282: insight Can't compile insight
Date: Sat, 19 Nov 2005 16:30:00 -0000	[thread overview]
Message-ID: <20051119163045.25606.qmail@sourceware.org> (raw)

Old Synopsis: %3A%20insight%2F281%3A%20Can%B4t%20compile%20insight
New Synopsis: insight Can't compile insight

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Sat Nov 19 16:30:45 2005
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->feedback
State-Changed-By: kseitz
State-Changed-When: Sat Nov 19 16:30:45 2005
State-Changed-Why:
    You say the latest snapshot, but don't list any specifics (download file name with the date). I also don't know what host system or target you are attempting to build. In future bug reports, please do not omit these details.
    
    Nonetheless, the build error you are seeing is occurring in the bfd sources. You're having problems with documentation building, so I'll hazard a guess that you're running on cygwin (windows) and you don't have all the appropriate packages installed to actually build them. You're probably missing the gettext package.

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


             reply	other threads:[~2005-11-19 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19 16:30 kseitz [this message]
2005-11-19 18:13 Keith Seitz
2005-11-19 18:23 Michael Stather
2005-11-19 19:43 Keith Seitz

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=20051119163045.25606.qmail@sourceware.org \
    --to=kseitz@sources.redhat.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=kontakt@michaelstather.com \
    --cc=nobody@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).