From owner-freebsd-ports Thu Aug 20 01:03:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12453 for freebsd-ports-outgoing; Thu, 20 Aug 1998 01:03:48 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12446; Thu, 20 Aug 1998 01:03:45 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca10-63.ix.netcom.com [205.186.214.63]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id BAA11239; Thu, 20 Aug 1998 01:03:03 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id BAA04304; Thu, 20 Aug 1998 01:02:51 -0700 (PDT) Date: Thu, 20 Aug 1998 01:02:51 -0700 (PDT) Message-Id: <199808200802.BAA04304@silvia.hip.berkeley.edu> To: jb@cimlogic.com.au CC: jb@cimlogic.com.au, ports@FreeBSD.ORG, jdp@FreeBSD.ORG In-reply-to: <199808200753.RAA05170@cimlogic.com.au> (message from John Birrell on Thu, 20 Aug 1998 17:53:53 +1000 (EST)) Subject: Re: ELF transition for ports (Re: rayshade port) From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * No. I mean when they `make aout_to_elf'. It's a special upgrade that * does two buildworlds. The first is aout to get known good tools; the second * uses the aout tools in the tmp tree to build the world in elf format. * Then an aout installworld puts all the aout things in place, followed * by an elf installworld which will over write common things. For people * upgrading from 2.2.5/6/7 there is also a kernel build because without * that they're hosed. Wow. * > Ok. I'm not sure what bsd.port.mk has to do, though. It's the * > individual ports that need to be OBJFORMAT (not OSREL as I said * > before) aware. * * I'm not convinced that is true. 8-) I have to prove myself right or * wrong. Well, tell me what you find, ok? :) * By "normal", I mean do they execute cc, ld, ar, etc without specifying * the path to the executable? If they just let the user's PATH find * /usr/bin/ld, for instance, the fact that /etc/objectformat contains * the line OBJFORMAT=elf will be enough to get /usr/libexec/elf/ld as * the linker automagically. I thought they have different command line arguments to specify that they're building shared libs, etc. (At least that's what I think msmith said when I met him last week. I couldn't really hear well so I might be wrong, though.) At the least, the output filename is different (elf shlibs don't have the minor, right?). * > For consumers of libraries, no, I don't think it's too different. I'm * > worried about ports that generate libraries. Speaking of which, is * > XFree86 ready for FreeBSD-elf? (Will x11/XFree86 port build elf * > libraries and binaries if OBJFORMAT=elf? :) * * I doubt that anyone has asked that. I'll try building their code * and see what's involved. Someone better ask them. It's going to suck if users tried to build an ELF executable on a supposedly ELF-based 3.0 release and it blows up in their face because XFree86 libs are a.out only. :> * > If it breaks a lot of ports, maybe that will give people extra * > incentives to fix them. :) * * Now if I said that, I'd get yelled at! 8-) But I'm not you, so I can say it. :p * > By the way, is 3.0R going to ship with a.out shared libraries too? * * Yes. Otherwise we break too many third party programs that people haven't * got the sources to rebuild. I see. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message