public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "kris dot van dot hees at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4172] New: Add option to configure to disable warnings-as-errors behaviour
Date: Thu, 08 Mar 2007 17:11:00 -0000	[thread overview]
Message-ID: <20070308171128.4172.kris.van.hees@oracle.com> (raw)

In order to support being able to test functionality, even in the event of
warnings being generated during the build process, configure should get an
option to disable the warnings-as-errors behaviour in all parts of the build. 
Doing it as a configure option ensures that as the build process changes over
time, this behaviour will remain consistent.

As a first use of this functionality in configure, the autobuild environments
can perform builds with and without the warnings-as-errors setting, providing
testing both on the level of correct code, and on the level of correct
functionality.

-- 
           Summary: Add option to configure to disable warnings-as-errors
                    behaviour
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: kris dot van dot hees at oracle dot com


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


             reply	other threads:[~2007-03-08 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 17:11 kris dot van dot hees at oracle dot com [this message]
2007-03-08 23:52 ` [Bug general/4172] " kris dot van dot hees at oracle dot com

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=20070308171128.4172.kris.van.hees@oracle.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@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).