public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: markandrews@skylertech.com
To: insight-gnats@sources.redhat.com
Cc: mark@andrews.net
Subject: insight/294: weekly build and 6.4 stable fail to compile under FC5
Date: Thu, 20 Apr 2006 21:23:00 -0000	[thread overview]
Message-ID: <20060420211833.26743.qmail@sourceware.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2762 bytes --]


>Number:         294
>Category:       insight
>Synopsis:       weekly build and 6.4 stable fail to compile under FC5
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 20 21:23:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     markandrews@skylertech.com
>Release:        4.6 and weekly 04-17-06
>Organization:
>Environment:
Linux : 2.6.16-1.2080_FC5   i386
>Description:

trying to build insight-weekly-CVS-6.40.50.20060417

with Linux : 2.6.16-1.2080_FC5 #1 Tue Mar 28 03:38:34 EST 2006 i686 i686 i386 GNU/Linux

gcc -c -g -O2     -I. -I.././gdb -I.././gdb/config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I.././gdb/../include/opcode -I.././gdb/../readline/.. -I../bfd -I.././gdb/../bfd -I.././gdb/../include -I../intl -I.././gdb/../intl  -DMI_OUT=1 -DGDBTK -DTUI=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wformat-nonliteral -Wunused-label -Wunused-function -Wno-pointer-sign -Wuninitialized -Werror p-valprint.c
cc1: warnings being treated as errors
p-valprint.c: In function ‘pascal_object_print_value_fields’:
p-valprint.c:756: warning: ‘tmp_obstack.alloc_failed’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.maybe_empty_object’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.use_extra_arg’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.extra_arg’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.freefun’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.chunkfun’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.alignment_mask’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.temp’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.chunk_limit’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.next_free’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.object_base’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.chunk’ may be used uninitialized in this function
p-valprint.c:756: warning: ‘tmp_obstack.chunk_size’ may be used uninitialized in this function
make[2]: *** [p-valprint.o] Error 1
make[2]: Leaving directory `/home/mandrews/tmp/src/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/home/mandrews/tmp/src'
make: *** [all] Error 2
>How-To-Repeat:
build
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2006-04-20 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 21:23 markandrews [this message]
2006-05-24 18:33 kseitz

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=20060420211833.26743.qmail@sourceware.org \
    --to=markandrews@skylertech.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=mark@andrews.net \
    /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).