public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rmathew at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/16814] [win32] libgcj dpends on both winsock32dll and ws2_32.dll
Date: Thu, 29 Jul 2004 06:53:00 -0000	[thread overview]
Message-ID: <20040729065342.22051.qmail@sourceware.org> (raw)
In-Reply-To: <20040729014510.16814.dannysmith@users.sourceforge.net>


------- Additional Comments From rmathew at gcc dot gnu dot org  2004-07-29 06:53 -------
(In reply to comment #0)
> Currently, the inclusion of windows.h in include/win32.h causes the windows 
> socket interface to default to the 2.2 version, since windows.h includes the 
> winsock2.h  header.  That's okay.  However, in libgcj.spec the lib order is:
> 
> *lib: -lgcj -lm     -lgdi32 -lwsock32 -lws2_32 
> 
> ie, the winsock version 1 library is linked in before the winsock 2 libary.  
> Linking in both dll's is dangerous, especially if you assume the version 2 api 
> but link in the version 1 library first.

See:

  http://gcc.gnu.org/ml/java-patches/2002-q4/msg00101.html
  http://gcc.gnu.org/ml/java/2002-10/threads.html#00238

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16814


  parent reply	other threads:[~2004-07-29  6:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29  1:45 [Bug libgcj/16814] New: [mingw32] " dannysmith at users dot sourceforge dot net
2004-07-29  2:04 ` [Bug libgcj/16814] " mckinlay at redhat dot com
2004-07-29  2:19 ` dannysmith at users dot sourceforge dot net
2004-07-29  2:33 ` mckinlay at redhat dot com
2004-07-29  4:51 ` [Bug libgcj/16814] [win32] " pinskia at gcc dot gnu dot org
2004-07-29  6:53 ` rmathew at gcc dot gnu dot org [this message]
2004-07-29 14:46 ` mckinlay at redhat dot com
2004-07-31  2:17 ` dannysmith at users dot sourceforge dot net
2004-07-31 19:27 ` mckinlay at redhat dot com
2004-08-01  4:37 ` dannysmith at users dot sourceforge dot net
2004-08-01  8:43 ` pinskia at gcc dot gnu dot org

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=20040729065342.22051.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).