From owner-freebsd-java Mon Aug 20 8:18:30 2001 Delivered-To: freebsd-java@freebsd.org Received: from naboo.ethz.ch (naboo.ethz.ch [129.132.17.66]) by hub.freebsd.org (Postfix) with ESMTP id 582C637B417 for ; Mon, 20 Aug 2001 08:18:25 -0700 (PDT) (envelope-from carlo@vis.ethz.ch) Received: by naboo.ethz.ch (Postfix, from userid 224) id C014F275B6; Mon, 20 Aug 2001 17:18:23 +0200 (CEST) Subject: SOLVED: Successful JDK 1.3.1 build with little modification To: freebsd-java@freebsd.org Date: Mon, 20 Aug 2001 17:18:23 +0200 (CEST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010820151823.C014F275B6@naboo.ethz.ch> From: carlo@vis.ethz.ch (Carlo Dapor) Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear Java aficionados Just wanted to let You know that I was able to build the JDK 1.3.1, without the weird setup I posted previously. That's right, not more INSANE or LINK.{c,cc} or the like. It turns out that just uncommenting '-z defs' in make/common/Defs-bsd.mk does all the magic for me. Also, as Greg has mentioned earlier, the generation of invokers.c does not require any hack anymore. The lines around 240 in make/common/Defs-bsd.mk lok like this now: fneq ($(LIBRARY),JdbcOdbc) ifneq ($(ARCH),ppc) LDFLAGS_COMMON = #-z defs endif # LIBRARY endif # ARCH Is my Current shaky, or is anyone else having similar symptoms on Current ? Ciao, derweil, -- Carlo PS: The man pages for gcc mention that '-z defs' is meant to silence warnings of unresolved symbols if switched on. But there seems to be more to it, both system gcc (2.95.1) and most recent gcc (3.0) have the exact same behaviour for me when building the JDK. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message