RE: Msys2 64: progress

30 Jun 2016

      BTW, during ./boot, I get a lot of errors like this.  Should I worry?

Thanks.

Simon

Booting .
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
               LC_ALL = (unset),
               LANG = "ENG"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Booting libraries/base/
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
               LC_ALL = (unset),
               LANG = "ENG"
    are supported and installed on your system.
Booting libraries/directory/
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
               LC_ALL = (unset),
               LANG = "ENG"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Booting libraries/integer-gmp/
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:

From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Simon Peyton Jones via ghc-devs
Sent: 30 June 2016 12:22
To: lonetiger@gmail.com
Cc: ghc-devs@haskell.org
Subject: RE: Msys2 64: progress

OK.  How do I “try with python2 instead”?

SImon

From: lonetiger@gmail.commailto:lonetiger@gmail.com [mailto:lonetiger@gmail.com]
Sent: 30 June 2016 10:12
To: Simon Peyton Jones mailto:simonpj@microsoft.com>
Cc: ghc-devs@haskell.orgmailto:ghc-devs@haskell.org
Subject: RE: Msys2 64: progress

Hi Simon,

Could you try with python2 instead? (If it’s installed I think the testsuite would pick it up automatically).

Python3 is marked as experimental in the testsuite

PYTHON3 = sys.version_info >= (3, 0)
if PYTHON3:
    print("*** WARNING: running testsuite using Python 3.\n"
          "*** Python 3 support is experimental. See Trac #9184.")

And based on that trac, it routinely breaks..

Regards,
Tamar

From: Simon Peyton Jonesmailto:simonpj@microsoft.com
Sent: Thursday, June 30, 2016 08:28
To: Simon Peyton Jonesmailto:simonpj@microsoft.com; lonetiger@gmail.commailto:lonetiger@gmail.com
Cc: ghc-devs@haskell.orgmailto:ghc-devs@haskell.org
Subject: RE: Msys2 64: progress

Tamar, Luke, David, Andrey, and others

OK that was it!  Now I can build GHC…. Real progress.

But I still can’t validate:
sh validate
using THREADS=5
make: Entering directory '/c/code/HEAD/utils/checkUniques'
./check-uniques.py ../..
Traceback (most recent call last):
  File "./check-uniques.py", line 39, in <module>
    uniques = find_uniques(glob.glob(os.path.join(top_dir, 'compiler', 'prelude', '*.hs')))
  File "./check-uniques.py", line 15, in find_uniques
    ms = unique_re.findall(open(f).read())
  File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
    return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 15185: ordinal not in range(128)
make: *** [Makefile:8: check] Error 1
make: Leaving directory '/c/code/HEAD/utils/checkUniques'
/c/code/HEAD$

Any ideas about what might be happening?   The Python version is 3.4.3.

Thanks

Simon

From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Simon Peyton Jones via ghc-devs
Sent: 29 June 2016 12:08
To: lonetiger@gmail.commailto:lonetiger@gmail.com
Cc: ghc-devs@haskell.orgmailto:ghc-devs@haskell.org
Subject: RE: Msys2 64: progress

Aha!  That sounds very plausible.   I’ll try.   Maybe it’s a path-ordering thing.

It would be very cool if ‘configure’ checked that ‘find’ was the find it was expecting, not Windows find.  Dunno how to do that, but that check would have saved us a lot of time.

(For most other utils, weget, curl etc, there is no Windows program with the same name.  But for ‘find’, there is.)

Simon

From: lonetiger@gmail.commailto:lonetiger@gmail.com [mailto:lonetiger@gmail.com]
Sent: 29 June 2016 11:35
To: Simon Peyton Jones mailto:simonpj@microsoft.com>
Cc: ghc-devs@haskell.orgmailto:ghc-devs@haskell.org
Subject: RE: Msys2 64: progress

Hi Simon,

I think you’re right,
That pattern in the error is the one we pass to find

find "${base_dir}" -name "*.tar.xz" -exec tar xfJ {} \;

on line 334 of configure.ac which is supposed to unpack the files.
That the download script doesn’t output nothing makes sense now since the hashes of the files match.

I *think* what’s going on here is that for some reason you don’t have findutils installed and it’s instead using
The windows “find” utility, which generates that error.