From owner-freebsd-alpha Wed Dec 4 15:51:22 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09EF537B401 for ; Wed, 4 Dec 2002 15:51:21 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAF2243EAF for ; Wed, 4 Dec 2002 15:51:20 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 9E1672A7EA; Wed, 4 Dec 2002 15:51:20 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Andrew Gallatin , "alex" , "Yoriaki FUJIMORI" , alpha@FreeBSD.ORG Subject: Re: link_elf: symbol osf1_wait4 undefined In-Reply-To: <20021204234429.1E7DE2A8A5@canning.wemm.org> Date: Wed, 04 Dec 2002 15:51:20 -0800 From: Peter Wemm Message-Id: <20021204235120.9E1672A7EA@canning.wemm.org> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Peter Wemm wrote: > Andrew Gallatin wrote: > > > > alex writes: > > > ahhhh. That solved the problem. > > > What is the technical reason for having to load the osf1 module first ? > > > > Linux/alpha uses the same ABI as OSF/1 for a number of functions, > > since they bootstrapped themselves from OSF/1 on alpha and never > > bothered to go fully native. This ABI is already provided by our > > osf1.ko module. > > > > The problem is that the osf1.ko module is SUPPOSED to be automatically > > loaded as a dependancy of the linux module. I've asked the person who > > wrote the module dependancy code for help on this, but he's moved on > > to other things and has never answered. If somebody wants to look > > into this, that would be great. I've never been able to figure it > > out. > > This is quite well solved in 5.0: ... > > There is no good solution for 4.x because the dependency system runs at > the file level (rather than module level) and cannot detect when a module > is already in the kernel. I've just realized that the 4.x tree has also had the MODULE_VERSION and MODULE_DEPEND stuff MFC'ed. The problem is that they are just stubs in RELENG_4. Maybe this is the source of confusion - those lines do absolutely nothing on 4.x. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message