From: Randolph Chung <randolph@tausq.org>
To: gdb@sources.redhat.com
Subject: hpux build errors, and -Werror
Date: Wed, 01 Mar 2006 15:23:00 -0000 [thread overview]
Message-ID: <4405BC50.3070603@tausq.org> (raw)
Currently on hppa64-hp-hpux11.11, gdb fails to build with -Werror
because we are not getting the const flag correct with iconv() calls.
gdb's configure script actually has some tests for this, from
acinclude.m4, however, the test doesn't actually work (at least in this
case), because configure doesn't compile the test program with -Werror,
and the resultant warning doesn't trigger the script to define ICONV_CONST
I'm not very good with autoconf & friends and can't figure out the right
way to fix it. Can somebody give me some hints?
On hppa2.0w-hp-hpux11.11, there is a different problem, at least on the
system I'm testing on:
ser-tcp.c:209 has a call to getsockopt. This causes a (fatal) warning:
../../gdb/gdb/ser-tcp.c:209: warning: passing arg 5 of `getsockopt' from
incompatible pointer type
getsockopt is declared as:
extern int getsockopt (int, int, int, void *, int *);
whereas socklen_t is:
typedef long unsigned int size_t
typedef size_t socklen_t;
I would argue the headers are broken on this platform, but nonetheless
we may need to find a way to workaround this in gdb. I can't think of
any good way to do this though.
Comments appreciated.
randolph
reply other threads:[~2006-03-01 15:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4405BC50.3070603@tausq.org \
--to=randolph@tausq.org \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).