From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Nick Clifton <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: Wed, 23 May 2007 13:04:00 -0000 [thread overview]
Message-ID: <46543BE2.1010209@lu.unisi.ch> (raw)
In-Reply-To: <m3odkbity0.fsf@redhat.com>
Nick Clifton wrote:
> Hi Paolo, Hi Alex,
>
> May I ask for your advice on a configure script matter ?
>
> The Binutils bug PR 4334 has pointed out the problems of trying to
> build a toolchain under Cygwin with a build directory mounted in
> text mode. So, I think that it is agreed that toolchains should
> only be built on bin-mounted drives and I would like the configure
> script to make sure that this happens.
>
> I am attaching a provisional patch which I think will do what I
> want, but I would like to get your comments it. I tested the
> patch under both Cygwin and Linux, and it does not appear to
> introduce any new problems, so I am reasonably confident that it
> works. But I am not at all sure that I have used the best approach
> to the problem. Your comments ?
I haven't looked at the patch yet, but as an aside, I think this should
also go into the main autoconf distribution; there is no reason why
somebody should build under a text-mode mounted directory.
Paolo
next prev parent reply other threads:[~2007-05-23 13:04 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 [this message]
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
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=46543BE2.1010209@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--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