public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Perry Smith <pedzsan@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: gdb 7.3.1 and gdb 7.2 on AIX 6.1
Date: Mon, 24 Oct 2011 16:07:00 -0000	[thread overview]
Message-ID: <1B63B75E-9F08-4E12-8779-EF256AD5BFFA@gmail.com> (raw)
In-Reply-To: <m3ty6ybhti.fsf@fleche.redhat.com>


On Oct 24, 2011, at 9:11 AM, Tom Tromey wrote:

>>>>>> "Perry" == Perry Smith <pedzsan@gmail.com> writes:
> 
>>> /usr/work/src/gdb-7.2/bfd/bfd.c: In function '_bfd_default_error_handler':
>>> /usr/work/src/gdb-7.2/bfd/bfd.c:710:3: error: value computed is not used
> 
> Perry> The same error happens with 7.3.1 and 7.2 (the above snippet is
> Perry> from 7.2).
> 
> Perry> Searching the web did not hit anything connected to gdb.  The curious
> Perry> thing is that I compiled gdb 7.2 using a previous gcc of 4.2.4.
> 
> Warnings change between versions of gcc.
> 
> Perry> I notice the message "warnings being treated as errors" which might
> Perry> explain why, looking at the code, I don't see the problem.
> 
> Perry> Any suggestions of what is wrong?
> 
> Probably nothing is wrong, just gcc being too eager.
> If you just want to build it, don't use -Werror.

Thank you.

For those watching on T.V. at home:

configure --enable-werror=no

but now I have another problem.  When I try "make install", I get 
the "You need makeinfo" message.

I've fiddled around with it a bit but I'm going to give up and just install
makeinfo and its friends.  I'm doing an "out of tree" build.  Maybe thats
part of the issue here.

pedz

  reply	other threads:[~2011-10-24 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24  2:16 Perry Smith
2011-10-24 15:43 ` Tom Tromey
2011-10-24 16:07   ` Perry Smith [this message]
2011-10-24 20:03     ` Joel Brobecker

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=1B63B75E-9F08-4E12-8779-EF256AD5BFFA@gmail.com \
    --to=pedzsan@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=tromey@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).