From owner-cvs-all  Thu Sep 17 10:28:44 1998
Return-Path: <owner-cvs-all>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA17846
          for cvs-all-outgoing; Thu, 17 Sep 1998 10:28:44 -0700 (PDT)
          (envelope-from owner-cvs-all)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17835
          for <committers@FreeBSD.ORG>; Thu, 17 Sep 1998 10:28:32 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA23076;
	Fri, 18 Sep 1998 03:28:03 +1000
Date: Fri, 18 Sep 1998 03:28:03 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199809171728.DAA23076@godzilla.zeta.org.au>
To: committers@FreeBSD.ORG, dillon@backplane.com
Subject: Re: /usr/lib/compat/aout not being scanned?
Sender: owner-cvs-all@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>    Even better, though I know people are going to hate this:  Have the
>    ldconfig program automatically look for an 'aout' subdirectory (and add
>    an option to disable the 'feature') so user's original /etc/rc files will
>    still work.

Yes, they are.  gcc does something like this, and it is very confusing.
IIRC, it appends /aout for builtin paths but not for paths in
$LIBRARY_PATH.  It only appends /aout if the aout subdirectory exists.
In some configurations, it then overrides the linker's possibly better
idea of the paths by passing the paths that it finds as -L options.

Bruce