From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Hayden Livingston <halivingston@gmail.com>, jit@gcc.gnu.org
Subject: Re: Has anyone tried building for Windows?
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <CACXZuxfL=v38EA0QLz48F4WFi_XJ4DK4bAV4t1ycRsBrhC0hQg@mail.gmail.com> (raw)
In-Reply-To: <1438166692.9683.17.camel@surprise>
On 29 July 2015 at 11:44, David Malcolm <dmalcolm@redhat.com> wrote:
> On Tue, 2015-07-28 at 22:43 -0700, Hayden Livingston wrote:
>> I've attempted to build on Windows using Cygwin and MingW-64 and I'm
>> not really familiar with the build system enough but I can't make any
>> forward progress.
>
> Thanks for trying this. As far as I know, you're the first person who's
> attempted this.
>
I tried a few days ago - but could not even get configure to work. It
kept complaining about missing mpfr, gmp, mpc even though these were
installed. I was using msys2 as the environment with mingw64
compilers. In the end decided life is too short and I have many other
things I need to do.
Does gcc even compile on Windows without patches from mingw project?
It is a pity as LLVM code generated on Windows has a serious
deficiency - longjmp calls cause crash as the generated code doesn't
conform to Windows requirements. I was hoping that gcc generated code
would not suffer from this.
Regards
Dibyendu
next prev parent reply other threads:[~2015-07-29 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 Hayden Livingston
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar [this message]
2015-01-01 0:00 ` Mukul Sabharwal
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Mukul Sabharwal
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='CACXZuxfL=v38EA0QLz48F4WFi_XJ4DK4bAV4t1ycRsBrhC0hQg@mail.gmail.com' \
--to=mobile@majumdar.org.uk \
--cc=dmalcolm@redhat.com \
--cc=halivingston@gmail.com \
--cc=jit@gcc.gnu.org \
/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).