From: davidsan AT verity DOT com (Dave Sanderman) Subject: RE: RE: problems linking formats. 26 Mar 1997 16:48:40 -0800 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <01BC39D0.3E4BB120.cygnus.gnu-win32@DAVIDSANL> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Original-To: "'chet AT po DOT cwru DOT edu'" Original-Cc: "gnu-win32 AT cygnus DOT com" Original-Sender: owner-gnu-win32 AT cygnus DOT com >> sets TESTVAR to simply "foo". on b17.1, i'm getting >> >> "foo >> bar" >> >> instead. > The latter value is correct. Since you don't have the version of bash > that's running on netcom, it's possible that this was a bug fixed in > a more current version of bash. Bash versions 1.14.6 and 1.14.7 get > this right. well, then something else is hosed in the gcc config process. basically, config.sub (i think, my cygnus install is at home, so i'm going a little from memory here) always returns "i386-cygwin32 i386-cygwin32" for all its calls in ./configure, so all the set TARGET=`config.sub` type constructions set TARGET to the two-line entity. then, the TARGET vars are substituted into sed scripts, causing stuff like "s/foo/i386-cygwin32 i386-cygwin32/" which sed (rightly?) barfs on. has anybody gotten this to work with b17.1? was there another step that i missed? dave - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".