public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jap3003+gcc@ksu.edu,
	nobody@gcc.gnu.org, rodrigc@gcc.gnu.org
Subject: Re: c++/3688: Somehow, an int is getting involved when getting sizeof a struct sockaddr variable.
Date: Sun, 02 Sep 2001 02:03:00 -0000	[thread overview]
Message-ID: <20010902090303.14520.qmail@sourceware.cygnus.com> (raw)

Synopsis: Somehow, an int is getting involved when getting sizeof a struct sockaddr variable.

State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Sun Sep  2 02:03:03 2001
State-Changed-Why:
    I don't think gcc is at fault.
    Between Solaris 2.6 and 2.8, the function prototype
    of a lot of the socket functions like accept() have
    changed to accept socklen_t.  This was done in accordance
    with the Single Unix Specification, version 2:
    http://www.opengroup.org/onlinepubs/007908799/xns/accept.html
    
    The reason for having socklen_t instead of int, is to have
    networking code which works correctly on 64-bit and 32-bit
    platforms.
    
    You need to report this problem to the mozilla project,
    where they need to fix their socket code so that it works
    on platforms which use socklen_t, and on platforms without
    socklen_t.
    
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3688&database=gcc


             reply	other threads:[~2001-09-02  2:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-02  2:03 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-02 16:36 rodrigc
2001-12-02 16:27 rodrigc
2001-07-15 12:06 Joseph Pingenot
2001-07-14 17:16 Carlo Wood
2001-07-14 16:46 jap3003+gcc

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=20010902090303.14520.qmail@sourceware.cygnus.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jap3003+gcc@ksu.edu \
    --cc=nobody@gcc.gnu.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).