Re: Any a.out users?
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 contemporary FreeBSD. Most likely statically linked > proprietary software. I'd be curious to know if anyone is still using > this. > > As far as ldconfig goes I don't see the value in generating a.out > hints; if someone is using a.out shared libraries (from FreeBSD 2.x) > it seems that they can also just use FreeBSD 2.x ldconfig to generate > the hints file. Is there any reason we shouldn't deprecate ldconfig > a.out support? There is also ldd(1) to clean if doing such cleanup. I agree with the statement that if you need to do anything that requires ldd/ldconfig for a.out, you really need to have the chroot with FreeBSD 2.2.x world around. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Any a.out users?
## 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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Any a.out users?
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 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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Any a.out users?
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 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. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Any a.out users?
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 contemporary FreeBSD. Most likely statically linked > proprietary software. I'd be curious to know if anyone is still using > this. > > As far as ldconfig goes I don't see the value in generating a.out > hints; if someone is using a.out shared libraries (from FreeBSD 2.x) > it seems that they can also just use FreeBSD 2.x ldconfig to generate > the hints file. Is there any reason we shouldn't deprecate ldconfig > a.out support? Could a.out support be a kernel config option that's off by default? 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? -- Ian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Any a.out users?
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'd be curious to know if anyone is still using this. As far as ldconfig goes I don't see the value in generating a.out hints; if someone is using a.out shared libraries (from FreeBSD 2.x) it seems that they can also just use FreeBSD 2.x ldconfig to generate the hints file. Is there any reason we shouldn't deprecate ldconfig a.out support? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
