Subject: RE: problems linking formats.
From: [email-masked] (Dave Sanderman)

25 Mar 1997 15:39:14 -0800
Approved: [email-masked]
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'" <[email-masked]>,
        Boatwright Charles
	 <[email-masked]>
Original-Cc: "[email-masked]" <[email-masked]>
X-MIME-Autoconverted: from quoted-printable to 8bit by cygnus.com id IAA06120
Original-Sender: [email-masked]

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 <<EOF"?  no amount of environment var fiddling seemed to save me...

thanks in advance...
  dave sanderman -- [email-masked]

-
For help on using this list, send a message to
"[email-masked]" with one line of text: "help".