Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Pierre Muller" <muller@ics.u-strasbg.fr>,
	 "'Eli Zaretskii'" <eliz@gnu.org>,
	 drow@false.org,  brobecker@adacore.com
Subject: Re: [RFC] Improve testsuite for poor expect behavior
Date: Thu, 18 Jun 2009 16:19:00 -0000	[thread overview]
Message-ID: <200906181720.01014.pedro@codesourcery.com> (raw)
In-Reply-To: <001201c9f02d$3ab7d310$b0277930$@u-strasbg.fr>

On Thursday 18 June 2009 16:55:40, Pierre Muller wrote:
>   The objdir is there to avoid translation from relative to absolute
> pathes, which leads to conflits both for mingw32 and djgpp
> as cygwin uses its own root dir and the /cygdrive/X for windows X:\ drive.

The usual recomended way to get around such cygwin x mingw path
issues is to do an "identity" mount (google: cygwin mingw identity mount).

 http://gcc.gnu.org/ml/gcc-patches/2008-03/msg00962.html

so that e.g., /mingw on the cygwin side, and /mingw on the mingw
side point at the same thing.

-- 
Pedro Alves


  parent reply	other threads:[~2009-06-18 16:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 23:00 Pierre Muller
2009-06-13 14:52 ` Doug Evans
2009-06-13 15:05 ` Daniel Jacobowitz
2009-06-13 20:29   ` Pierre Muller
2009-06-13 23:55     ` 'Daniel Jacobowitz'
2009-06-14  0:25       ` Joel Brobecker
2009-06-15  7:23         ` Pierre Muller
2009-06-16 14:58           ` Joel Brobecker
2009-06-16 23:29             ` Pierre Muller
2009-06-17 13:36               ` 'Daniel Jacobowitz'
2009-06-17 14:54                 ` Joel Brobecker
2009-06-17 17:25                   ` Eli Zaretskii
2009-06-17 19:39                     ` Joel Brobecker
2009-06-18 14:38                       ` Eli Zaretskii
2009-06-18 14:59                         ` Joel Brobecker
2009-06-18 15:25                           ` Eli Zaretskii
2009-06-18 15:33                             ` Joel Brobecker
2009-06-18 15:58                               ` Samuel Bronson
2009-06-18 23:02                               ` Eli Zaretskii
2009-06-17 17:17                 ` Eli Zaretskii
2009-06-17 20:17                   ` Pierre Muller
2009-06-17 21:00                     ` Pierre Muller
2009-06-18 14:33                     ` Eli Zaretskii
2009-06-18 15:57                       ` Pierre Muller
2009-06-18 16:08                         ` Pedro Alves
2009-06-18 23:18                           ` Eli Zaretskii
2009-06-18 16:19                         ` Pedro Alves [this message]
2009-06-17 21:56                   ` Pierre Muller
2009-06-18 14:48                     ` Eli Zaretskii
2009-06-17 22:39                 ` Pierre Muller
2009-06-17 22:43                   ` 'Daniel Jacobowitz'
2009-06-17 22:54                     ` Pierre Muller
2009-06-17 23:21                       ` 'Daniel Jacobowitz'
2009-06-17 23:18                     ` Joel Brobecker
2009-06-18  6:31                       ` Mark Kettenis
2009-06-23 18:14               ` Joel Brobecker

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=200906181720.01014.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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