Date: Fri, 13 Mar 2020 11:43:08 -0600 From: Ian Lepore <ian@freebsd.org> To: Ed Maste <emaste@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Any a.out users? Message-ID: <344ed2da70379a40198353271cdb23beb455096e.camel@freebsd.org> In-Reply-To: <CAPyFy2AWge6G2DNXJ%2BTwM-aV_j4FF-2oT7XtF42SCMoKAqt9yg@mail.gmail.com> References: <CAPyFy2CmZO_eDFTMhk0TO8QbN9H%2BnE5KVk058MyjhqtNcPy-RA@mail.gmail.com> <177f99391d35483369bd43a2be1e994d07697e17.camel@freebsd.org> <CAPyFy2AWge6G2DNXJ%2BTwM-aV_j4FF-2oT7XtF42SCMoKAqt9yg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2020-03-13 at 13:34 -0400, Ed Maste wrote: > On Fri, 13 Mar 2020 at 13:22, Ian Lepore <ian@freebsd.org> wrote: > > > > Could a.out support be a kernel config option that's off by > > default? > > Probably. That seems reasonable to me. > > > And could its presence be indicated via sysctl in some way, so that > > ldconfig could do a.out hints only if support for them is > > available? > > But why does ldconfig need to know about a.out files at all? Assuming > this support still works we can just provide an a.out ldconfig along > with a.out shared libraries. > Oh, that makes sense... if the libs are conditionally installed, an ldconfig_aout could also be conditionally installed. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?344ed2da70379a40198353271cdb23beb455096e.camel>