From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Compile fix for 64-bit HPUX
Date: Tue, 28 Mar 2006 22:27:00 -0000 [thread overview]
Message-ID: <20060328221249.GD10392@nevyn.them.org> (raw)
In-Reply-To: <44264D9D.5070305@tausq.org>
On Sun, Mar 26, 2006 at 04:15:25PM +0800, Randolph Chung wrote:
> On 64-bit HPUX, gdb fails to compile with -Werror because of an
> incorrect iconv() prototype. gdb's configure script checks for this, but
> because the configure script test is compiled without -Werror even when
> -Werror is enabled, the test doesn't detect the condition properly. The
> attached patch forces this test to use the value of WERROR_CFLAGS so
> that the check uses the same flags that will be used to build gdb.
>
> tbh I think this is really a hack and we should somehow make all the
> autoconf test use the -Werror flag when running the compile tests, but
> it's not obvious to me how I can do this without redoing a lot of the
> Makefile logic (for example, why do we use a separate WERROR_CFLAGS and
> not just append the -Werror into CFLAGS?)...
So that we can turn off -Werror without turning off warnings, I
presume. I thought I'd touched this code recently but I don't see
where...
Don't most autoconf checks fail if they produce a warning, anyway?
Oh, that's got a separate knob: AC_LANG_WERROR. Maybe that would help
you. And AC_PROG_CPP_WERROR. I don't know why no one uses
AC_LANG_WERROR in src yet; maybe there's a good reason.
> + oldcflags="${CFLAGS-}"
What's ${foo-}? I don't see it in my bash or dash docs.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-28 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 10:16 Randolph Chung
2006-03-28 22:27 ` Daniel Jacobowitz [this message]
2006-03-29 0:18 ` Andreas Schwab
2006-03-30 0:05 ` Daniel Jacobowitz
2006-03-30 13:05 ` Andreas Schwab
2006-03-30 13:37 ` Randolph Chung
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=20060328221249.GD10392@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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