Date: Tue, 3 Jul 2018 11:33:45 +0200 From: Gary Jennejohn <gljennjohn@gmail.com> To: Eitan Adler <lists@eitanadler.com> Cc: "freebsd-arch@freebsd.org" <arch@freebsd.org> Subject: Re: xstr, mkstr Message-ID: <20180703113345.4db68896@ernst.home> In-Reply-To: <CAF6rxgnqEkgq4_FaZasL1z3vx0r1jOG0WGrdnMAXFig%2Byu3WpQ@mail.gmail.com> References: <CAF6rxgkQAuM4%2B=_D0YGWiFj8-2YH548RWOAvbChX8LXL5tq5Mw@mail.gmail.com> <CAF6rxgnqEkgq4_FaZasL1z3vx0r1jOG0WGrdnMAXFig%2Byu3WpQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2 Jul 2018 21:58:43 -0700 Eitan Adler <lists@eitanadler.com> wrote: > On 24 June 2018 at 02:51, Eitan Adler <lists@eitanadler.com> wrote: > > Why are these tools in base? As far as I could tell these tools are > > un-used in the build process and otherwise specialized tools. Is there > > any reason we still have them in the toolchain or in base? > > Anyone? They don't cause acute problems, but having specialized and > specific tools like this don't seem like they belong. > Reading the man pages it appears that these are old baggage left over from the PDP/VAX legacy of BSD. Their whole prupose was to reduce the memory consumed by strings in binaries on machines with little RAM. In fact, the BUGS section of mkstr(1) makes this very clear. xstr is actually used in /usr/src/contrib/bmake/mk/prog.mk. I can't tell whether this file is ever invoked. It's commented out in some other makefiles. There's a test for mkstr in /usr/src/contrib/netbsd-tests/lib/libc/regex/t_exhaust.c. Both are in /usr/src/usr.sbin/crunch/examples/really-big.conf. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180703113345.4db68896>