From: davidsan AT verity DOT com (Dave Sanderman) Subject: RE: problems linking formats. 25 Mar 1997 15:39:14 -0800 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <01BC38F2.5C260D50.cygnus.gnu-win32@DAVIDSANL> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit Original-To: "'Tim Iverson'" , Boatwright Charles Original-Cc: "gnu-win32 AT cygnus DOT com" X-MIME-Autoconverted: from quoted-printable to 8bit by cygnus.com id IAA06120 Original-Sender: owner-gnu-win32 AT cygnus DOT com BTW, on another note, the standard b17.1 distribution doesn't even come close to building itself under Windows '95. Is everyone building under NT or Unix (most of the problems seem to be bugs in bash)? Is there a long list of caveats someplace? There is absolute no documentation in the 'all' tarball -- gotta scrounge around for it on the web site. i wanted to chime in here with a note about the particular bash [bug|misfeature] that i'm seeing, under both win95 and nt40: on the bash that i have on netcom (sorry, can't check the version # of it right now), the following: % echo foo > out % echo bar >> out % export TESTVAR=`cat out` sets TESTVAR to simply "foo". on b17.1, i'm getting "foo bar" instead. this is preventing any of the configuration scripts supplied with gcc from functioning, so i'm unable to self-host and rebuild gcc. apologies if this is a known issue, but like tim i was unable to find any list of known bash problems. oh, and one other thing, which i'm sure must be a FAQ, but again, i can't find the answer to--how do i stop bash from requiring a /tmp dir for the temp files produced by "cat <