all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sean Sieger <sean.sieger@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: trunk build failure on windows
Date: Sat, 05 Jun 2010 10:51:46 -0400	[thread overview]
Message-ID: <E1OKuiw-0001tY-TO@fencepost.gnu.org> (raw)
In-Reply-To: <83y6et5z2w.fsf@gmail.com> (message from Sean Sieger on Sat, 05 Jun 2010 10:33:11 -0400)

> From: Sean Sieger <sean.sieger@gmail.com>
> Date: Sat, 05 Jun 2010 10:33:11 -0400
> 
> Anyway, maybe I'll hear from ya before I get the time to go back to an
> earlier GCC (will 4.4 work? and can it an 4.5 co-exist in my MinGW?),
> otherwise I'll move back to said earlier GCC.

I think only GCC 4.5 has that problem.

As for coexistence: each version of gcc.exe should be able to find its
own sub-programs (they are installed in different directories whose
name includes the version).  So what I usually do is rename the couple
of executables installed on PATH to something like gcc45.exe and
cpp45.exe, and invoke them by that name when I need.

> And another question, given the compilers co-existance, when I
> configure, do I use the argument say `--with-gcc=4.4' or something?

This is not supported by the current nt/configure.bat.  --with-gcc
means use the compiler named literally "gcc".  You could rename
gcc45.exe to gcc.exe before running configure.bat, though.

(Btw, if the problem is really in GCC 4.5, why would you want to leave
a buggy compiler on your system?  I'd just nuke it.)



  reply	other threads:[~2010-06-05 14:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05  1:48 trunk build failure on windows Sean Sieger
2010-06-05  2:21 ` Eli Zaretskii
2010-06-05  2:44   ` Sean Sieger
2010-06-05  2:50     ` Eli Zaretskii
2010-06-05 14:33       ` Sean Sieger
2010-06-05 14:51         ` Eli Zaretskii [this message]
2010-06-05 17:04           ` Sean Sieger

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=E1OKuiw-0001tY-TO@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sean.sieger@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.