public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libgcj/3694: natPlainDatagramSocketImpl.cc doesn't compile in ALPHA OSF1 Date: Wed, 18 Jul 2001 09:46:00 -0000 [thread overview] Message-ID: <20010718164601.20548.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libgcj/3694; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: ake@purdue.edu Cc: gcc-gnats@gcc.gnu.org Subject: Re: libgcj/3694: natPlainDatagramSocketImpl.cc doesn't compile in ALPHA OSF1 Date: 18 Jul 2001 11:07:25 -0600 >>>>> "Antonio" == ake <ake@purdue.edu> writes: I looked at this PR a little bit. Antonio> ../../../gcc-20010702/libjava/java/net/natPlainDatagramSocketImpl.cc:162: field Antonio> `mreq6' has incomplete type This looks like our test for IPv6 is flawed. I don't currently have access to an OSF machine, so I can't really find out what more we need to check. Antonio> ../../../gcc-20010702/libjava/java/net/natPlainDatagramSocketImpl.cc:230: cannot Antonio> convert `socklen_t*' to `int*' for argument `3' to `int getsockname(int, Antonio> sockaddr*, int*)' This is interesting. This means that your OS has socklen_t but doesn't actually use it in function prototypes. That's bad. Is there some way to request that OSF use socklen_t in prototypes? Sometimes an OS will have some #define that can be enabled to do things like this. Tom
next reply other threads:[~2001-07-18 9:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-18 9:46 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-08-01 10:57 ro 2001-07-27 6:16 Rainer Orth 2001-07-26 15:46 Tom Tromey 2001-07-26 12:00 ro 2001-07-15 21:56 ake
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=20010718164601.20548.qmail@sourceware.cygnus.com \ --to=tromey@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --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: linkBe 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).