caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dave Benjamin <dave@ramenlabs.com>
To: Alain Frisch <alain@frisch.fr>
Cc: Alan Schmitt <alan.schmitt@polytechnique.org>, caml-list@inria.fr
Subject: Re: [Caml-list] Problem during Godi bootstrap_stage2 (Windows mingw)
Date: Thu, 19 Mar 2009 07:30:56 -0700	[thread overview]
Message-ID: <49C25720.2040800@ramenlabs.com> (raw)
In-Reply-To: <49C1F8AC.7030705@frisch.fr>

Alain Frisch wrote:
> Alan Schmitt wrote:
>> I had to reinstall my environment to develop OCaml applications under 
>> Windows (using mingw), and I'm having some problem during 
>> bootstrap_stage2. Here are the last few lines before the problem occurs:
> 
> I think the problem comes from a recent update in Cygwin. Now, gcc is a 
> (Cygwin) symbolic link to gcc3.exe. Cygwin applications (like bash or 
> make) are able to follow symlinks, but not native Win32 applications 
> (like ocamlrun).
> 
> A solution is to copy gcc3.exe to gcc.exe in a directory which is put in 
> front of the PATH. Same for cpp.

I ran into this problem as well. My solution was basically what you 
described:

cd /usr/bin
mv gcc.exe gcc.exe.cygwin
cp gcc-3.exe gcc.exe
mv cpp.exe cpp.exe.cygwin
cp cpp-3.exe cpp.exe

The symlinks are due to the "alternatives" system. If you look at 
Cygwin's original gcc.exe and cpp.exe, you'll see that they point to 
/etc/alternaines/gcc and cpp, which in turn point back to 
/usr/bin/gcc-3.exe and cpp-3.exe. The goal is to let you install 
multiple versions and use symlinks to set the defaults. Seems like 
overkill in this case.

Dave


  reply	other threads:[~2009-03-19 14:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  7:02 Alan Schmitt
2009-03-19  7:47 ` [Caml-list] " Alain Frisch
2009-03-19 14:30   ` Dave Benjamin [this message]
2009-03-19 15:52     ` Joel Reymont
2009-03-19 16:28   ` Alan Schmitt

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=49C25720.2040800@ramenlabs.com \
    --to=dave@ramenlabs.com \
    --cc=alain@frisch.fr \
    --cc=alan.schmitt@polytechnique.org \
    --cc=caml-list@inria.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;
as well as URLs for NNTP newsgroup(s).