From owner-freebsd-current Sat Sep 5 09:24:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09207 for freebsd-current-outgoing; Sat, 5 Sep 1998 09:24:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09199 for ; Sat, 5 Sep 1998 09:24:43 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id LAA11735; Sat, 5 Sep 1998 11:21:42 -0400 (EDT) Date: Sat, 5 Sep 1998 11:21:42 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: John Polstra cc: current@FreeBSD.ORG Subject: Re: ELF -current users: HEADS UP In-Reply-To: <199809051609.JAA22021@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Sep 1998, John Polstra wrote: > > John, many of use have huge time investments in /usr/local/lib and > > /usr/X11R6/lib ports-derived libraries. While I'm definitely going > > to be wanting to transition these to elf, I'd not wanted to have to > > do it suddenly. How will this ldconfig change affect the fact that > > my elf system still must use many aout libs (and probably will for > > some months ahead)? > > If you give it the -aout switch, or if it is running on an a.out > system, or if OBJFORMAT=aout in the environment, the new ldconfig > behaves exactly as it did before. So if you make the change to > /etc/rc that I suggested, you will see no change whatsoever. > > The ldconfig hints for a.out and for ELF are in two completely > separate files. On a mixed system, you can run ldconfig twice: once > with "-aout" and once with "-elf". Presumably you would specify > different directories for the two invocations. The two sets of hints > don't get mixed up with each other. Just pretend like there are two > ldconfig programs, one for a.out and the other for ELF. They don't > really interact with each other at all. > > All clear now? I was hoping you'd think about this from a ports standpoint, actually. I well knew that I could do that locally, but the issue I was trying to raise was the coexistence, for ports, of both aout and elf libs. There isn't any hierarchy defined for ports yet ... Well, I understand it well enough, but I think I'll take it up with Satoshi. I'm wondering if maybe the definitions of where stuff gets installed has to change. Adding in the ldconfig for both elf and aout is going to cause an enormous headache, because there is no global machanism to move the installation targets for libraries. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message