public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "emachado at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/13835] Build fails on SLES 10 (PPC)
Date: Tue, 31 Jul 2012 15:55:00 -0000	[thread overview]
Message-ID: <bug-13835-4717-1nthJKVQjV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13835-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13835

Edjunior Machado <emachado at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |emachado at sourceware dot
                   |                            |org

--- Comment #3 from Edjunior Machado <emachado at sourceware dot org> 2012-07-31 15:54:52 UTC ---
I also confirm this is still happening on upstream gdb. This seems to be due to
an old version of flex on SLES10 (flex 2.5.31), and is not reproducible if
you're using 2.5.35.
As suggested by Andreas, './configure --disable-werror' also avoids the
problem.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


      parent reply	other threads:[~2012-07-31 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 15:43 [Bug build/13835] New: " chris.january at allinea dot com
2012-07-19 12:07 ` [Bug build/13835] " rguenther at suse dot de
2012-07-19 12:22 ` schwab@linux-m68k.org
2012-07-31 15:55 ` emachado at sourceware dot org [this message]

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=bug-13835-4717-1nthJKVQjV@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).