Subject: toolchain/25835: xstr(1) and therefore SHAREDSTRINGS in bsd.prog.mk are both broken
To: None <gnats-bugs@gnats.netbsd.org>
From: None <fair@netbsd.org>
List: netbsd-bugs
Date: 06/05/2004 20:27:44
>Number: 25835
>Category: toolchain
>Synopsis: xstr(1) and therefore SHAREDSTRINGS in bsd.prog.mk are both broken
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: toolchain-manager
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jun 06 03:28:01 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: Erik E. Fair
>Release: NetBSD 2.0
>Organization:
UNIX Hackers with Long Memories
>Environment:
n/a
>Description:
The scourge of bitrot, an evolving C standard, and a pickier
gcc have conspired to allow a useful old utility to fall
into disrepair: xstr(1).
Frank was grumbling about how fat ftp(1) is and how reducing
the number of strings in it would help make it an easier
fit on installation media. I remembered xstr(1) from my
days using 2.8BSD on DEC PDP-11/70, and lo! It's still in
our distribution!
Alas, it no longer produces valid output so far as gcc is concerned.
See
http://mail-index.netbsd.org/current-users/2003/11/07/0023.html
and
http://mail-index.netbsd.org/current-users/2003/12/04/0011.html
We should fix it, or pitch it. I recommend fixing it, as
the problem that this tool attempts to solve is ever with us.
This also affects /usr/share/mk/bsd.prog.mk also, because support
for using xstr(1) is optionally available therein under the define
SHAREDSTRINGS.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: