Date: Tue, 1 Sep 1998 18:11:10 +0200 (CEST) From: Mikael Karpberg <karpen@ocean.campus.luth.se> To: chuckr@glue.umd.edu (Chuck Robey) Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP: Today is E-day Message-ID: <199809011611.SAA08166@ocean.campus.luth.se> In-Reply-To: <Pine.BSF.4.00.9809010942190.353-100000@picnic.mat.net> from Chuck Robey at "Sep 1, 98 09:47:29 am"
next in thread | previous in thread | raw e-mail | index | archive | help
According to Chuck Robey: > > On Tue, 1 Sep 1998, John Birrell wrote: > > > If you haven't already done so, edit /etc/rc and change the _LDC line > > to reference /usr/lib/aout instead of /usr/lib. Once you do that and > > re-run ldconfig (or just reboot), your aout libraries will function > > normally (they are deprecated, though). > > I'm a little confused. I did the upgrade, but I'd had the _LDC pointing > to /usr/lib/aout beforehand, because that's where the new libs were > being put. The upgrade seemed to stick new aout libs in /usr/lib/aout, > but also put new libs in /usr/lib. File doesn't tell me if the ones in > /usr/lib are ELF or not, but from the timestamp on those (which is a few > minutes after the timestamp on the /usr/lib/aout ones) I suspect that > they are. If my system is now ELF, why the advice to add /usr/lib/aout > to my _LDC? Especially since I had already had /usr/lib/aout replacing > /usr/lib in the _LDC, shouldn't I take the "/aout" off now that I've > upgraded? > > Oddly enough, I checked one of my new executeables in /usr/bin, and ldd > tells me that it's linked to libs in /usr/lib, even tho /usr/lib itself > isn't on my _LDC line. I'm a little confused by this. No, it's quite simple. After reading about a hundred posts on this subject I think I have enough info to answer you correctly. :-) Ok... so you already had /usr/lib/aout in there... that's becuase you were running a recent -current. Then you don't need change _LDC. That's just for older systems, who had not yet had their libs moved. The reason you don't need to change _LDC to /usr/lib is because ELF doesn't used ldconfig at all! It's an a.out tool. It's not needed for ELF, and so you don't need to point it at the ELF libs in /usr/lib. You just need to point it at the a.out libs, since it will only be used for compability when you run a.out binaries. ELF binaries don't use lcdonfig, and will find their libs anyway, so you don't need to point ldconfig at the ELF libs because it doesn't get used for ELF things. :-) Ok... did I repeat myself in enough ways there to make it clear to everyone? Let's just hope I didn't screw up and got it wrong, now. :-) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809011611.SAA08166>