On Thu, Aug 6, 2015 at 4:22 PM, David Cournapeau cournape@gmail.com wrote:

Sorry if that's obvious, but do you have Visual Studio 2010 installed ?

On Thu, Aug 6, 2015 at 11:17 PM, Charles R Harris < charlesr.harris@gmail.com> wrote:

...

Anyone know how to fix this? I've run into it before and never got it figured out.

[192.168.121.189:22] out: File "C:\Python34\lib\distutils\msvc9compiler.py", line 259, in query_vcvarsall [192.168.121.189:22] out: [192.168.121.189:22] out: raise DistutilsPlatformError("Unable to find vcvarsall.bat") [192.168.121.189:22] out: [192.168.121.189:22] out: distutils.errors.DistutilsPlatformError: Unable to find vcvarsall.bat

Chuck

I'm running numpy-vendor, which is running wine. I think it is all mingw with a few installed dll's. The error is coming from the Python distutils as part of `has_cblas`.

Chuck

Which command exactly did you run to have that error ? Normally, the code in msvc9compiler should not be called if you call the setup.py with the mingw compiler as expected by distutils

On Fri, Aug 7, 2015 at 12:19 AM, Charles R Harris <charlesr.harris@gmail.com

wrote:

On Thu, Aug 6, 2015 at 5:11 PM, Charles R Harris < charlesr.harris@gmail.com> wrote:

...

On Thu, Aug 6, 2015 at 4:22 PM, David Cournapeau cournape@gmail.com wrote:

...

Sorry if that's obvious, but do you have Visual Studio 2010 installed ?

On Thu, Aug 6, 2015 at 11:17 PM, Charles R Harris < charlesr.harris@gmail.com> wrote:

...

Anyone know how to fix this? I've run into it before and never got it figured out.

[192.168.121.189:22] out: File "C:\Python34\lib\distutils\msvc9compiler.py", line 259, in query_vcvarsall [192.168.121.189:22] out: [192.168.121.189:22] out: raise DistutilsPlatformError("Unable to find vcvarsall.bat") [192.168.121.189:22] out: [192.168.121.189:22] out: distutils.errors.DistutilsPlatformError: Unable to find vcvarsall.bat

Chuck

I'm running numpy-vendor, which is running wine. I think it is all mingw with a few installed dll's. The error is coming from the Python distutils as part of `has_cblas`.

It's not impossible that we have changed the build somewhere along the line.

Chuck

---

NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

On Fri, Aug 7, 2015 at 3:33 AM, David Cournapeau cournape@gmail.com wrote:

Which command exactly did you run to have that error ? Normally, the code in msvc9compiler should not be called if you call the setup.py with the mingw compiler as expected by distutils

I'm running numpy-vendor which is running wine inside ubuntu inside a vm. The relevant commands are

run("rm -rf ../local") run("paver sdist") run("python setup.py install --prefix ../local") run("paver pdf") run("paver bdist_superpack -p 3.4") run("paver bdist_superpack -p 3.3") run("paver bdist_superpack -p 2.7") run("paver write_release_and_log") run("paver bdist_wininst_simple -p 2.7") run("paver bdist_wininst_simple -p 3.3") run("paver bdist_wininst_simple -p 3.4")

Which don't look suspicious. I think we may have changed something in numpy/distutils, possibly as part of https://github.com/numpy/numpy/pull/6152

Chuck

On Fri, Aug 7, 2015 at 8:16 AM, Charles R Harris charlesr.harris@gmail.com wrote:

On Fri, Aug 7, 2015 at 8:02 AM, Charles R Harris < charlesr.harris@gmail.com> wrote:

...

On Fri, Aug 7, 2015 at 3:33 AM, David Cournapeau cournape@gmail.com wrote:

...

Which command exactly did you run to have that error ? Normally, the code in msvc9compiler should not be called if you call the setup.py with the mingw compiler as expected by distutils

I'm running numpy-vendor which is running wine inside ubuntu inside a vm. The relevant commands are

    run("rm -rf ../local")
    run("paver sdist")
    run("python setup.py install --prefix ../local")
    run("paver pdf")
    run("paver bdist_superpack -p 3.4")
    run("paver bdist_superpack -p 3.3")
    run("paver bdist_superpack -p 2.7")
    run("paver write_release_and_log")
    run("paver bdist_wininst_simple -p 2.7")
    run("paver bdist_wininst_simple -p 3.3")
    run("paver bdist_wininst_simple -p 3.4")

Which don't look suspicious. I think we may have changed something in numpy/distutils, possibly as part of https://github.com/numpy/numpy/pull/6152

Actually, looks like b6d0263239926e8b14ebc26a0d7b9469fa7866d4. Hmm..., strange.

OK, that just leads to an earlier cythonize error because random.pyx changed, so not the root cause.

Chuck

On Fri, Aug 7, 2015 at 9:36 AM, Charles R Harris charlesr.harris@gmail.com wrote:

So the problem comes from the has_cblas function

def has_cblas(self):
    # primitive cblas check by looking for the header
    res = False
    c = distutils.ccompiler.new_compiler()
    tmpdir = tempfile.mkdtemp()
    s = """#include <cblas.h>"""
    src = os.path.join(tmpdir, 'source.c')
    try:
        with open(src, 'wt') as f:
            f.write(s)
        try:
            c.compile([src], output_dir=tmpdir,
                      include_dirs=self.get_include_dirs())
            res = True
        except distutils.ccompiler.CompileError:
            res = False
    finally:
        shutil.rmtree(tmpdir)
    return res

The problem is the test compile, which does not use the mingw compiler, but falls back to the compiler found in python distutils. Not sure what the fix is.

See #6175 https://github.com/numpy/numpy/pull/6175 .

Chuck