From: Eli Zaretskii <eliz@gnu.org>
To: Nick Clifton <nickc@redhat.com>
Cc: dj@redhat.com, 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 18:26:00 -0000 [thread overview]
Message-ID: <ufy5mhycq.fsf@gnu.org> (raw)
In-Reply-To: <4655AEA3.7080309@redhat.com> (message from Nick Clifton on Thu, 24 May 2007 16:26:27 +0100)
> Date: Thu, 24 May 2007 16:26:27 +0100
> From: Nick Clifton <nickc@redhat.com>
> CC: bonzini@gnu.org, aoliva@redhat.com, binutils@sourceware.org, gdb-patches@sourceware.org
>
> >> I agree, I think it would be very good to have this check available in
> >> the main autoconf sources.
> >
> > Except that it would penalize MinGW and DJGPP since they don't have a
> > "binmode" concept. We've put a lot of work into keeping track of
> > binary vs text files, why give up on it now?
>
> 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 think such problems cannot happen with DJGPP or MinGW, so this test
should be kept as Cygwin-specific one.
I agree with DJ that the Cygwin tools had better handle this EOL
problem no matter what's the mount mode, but if Cygwin folks don't
feel like going that way, and think it's okay to force binmode mounts
in this situation, I don't see why we should object.
prev parent reply other threads:[~2007-05-24 18:26 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
2007-05-25 9:47 ` Corinna Vinschen
2007-05-25 12:15 ` Eric Blake
2007-05-24 18:26 ` Eli Zaretskii [this message]
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=ufy5mhycq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=dj@redhat.com \
--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