On Fri, Mar 13, 2020 at 01:04:42PM -0400, Ed Maste wrote:
> While looking at other things we came across ldconfig's a.out support,
> which hasn't been used by anything in the FreeBSD base system in ~2
> decades.
>
> I know there are (or at least recently were) folks using a.out
> binaries on conte
## Ian Lepore (i...@freebsd.org):
> 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?
Less code, not more.
Regards,
Christoph
--
Spare Space
___
freebsd-current@
On Fri, 2020-03-13 at 13:34 -0400, Ed Maste wrote:
> On Fri, 13 Mar 2020 at 13:22, Ian Lepore 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 t
On Fri, 13 Mar 2020 at 13:22, Ian Lepore 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 availa
On Fri, 2020-03-13 at 13:04 -0400, Ed Maste wrote:
> While looking at other things we came across ldconfig's a.out
> support,
> which hasn't been used by anything in the FreeBSD base system in ~2
> decades.
>
> I know there are (or at least recently were) folks using a.out
> binaries on contempora
While looking at other things we came across ldconfig's a.out support,
which hasn't been used by anything in the FreeBSD base system in ~2
decades.
I know there are (or at least recently were) folks using a.out
binaries on contemporary FreeBSD. Most likely statically linked
proprietary software. I
