public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX Coudert <fxcoudert@gmail.com>
To: Christopher Faylor <me@cgf.cx>
Cc: gcc@gcc.gnu.org,  dannysmith@users.sourceforge.net,
	 patch <gcc-patches@gcc.gnu.org>,
	ian@airs.com
Subject: Re: PING [4.1 regression, patch] build i686-pc-mingw32
Date: Tue, 19 Jul 2005 20:03:00 -0000	[thread overview]
Message-ID: <42DD5C82.4040502@gmail.com> (raw)
In-Reply-To: <20050719195238.GB23513@trixie.casa.cgf.cx>

> I'd prefer that Danny review this but neither of us has the right to
> approve this patch.

Well, then, who has the right to approve such a patch?

> However, it seems like you're adding extra stuff to the Makefile where
> it is already trying to do the right thing if $(LN) fails.  Couldn't LN
> just be declared as "cp" for mingw or, alternatively, couldn't it be
> defined as some failing command so that the cp in the failing condition
> would be invoked?

Well, perhaps I wasn't clear enough on what is the problem:

-	case "$<" in \
-	  ./*) ;; \
-	  ../*) \
-	     echo $(LN) $< as$(exeext); \
-	     $(LN) $< as$(exeext) || cp $< as$(exeext) ;; \
-	  *) echo '#!$(SHELL)' > as; echo 'exec $< "$$@"' >> as ; \
-	     chmod +x as ;; \
+	case "$(build)" in \
+	  *mingw32*) \
+	    cp $< as$(exeext) ;; \
+	  *) \
+	    case "$<" in \
+	      ./*) ;; \
+	      ../*) \
+	        echo $(LN) $< as$(exeext); \
+	        $(LN) $< as$(exeext) || cp $< as$(exeext) ;; \
+	      *) echo '#!$(SHELL)' > as; echo 'exec $< "$$@"' >> as ; \
+	        chmod +x as ;; \
+	    esac \

The cases with ./*) and ../*) already well handled, and just kept "as 
is" when $(build) is mingw32. The $(LN) command succeeds, that's not the 
problem.

Only the remaining case, which creates a shell script, fails on mingw32. 
The shell script is spawned to call the assembler, which fails. Only 
real win32 executables can be spawned.

FX

  reply	other threads:[~2005-07-19 20:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19  9:07 FX Coudert
2005-07-19 19:52 ` Christopher Faylor
2005-07-19 20:03   ` FX Coudert [this message]
2005-07-19 20:14     ` Christopher Faylor
2005-07-19 20:21       ` Daniel Jacobowitz
2005-07-21  2:10         ` Christopher Faylor
2005-07-21  2:14           ` Daniel Jacobowitz
2005-07-21  2:25           ` DJ Delorie
2005-07-21  2:40             ` Christopher Faylor
2005-07-21  2:58               ` Daniel Jacobowitz
2005-07-21  2:58               ` DJ Delorie
2005-07-21  3:00                 ` Daniel Jacobowitz
2005-07-21  3:27                   ` DJ Delorie
2005-07-21  3:05                 ` Christopher Faylor
2005-07-21  3:36                   ` DJ Delorie
2005-07-21  3:27                     ` Christopher Faylor
2005-07-25 13:38                       ` François-Xavier Coudert
2005-07-25 15:22                         ` Christopher Faylor
2005-07-25 20:49                           ` DJ Delorie
2005-07-25 21:09                             ` Christopher Faylor
2005-07-25 21:24                               ` DJ Delorie
2005-07-25 21:33                                 ` Christopher Faylor
2005-07-25 22:06                                   ` Danny Smith
2005-09-15  0:47                                   ` Christopher Faylor
2005-07-26  7:38                             ` Paolo Bonzini
2005-07-21  6:55                   ` Paolo Bonzini
2005-07-21  6:20 Ross Ridge
2005-07-21 16:19 ` DJ Delorie
2005-07-21 17:32   ` Ross Ridge
2005-07-21 17:48     ` DJ Delorie
2005-07-21 18:17       ` Ross Ridge
2005-07-22 18:34         ` Mark Mitchell
2005-07-22 20:15           ` Ross Ridge
2005-07-22 20:22             ` Mark Mitchell

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=42DD5C82.4040502@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=dannysmith@users.sourceforge.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=ian@airs.com \
    --cc=me@cgf.cx \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).