RE: problems linking formats.

RE: problems linking formats.

[Dave Sanderman]

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 -- davidsan@verity.com

-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: RE: problems linking formats.

[Chet Ramey]

You know, you should really insert newlines into your mail messages.

> 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.

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.

>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... 

Bash, as it stands today, requires /tmp.  There are a couple of things
you could do to change it, both requiring modifications to execute_cmd.c.

The easier of the two is to change the code in do_redirection_internal
that handles redirections of types `r_reading_until' and
`r_deblank_reading_until' to look for and use, if found, the value of
a `TMPDIR' variable instead of /tmp, defaulting to /tmp if TMPDIR is
not set.

The second, somewhat more complex, approach is to dispense with a temp
file altogether and use a pipe.  Bash would create a pipe and fork a child.
The child would close the read end of the pipe and stuff the text of
the here document into the write end.  The parent would close the write
end, dup the read end of the pipe to file descriptor 0 for the `cat'
process, and close the read end.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, Case Western Reserve University	Internet: chet@po.CWRU.Edu
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

RE: RE: problems linking formats.

[Dave Sanderman]

>> 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@cygnus.com" with one line of text: "help".