am a babe in these particular woods, and defer to others wisdom.
Simon
From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Gintautas
Miliauskas
Sent: 12 October 2014 23:06
To: kyra
Cc: ghc-devs@haskell.org
Subject: Re: Building ghc on Windows with msys2
However, overall (not GHC
On 2014-10-13 at 10:57:10 +0200, Simon Peyton Jones wrote:
I think the potential difficulty is (1). Maybe they take it down (e.g. they
move on to version X so they take down old version Y).
An alternative would be to stash a copy somewhere on GHC’s main web
server, and wget that. I’d be
]
Sent: 09 October 2014 06:04
To: Gintautas Miliauskas; Simon Peyton Jones
Cc: Randy Polen; kyra; Marek Wawrzos; Roman Kuznetsov; Neil Mitchell;
ghc-devs@haskell.orgmailto:ghc-devs@haskell.org
Subject: Re: Building ghc on Windows with msys2
Hi Gintautas,
Indeed, the next thing I was going to ask
I've updated the configure script to download the mingw distribution on the
fly (D339 https://phabricator.haskell.org/D339, #9218
https://ghc.haskell.org/trac/ghc/ticket/9218). I could use some help with
a few things:
1. Validating the update to gcc 4.8.3. I tried to run the tests and got
some
However, overall (not GHC use cases) gcc 4.9.1 still looks more buggy on
Windows than 4.8.3. 'Mingw-builds' project (which is now a part of
mingw-w64 project and is considered to be an official mingw-w64 gcc
distribution and is maintained by a man close to Msys2 project) has very
nice and
,
Tamar
--
From: Gintautas Miliauskas gintau...@miliauskas.lt
Sent: 13/10/2014 00:06
To: kyra ky...@mail.ru
Cc: ghc-devs@haskell.org
Subject: Re: Building ghc on Windows with msys2
However, overall (not GHC use cases) gcc 4.9.1 still looks more buggy on
Windows
:* Randy Polen; kyra; Marek Wawrzos; Roman Kuznetsov; Neil Mitchell;
ghc-devs@haskell.org
*Subject:* Re: Building ghc on Windows with msys2
Hi Gintautas,
Indeed, the next thing I was going to ask was about expediting the
decision process. I would be happy to try and coordinate a push
On 2014-10-09 at 07:15:13 +0200, Páli Gábor János wrote:
2014-10-07 17:02 GMT+02:00 Páli Gábor János pali.ga...@gmail.com:
2014-10-07 15:04 GMT+02:00 cg chengan...@gmail.com:
I guess the current two build server are all Cygwin based, they are
failing at the same permission issue at early
up the msys2 page to serve as
the default, but wanted to see more testing done before before dropping the
other pages.
I agree with using msys2 as the main choice. (I’m using it myself.) It may be
that Gintautas’s page
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows/MSYS2
*From:* loneti...@gmail.com [mailto:loneti...@gmail.com]
*Sent:* 09 October 2014 06:04
*To:* Gintautas Miliauskas; Simon Peyton Jones
*Cc:* Randy Polen; kyra; Marek Wawrzos; Roman Kuznetsov; Neil Mitchell;
ghc-devs@haskell.org
*Subject:* Re: Building ghc on Windows with msys2
Hi Gintautas
@haskell.org; kyra; Marek Wawrzos
Subject: RE: Building ghc on Windows with msys2
I'll set up a wikipage this evening.
Should we get a mailing list of our own too, or do you think it's best to
continue on ghc-devs@?
--
Gintautas Miliauskas
On Oct 9, 2014 9:52 AM, Simon Peyton Jones
simo
On 27/09/2014 22:04, Gintautas Miliauskas wrote:
8. A broader question: what general approach to ghc on Windows shall we
take? The prebuilt packages currently provided by ghc-tarballs are also
covered by msys2's package manager. Why not offload that pain to msys2
then? The advantage here is
2014-10-09 9:12 GMT+02:00 Herbert Valerio Riedel hvrie...@gmail.com:
I didn't see this issue on a newly setup MSYS2 environment
either. How old is your MSYS environment? (And what filesystem windows
version are you running?)
I use a 64-bit Windows 7 SP1 (6.1.7601) with both the 32-bit (i686)
On 2014-10-08 at 04:28:50 +0200, cg wrote:
[...]
After cloning ghc repository, I switch every sub-module to Master (it is
usually HEAD) branch.
Why are you doing that? :-)
[...]
Now after cloning ghc repository, if I don't switch to any branch --
'git branch'
will show all submodules
2014-10-07 17:02 GMT+02:00 Páli Gábor János pali.ga...@gmail.com:
2014-10-07 15:04 GMT+02:00 cg chengan...@gmail.com:
I guess the current two build server are all Cygwin based, they are
failing at the same permission issue at early building stage, it prevents
checking out the real problem. It
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows/MSYS2 is
already sufficient. Although I’d like to see it tested by others. For
example, I found that it was CRUCIAL to set MSYSYSTEM=MINGW whereas Gintautas’s
page says nothing about that.
Are you sure that is a problem
On 10/1/2014 6:25 AM, Simon Peyton Jones wrote:
·[...] The important thing is that it
should be reproducible, and not dependent on the particular Cygwin or
gcc or whatever the that user happens to have installed.
Exactly. So how about setting up a build server using msys2?
I guess the
2014-10-07 15:04 GMT+02:00 cg chengan...@gmail.com:
I guess the current two build server are all Cygwin based, they are
failing at the same permission issue at early building stage, it prevents
checking out the real problem. It seems msys2 (or msys) seldom has
such issue.
For what it is
On Tue, Oct 7, 2014 at 11:25 AM, cg chengan...@gmail.com wrote:
On 9/16/2014 4:57 AM, Gintautas Miliauskas wrote:
msys2 seems to be in good shape and should probably be promoted to the
primary suggested method to build ghc on Windows. Let's look into that
once the new build instructions have
is the main choice.)
I agree with using msys2 as the main choice. (I’m using it myself.) It
may be that Gintautas’s page
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows/MSYS2
is already sufficient. Although I’d like to see it tested by others. For
example, I found
be that Gintautas’s page
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows/MSYS2
is already sufficient. Although I’d like to see it tested by others. For
example, I found that it was CRUCIAL to set MSYSYSTEM=MINGW whereas
Gintautas’s page says nothing about that.
Other small thoughts
On 10/8/2014 1:03 AM, Austin Seipp wrote:
I hide 'empty' and 'foldr' at importing point and the code compiles.
Has anyone see the same issues?
Ugh, this is some fallout I thought we had fixed, but apparently not.
I'll fix it shortly, thanks.
[...]
Why does ghc-stage1.exe use so much
pages.
I agree with using msys2 as the main choice. (I’m using it myself.) It
may be that Gintautas’s page
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows/MSYS2
is already sufficient. Although I’d like to see it tested by others. For
example, I found that it was CRUCIAL
I'm sure we could make git handle the tarballs, but it just seems like the
wrong tool for the job. We'd have to use multiple advanced features of git
where a simple wget/curl would do. Versioning is also a moot point, since
we would embed versions in filenames. In fact, versioning would be easier
agree with using msys2 as the main choice. (I’m using it myself.) It may be
that Gintautas’s page
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows/MSYS2 is
already sufficient. Although I’d like to see it tested by others. For
example, I found that it was CRUCIAL to set
On 9/28/2014 11:16 PM, Gintautas Miliauskas wrote:
However, overall (not GHC use cases) gcc 4.9.1 still looks more buggy
on Windows than 4.8.3.
Hmm, that sounds like an argument against trusting msys2 to provide a
sane mingw gcc compiler... Bummer. What kind of bugs did you have in mind?
3. Why is ghc-tarballs a git repository? That does not seem very wise.
[...]
Could we have a stable folder under haskell.org/ to put the files in,
to
make sure that they never go away, and just wget/curl them from there?
Forgot to add. Here is a script I used to test this approach, using
libffi-tarballs as an example:
https://gist.github.com/thomie/260755a5ab79f020fb79
On Mon, Sep 29, 2014 at 11:40 AM, Thomas Miedema thomasmied...@gmail.com
wrote:
3. Why is ghc-tarballs a git repository? That does not seem
On 9/28/2014 1:04 AM, Gintautas Miliauskas wrote:
11. A build with the host gcc failed. I think the cause is that it is
too new (4.9.1, significantly newer than 4.6.3 in ghc-tarballs). The
build of the currently checked in GMP (libraries/integer-gmp) fails
because a utility used in the build
However, overall (not GHC use cases) gcc 4.9.1 still looks more buggy on
Windows than 4.8.3.
Hmm, that sounds like an argument against trusting msys2 to provide a sane
mingw gcc compiler... Bummer. What kind of bugs did you have in mind?
'Mingw-builds' project (which is now a part of mingw-w64
Hey,
I can only address a small subset of your comments as I don't usually
develop on Windows and hence lack any significant Windows experience...
Thanks. Honestly, I'm no fan of Windows either. Not sure how I got into
this mess :)
2. Since the msys2 setup instructions are so simple and
Hi,
I've been spending some time on the Windows build, and a bunch of things
came up.
1. Building on msys2 with the provided ghc-tarballs works. The wikipage
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows/MSYS2 for
MSYS2 should be in good shape. It would be nice to get a bit
Hello!
I can only address a small subset of your comments as I don't usually
develop on Windows and hence lack any significant Windows experience...
On 2014-09-27 at 23:04:38 +0200, Gintautas Miliauskas wrote:
[...]
2. Since the msys2 setup instructions are so simple and linear, perhaps it
information, and yes I think we should focus on msys2.
Great stuff
Simon
*From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of
*Gintautas
Miliauskas
*Sent:* 15 September 2014 21:58
*To:* ghc-devs@haskell.org
*Subject:* Building ghc on Windows with msys2
Hello,
I
Hello,
I have been messing around a little bit with building GHC from source on
Windows, and found the msys2 wikipage
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows/MSYS2
quite
useful, but somewhat outdated. Quite a few steps in those instructions are
no longer necessary
35 matches
Mail list logo
