Subject: misc/23320: Special shell chars in uname -p output on some system(s)
To: None <gnats-bugs@gnats.NetBSD.org>
From: None <elvstone@home.se>
List: netbsd-bugs
Date: 10/30/2003 21:19:41
>Number: 23320
>Category: misc
>Synopsis: Special shell chars in uname -p output on some system(s)
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: misc-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Oct 30 21:20:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Aron Stansvik
>Release: netbsd-current
>Organization:
>Environment:
Linux abbey 2.6.0-test9 #1 Thu Oct 30 00:05:56 CET 2003 i686 AMD Athlon(tm) AuthenticAMD GNU/Linux
>Description:
I recently tried to cross compile netbsd-current on a Linux system for the first time. uname -p on this Linux system produces: Athlon(tm), this messes up the build process because '(' and ')' are interpreted by the shell. Someone should make the scripts in the build process safe against shell special chars (src/share/mk/bsd.own.mk?).
>How-To-Repeat:
Checkout netbsd-current, try to build a release on a Linux system with uname -p output with shell special chars in it.
>Fix:
Do something nifty in the scripts in src/share/mk I think. (sorry for not being more specific, but I'm sure the people responsible for the scripts know what to do).
>Release-Note:
>Audit-Trail:
>Unformatted: