Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Markus Deuling <deuling@de.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 6.5.90 available for testing (GDB 6.6 pre-release)
Date: Mon, 04 Dec 2006 18:22:00 -0000	[thread overview]
Message-ID: <20061204182108.GA11343@adacore.com> (raw)
In-Reply-To: <4573EBCD.90505@de.ibm.com>


> I tried to build it on x86, FC5 with following error:

Thanks for trying it out...

> c1: warnings being treated as errors
> /home/user/gdb/6.5.90/gdb-6.5.90/gdb/p-valprint.c: In Funktion 
> »pascal_object_print_value_fields«:
> /home/user/gdb/6.5.90/gdb-6.5.90/gdb/p-valprint.c:756: Warnung: 
> »tmp_obstack.alloc_failed« könnte in dieser Funktion uninitialisiert 
> verwendet werden
> 
> <schnipp ... >
> 
> /home/user/gdb/6.5.90/gdb-6.5.90/gdb/p-valprint.c:756: Warnung: 
> »tmp_obstack.chunk_size« könnte in dieser Funktion uninitialisiert 
> verwendet werden
> make[2]: *** [p-valprint.o] Fehler 1
> make[2]: Leaving directory `/home/user/gdb/6.5.90/gdb-6.5.90/build/gdb'
> make[1]: *** [all-gdb] Fehler 2
> make[1]: Leaving directory `/home/user/gdb/6.5.90/gdb-6.5.90/build'
> make: *** [all] Fehler 2
> [user@host build]$

I don't speak German, so if you could set your environment to C,
that would help me understand the source of the problem.

A workaround for you is to build with --disable-werror.

> I checked out 6.6 branch and head some days ago, they build fine.

So we just need to isolate the patch from head that avoids the warning.

-- 
Joel


  reply	other threads:[~2006-12-04 18:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 19:23 Joel Brobecker
2006-12-04  9:35 ` Markus Deuling
2006-12-04 18:22   ` Joel Brobecker [this message]
2006-12-04 18:23     ` Daniel Jacobowitz
2006-12-05  7:02     ` Markus Deuling
2006-12-05 19:02       ` Joel Brobecker
2006-12-05 19:12       ` Jim Blandy
2006-12-05 20:09         ` Daniel Jacobowitz
2006-12-05 21:56           ` Jim Blandy
2006-12-05 20:35         ` H. J. Lu
2006-12-05 21:37         ` Mark Kettenis
2006-12-05 21:41           ` Daniel Jacobowitz
2006-12-06 16:06           ` Markus Deuling
2006-12-13 11:47             ` Markus Deuling
2006-12-04 12:09 ` Marc Kleine-Budde
2006-12-04 18:29   ` Joel Brobecker
2006-12-04 19:38 ` Ulrich Weigand
2006-12-05  7:40 ` Markus Deuling
2006-12-05 18:56   ` Joel Brobecker
2006-12-06 12:02     ` Markus Deuling
2006-12-06 17:48       ` Joel Brobecker
2006-12-07 10:00         ` Markus Deuling
2006-12-04 20:37 Kaz Kylheku

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=20061204182108.GA11343@adacore.com \
    --to=brobecker@adacore.com \
    --cc=deuling@de.ibm.com \
    --cc=gdb@sourceware.org \
    /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