From owner-freebsd-bugs  Fri Mar  1 02:40:04 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA03217
          for bugs-outgoing; Fri, 1 Mar 1996 02:40:04 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA03191
          Fri, 1 Mar 1996 02:40:02 -0800 (PST)
Date: Fri, 1 Mar 1996 02:40:02 -0800 (PST)
Message-Id: <199603011040.CAA03191@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: bin/1052: /bin/sh problem with new GCC (snapshot for 2.8)
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-bugs@FreeBSD.ORG
Precedence: bulk

The following reply was made to PR bin/1052; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: FreeBSD-gnats-submit@FreeBSD.ORG, tege@matematik.su.se
Cc:  Subject: Re: bin/1052: /bin/sh problem with new GCC (snapshot for 2.8)
Date: Fri, 1 Mar 1996 21:29:09 +1100

 >The /bin/sh of FreeBSD doesn't work as on other systems, or like bash.
 >The problem seems to be with the builtin `eval'.
 
 >>How-To-Repeat:
 
 >bash$ foo=tomte; var=foo; echo `eval echo \\$$var`
 >tomte
 >sh$ foo=tomte; var=foo; echo `eval echo \\$$var`
 >5578var
 
 This is fixed in the following versions of ash:
 
 	the one in FreeBSD-1.1.5
 	the original one + assorted fixes from various places
 	the one in BSD-4.4lite2
 
 Bruce