From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22070 invoked by alias); 29 Jul 2004 06:53:42 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 22052 invoked by uid 48); 29 Jul 2004 06:53:42 -0000 Date: Thu, 29 Jul 2004 06:53:00 -0000 Message-ID: <20040729065342.22051.qmail@sourceware.org> From: "rmathew at gcc dot gnu dot org" To: java-prs@gcc.gnu.org In-Reply-To: <20040729014510.16814.dannysmith@users.sourceforge.net> References: <20040729014510.16814.dannysmith@users.sourceforge.net> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libgcj/16814] [win32] libgcj dpends on both winsock32dll and ws2_32.dll X-Bugzilla-Reason: CC X-SW-Source: 2004-q3/txt/msg00143.txt.bz2 List-Id: ------- 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