From: DJ Delorie <dj@redhat.com>
To: nickc@redhat.com
Cc: bonzini@gnu.org, aoliva@redhat.com, binutils@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: RFC: Adding a check to the top level configure script for a binary-mounted cygwin-hosted build directory
Date: Thu, 24 May 2007 15:43:00 -0000 [thread overview]
Message-ID: <200705241542.l4OFgi0v023645@greed.delorie.com> (raw)
In-Reply-To: <4655AEA3.7080309@redhat.com> (message from Nick Clifton on Thu, 24 May 2007 16:26:27 +0100)
> Are the problems described in PR 4334 also present when building
> under MinGW or DJGPP ? If not, then we can keep this new autoconf
> test as a Cygwin specific test.
I don't have a djgpp build tree at the moment, but djgpp is like
*always* having text mounts. So, you can simulate it with a cygwin
install where everything is text mounted. However, DJGPP's tools know
about CR/LF so it may not expose this "bug".
> If those problems are also present then I would agree with you that
> we need to fix the binutils build process.
IMHO the bug is that cygwin's bash isn't dealing with `` line endings
properly. It's the responsibility of the shell to strip trailing line
endings (1003.2-1992 3.6.3, although it doesn't mention
platform-specific line endings) during command substitution.
Also, cygwin's bash should allow CR/LF pairs as word delimiters during
splitting, if it doesn't already. Cygwin supports mixed mounts, it
needs to deal with the ramifications itself.
next prev parent reply other threads:[~2007-05-24 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 12:52 Nick Clifton
2007-05-23 13:04 ` Paolo Bonzini
2007-05-24 9:47 ` Nick Clifton
2007-05-24 14:27 ` DJ Delorie
2007-05-24 15:26 ` Nick Clifton
2007-05-24 15:43 ` DJ Delorie [this message]
2007-05-25 9:47 ` Corinna Vinschen
2007-05-25 12:15 ` Eric Blake
2007-05-24 18:26 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200705241542.l4OFgi0v023645@greed.delorie.com \
--to=dj@redhat.com \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox