Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Kai Tietz <Kai.Tietz@onevision.com>, GDB <gdb@sources.redhat.com>
Cc: Binutils <binutils@sourceware.org>,
	Brian Dessent <brian@dessent.net>,
		Kai Tietz <ktietz70@googlemail.com>,
		Nick Clifton <nickc@redhat.com>,
		NightStrike <nightstrike@gmail.com>
Subject: Re: PATCH: PR 5715: Binutils is broken on 32bit mingw host for 	64bit target
Date: Mon, 04 Feb 2008 19:59:00 -0000	[thread overview]
Message-ID: <20080204195831.GA12026@lucon.org> (raw)
In-Reply-To: <20080204193935.GA11945@lucon.org>

On Mon, Feb 04, 2008 at 11:39:35AM -0800, H.J. Lu wrote:
> I am applying this patch as an obvious fix. I will check if gdb needs
> update.
> 
> 
> H.J.
> ---
> bfd/
> 
> 2008-02-04  Kai Tietz  <kai.tietz@onevision.com>
> 	    H.J. Lu  <hongjiu.lu@intel.com>
> 
> 	PR 5715
> 	* warning.m4: Enable -Wno-format by default when using gcc on
> 	mingw.
> 	* configure: Regenerated.
> 	

gdb is ok. I missed gprof. I am checking it in now.

H.J.
---
2008-02-04  H.J. Lu  <hongjiu.lu@intel.com>

	PR 5715
	* configure: Regenerated.

--- gprof/configure.ll	2007-10-26 09:49:55.000000000 -0700
+++ gprof/configure	2008-02-04 11:56:33.000000000 -0800
@@ -11222,6 +11222,16 @@ echo "$as_me: error: bad value ${enablev
    esac
 fi;
 
+# Enable -Wno-format by default when using gcc on mingw
+case "${host}" in
+  *-*-mingw32*)
+    if test "${GCC}" = yes -a -z "${ERROR_ON_WARNING}" ; then
+      GCC_WARN_CFLAGS="$GCC_WARN_CFLAGS -Wno-format"
+    fi
+    ;;
+  *) ;;
+esac
+
 # Enable -Werror by default when using gcc
 if test "${GCC}" = yes -a -z "${ERROR_ON_WARNING}" ; then
     ERROR_ON_WARNING=yes


      reply	other threads:[~2008-02-04 19:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080204153803.GA11121@lucon.org>
     [not found] ` <OF87A2F223.26E4FB87-ONC12573E5.0056CF2A-C12573E5.00570F1C@onevision.de>
2008-02-04 19:40   ` H.J. Lu
2008-02-04 19:59     ` H.J. Lu [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=20080204195831.GA12026@lucon.org \
    --to=hjl.tools@gmail.com \
    --cc=Kai.Tietz@onevision.com \
    --cc=binutils@sourceware.org \
    --cc=brian@dessent.net \
    --cc=gdb@sources.redhat.com \
    --cc=ktietz70@googlemail.com \
    --cc=nickc@redhat.com \
    --cc=nightstrike@gmail.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