From owner-freebsd-java Sun Oct 29 11:30:27 2000 Delivered-To: freebsd-java@freebsd.org Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by hub.freebsd.org (Postfix) with ESMTP id 4234237B479 for ; Sun, 29 Oct 2000 11:30:26 -0800 (PST) Received: from 207-172-201-151.s24.as3.xnb.nj.dialup.rcn.com ([207.172.201.151] helo=unknown.whichever.org) by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.16 #1) id 13py9x-0002QC-00 for freebsd-java@freebsd.org; Sun, 29 Oct 2000 14:30:25 -0500 Received: (from archer@localhost) by unknown.whichever.org (8.11.0/8.9.3) id e9TJUNG75717; Sun, 29 Oct 2000 14:30:23 -0500 (EST) (envelope-from archer) Date: Sun, 29 Oct 2000 14:30:23 -0500 (EST) Message-Id: <200010291930.e9TJUNG75717@unknown.whichever.org> From: Alexander Litvin To: freebsd-java@freebsd.org Subject: Re: Problem with appletviewer in jdk1.2.2b10 In-Reply-To: <200010291708.KAA04295@nomad.yogotech.com> X-Newsgroups: unknown.freebsd.java User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <200010291708.KAA04295@nomad.yogotech.com> you wrote: NW> libgcc is *NOT* supposed to be built shared. However, as you point out, NW> the binaries created by gcc are dependant upon these routines, so they NW> should be linked into the final executable. Right. libgcc.a is supposed to be linked in automatically. That is, without -lgcc given to linker. The problem is that our port _has_ -lgcc flag (see e.g. build/freebsd/java/java/GNUmakefile). My guess is that this causes incorrect dynamic leftover libgcc being linked in (dynamic libraries are looked at first). --- After living in New York, you trust nobody, but you believe everything. Just in case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message