From owner-freebsd-current Fri Sep 4 22:06:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13154 for freebsd-current-outgoing; Fri, 4 Sep 1998 22:06:20 -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 WAA13148 for ; Fri, 4 Sep 1998 22:06:14 -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 AAA06835; Sat, 5 Sep 1998 00:03:12 -0400 (EDT) Date: Sat, 5 Sep 1998 00:03:11 -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: <199809050424.VAA14443@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 Fri, 4 Sep 1998, John Polstra wrote: > I implemented ldconfig functionality for ELF today. If you are > running an ELF system but still rely on some a.out libraries (e.g., > in /usr/X11R6/lib), you may need to adjust your /etc/rc file to avoid > problems. > > The new ldconfig treats ELF and a.out separately. When you run it, > it deals with one format or the other, but not both. The format is > selected by the usual rules involving "/etc/objformat", ${OBJFORMAT}, > and the "-aout" and "-elf" command line options. > > Because of this, if you are on an ELF system the ldconfig invocation > in /etc/rc will suddenly stop affecting your a.out hints, and will > start affecting your ELF hints instead. Thus if you do nothing, > you'll have no a.out hints at all when you reboot. > > A quick work-around is to edit /etc/rc, adding the "-aout" option to > the ldconfig invocation there. It should look like this: > > ldconfig -aout ${_LDC} > > A better solution will involve separate ldconfig directory lists > for a.out and ELF in /etc/rc.conf. I'll commit something along > those lines soon. 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)? Understand the point of this question isn't system libs, its all the ports stuff, which just won't transition in one swell foop like the system did. ----------------------------+----------------------------------------------- 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