From owner-freebsd-current Thu Dec 31 11:22:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07720 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:22:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gaylord.async.vt.edu (gaylord.async.vt.edu [128.173.18.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07707 for ; Thu, 31 Dec 1998 11:22:39 -0800 (PST) (envelope-from gaylord@gaylord.async.vt.edu) Received: (from gaylord@localhost) by gaylord.async.vt.edu (8.9.1/8.8.5) id OAA39518 for freebsd-current@freebsd.org; Thu, 31 Dec 1998 14:24:43 -0500 (EST) From: Clark Gaylord Message-Id: <199812311924.OAA39518@gaylord.async.vt.edu> Subject: Re: New aout-to-elf build failures. To: freebsd-current@FreeBSD.ORG Date: Thu, 31 Dec 1998 14:24:42 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL31 (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 > Subject: Re: New aout-to-elf build failures. > Date: Wed, 30 Dec 1998 21:11:22 -0800 > From: "Jordan K. Hubbard" > > > Ok, as I'm not and haven't done any of the work I certainly don't have any > > say, but just to add something that you might want to consider. I've been > > thinking that it would be nice if the aout to elf build would be supported > > till a little after the branch split. This would allow people following > > stable the option of source upgrades the whole way through. But maybe this > > adds to much "cruft" to the start of the new stable branch? > > I don't mind them following -current up to and after the branch, but > they need to go ELF before that. It's just getting too difficult to > support both worlds and I no longer even have a 3.0/a.out box handy > here for testing such an environment. I have a stupid question: how do I know if I have an elf box? Maybe this is really trivial, but when I explain my confusion maybe it won't make me look quite so stupid (more foolish maybe, but hopefully not so stupid ;-): I tried aout-to-elf rather prematurely and it failed miserably; I then did a number of especially stupid things to try to kludge around the problem; finally, with a barely hobbling system I dl'ed a binary distribution, did a make world, make aout-to-elf, etc. Interestingly, /etc/objformat still said AOUT, but all the .../lib stuff seemed to be elf, so I just manually overwrote that. Anyway... But I still have a bunch of stuff in .../lib/aout (and maybe some aout stuff in .../lib ... I told you I did some stupid stuff). Do I have an "elf" system in the Hubbard sense of the word? I've tried moving stuff out of .../lib/aout when there were updated libs in .../lib, but there's a lot of "hey, I need blah.k (notwithstanding that blah.l is in elf for some l>k)" and subsequent rebuilds of almost everything on my system. But I can't build netscape (which seems to want the older libs I have in a.out). I also use X in binary; is that a.out or elf (I use the 3.0 binaries; don't have room for sources anymore). Can I transliterate the aout stuff and get it to work? (Maybe this was supposed to have been done by aout-to-elf, but my numerous fuddlings probably fubar'ed it.) Part of my problem is that I really don't understand a.out vs elf. Is there something I can read to better describe the different formats and how libraries are located (e.g., why do I need to have blah.k when I now have blah.l?) I'm not really much of a hacker, just a user that doesn't mind getting a little bloody every now and then. Thanks, CLark -- Clark K. Gaylord Blacksburg, Virginia USA cgaylord@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message