Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] new tcp_open
Date: Thu, 20 Dec 2001 03:04:00 -0000	[thread overview]
Message-ID: <3C21C5AC.6090809@cygnus.com> (raw)
In-Reply-To: <200112200816.AAA24102@cygnus.com>

> Those warnings were always there.  My patch reverted those lines back
> to what was there before.  However, it does appear that changing the char * 
> cast to a void * would eliminate the warning and should probably work 
> everywhere.  Systems that based their sockets on very old BSD have char * 
> instead of void * in their setsockopt prototypes.


Can I suggest either removing the cast or making it ``void *'' with a 
comment to the effect that looser OS's such as solaris 2.5.1 have a 
``char*'' as that argument.

Modern OS's and the Single UNIX spec have ``void *'' as the parameter - 
I checked Red Hat 7.2 and NetBSD 1.5.2 and Solaris 2.7.

http://www.opengroup.org/onlinepubs/007908799/xns/getsockopt.html


> I tested void * on Linux and Windows and neither complain.  I have been
> trying all day on a Solaris box, but it just can't seem to compile
> GDB in less than a couple of days.  How can a big Ultrasparc with
> a load average of 0.08 take > 12 hours to build GDB???


configure appears to be getting really slow again :-/

Andrew


  reply	other threads:[~2001-12-20 11:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 11:18 Martin M. Hunt
2001-12-03 12:02 ` Andrew Cagney
2001-12-03 13:26   ` Martin M. Hunt
2001-12-03 13:36     ` Andrew Cagney
2001-12-03 22:13       ` Martin M. Hunt
2001-12-18  2:41 ` Orjan Friberg
2001-12-18  2:57   ` Martin M. Hunt
2001-12-18  3:22     ` Andrew Cagney
2001-12-18 12:29       ` Martin M. Hunt
2001-12-19 15:32         ` Elena Zannoni
2001-12-20  3:39           ` Martin M. Hunt
2001-12-20  3:04             ` Andrew Cagney [this message]
2001-12-18  3:40     ` Orjan Friberg

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=3C21C5AC.6090809@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=ezannoni@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hunt@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