From: Keith Seitz <keiths@redhat.com>
To: sandip gangakhedkar <sandipfloyd@gmail.com>
Cc: insight@sourceware.org
Subject: Re: make fails on ubuntu 11.04 VM,
Date: Fri, 04 Nov 2011 01:37:00 -0000 [thread overview]
Message-ID: <4EB341A1.2070201@redhat.com> (raw)
In-Reply-To: <CAEPsib2jtCPrqnt44jKgcnBujzs5E_HC61wNwNt_npf+XEXtyg@mail.gmail.com>
On 11/03/2011 06:11 PM, sandip gangakhedkar wrote:
> cc1: warnings being treated as errors
> linux-nat.c: In function ‘linux_nat_info_proc_cmd’:
> linux-nat.c:2879:10: error: ignoring return value of ‘fgets’, declared
> with attribute warn_unused_result
> make[2]: *** [linux-nat.o] Error 1
> make[2]: Leaving directory `/home/sandipg/insight-6.8-1/gdb'
> make[1]: *** [all-gdb] Error 2
> make[1]: Leaving directory `/home/sandipg/insight-6.8-1'
> make: *** [all] Error 2
> sandipg@sandipg-VirtualBox:~/insight-6.8-1$ make> makelog
> cc1: warnings being treated as errors
> linux-nat.c: In function ‘linux_nat_info_proc_cmd’:
> linux-nat.c:2879:10: error: ignoring return value of ‘fgets’, declared
> with attribute warn_unused_result
> make[2]: *** [linux-nat.o] Error 1
> make[1]: *** [all-gdb] Error 2
> make: *** [all] Error 2
That's a gdb error. Normally, I would advise you to try the gdb mailing
list for better advice, but I suspect you may be attempting to build
something quite old...
For Insight, definitely grab CVS HEAD or git. If you *really* want a
release, try grabbing the latest gdb release and copying the gdb/gdbtk
and libgui folders inside it. But I suspect it will be much easier for
you to just grab the latest sources. FWIW, I use this daily for my own work.
Or you could pass "--disable-werror" to configure to suppress erroring
on warnings.
If you need to get your specific error fixed, try emailing the gdb@
mailing list.
Keith
next prev parent reply other threads:[~2011-11-04 1:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEPsib3XCnbO1yK49NQDp1QFQJVYamgBR1nQL1vAL7+HGVMKfw@mail.gmail.com>
2011-11-04 1:12 ` sandip gangakhedkar
2011-11-04 1:37 ` Keith Seitz [this message]
2011-11-04 2:47 ` sandip gangakhedkar
2011-11-04 3:54 ` sandip gangakhedkar
2011-11-04 4:18 ` Keith Seitz
2011-11-04 17:09 ` sandip gangakhedkar
2011-11-04 18:32 ` Keith Seitz
[not found] ` <4EB43706.8020509@redhat.com>
[not found] ` <CAEPsib1LCq-RTQrsdPwruOS7P-6mrig=SSO09KO+EjThGpphHw@mail.gmail.com>
[not found] ` <4EBBFDB3.2010404@redhat.com>
2011-11-10 19:55 ` sandip gangakhedkar
2011-11-10 20:06 ` 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=4EB341A1.2070201@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=sandipfloyd@gmail.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).