From owner-freebsd-current Sat May 30 21:39:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00416 for freebsd-current-outgoing; Sat, 30 May 1998 21:39:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00404 for ; Sat, 30 May 1998 21:39:06 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id OAA13356; Sun, 31 May 1998 14:47:20 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805310447.OAA13356@cimlogic.com.au> Subject: Re: Undefined symbols referenced In-Reply-To: <199805310204.VAA03255@isua1.iastate.edu> from Kent A Vander Velden at "May 30, 98 09:04:53 pm" To: graphix@iastate.edu (Kent A Vander Velden) Date: Sun, 31 May 1998 14:47:20 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent A Vander Velden wrote: > > While compiling xdelta and gimp-devel on a semi-current system I started > to notice many of applications failing to link. The messages that ld What is a "semi-current system" ?? It looks to me as though you've updated to a -current libc (with weak symbols for the syscalls), but your linker doesn't know about weak symbols. Is that possible? It's surprising. If you run "nm -W /usr/lib/libc.a | grep _read", do you see: 00000008 T __read 00000008 TW _read (plus many other references)? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message