must set USE_BLAS64=0 when using Ubuntu PPA

[heptal]

I know this is not officially supported, but it could be that the PPA binary was built as 32-bit?

ERROR: OpenBLAS was not built with 64bit integer support.
You're seeing this error because Julia was built with USE_BLAS64=1
Please rebuild Julia with USE_BLAS64=0
Quitting.

It shows I have the one installed from @staticfloat's PPA

~/julia$ apt-cache policy libopenblas-dev
libopenblas-dev:
  Installed: 0.2.8.1-juliadeps4~precise
  Candidate: 0.2.8.1-juliadeps4~precise
  Version table:
 *** 0.2.8.1-juliadeps4~precise 0
        500 http://ppa.launchpad.net/staticfloat/julia-deps/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status
     0.1alpha2.2-3 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

Make.user:

LLVM_CONFIG=llvm-config-3.3
USECLANG=1
USE_SYSTEM_LLVM=1
USE_SYSTEM_ZLIB=1
USE_SYSTEM_SUITESPARSE=1
USE_SYSTEM_ARPACK=1
USE_SYSTEM_BLAS=1
USE_SYSTEM_FFTW=1
USE_SYSTEM_LAPACK=1
USE_SYSTEM_LIGHTTPD=1
USE_SYSTEM_GMP=1
USE_SYSTEM_PCRE=1
USE_SYSTEM_LIBUNWIND=1
USE_SYSTEM_READLINE=1
USE_SYSTEM_GLPK=1

Using Ubuntu 12.04.3 LTS inside a VM:

Linux ubuntu 3.2.0-52-generic \#78-Ubuntu SMP Fri Jul 26 16:21:44 UTC 2013 x86_64

It builds when I set USE_BLAS64=0.

[pao]

Yes, that's correct (I noticed the same thing.) Is this a request for @staticfloat to supply a version with the BLAS64 interfaces, or is there some other issue?

[staticfloat]

Is there any reason to build a 32-bit binary with a 64-bit interface? Does
a 32-bit kernel support addressing more than 4GB in the same process? (I'm
a little rusty on what exactly PAE gives you)
On Aug 25, 2013 10:21 AM, "pao" notifications@github.com wrote:

Yes, that's correct (I noticed the same thing.) Is this a request for
@staticfloat https://github.com/staticfloat to supply a version with
the BLAS64 interfaces, or is there some other issue?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4142#issuecomment-23228471
.

[heptal]

I suppose the real issue is documentation. I had used this thread which is outdated (stumbling through failed builds until I installed clang-3.3 and llvm-3.3-dev).

I just discovered that travis.yml has all the relevant information in copy/paste form, and would be up to date. I linked to it in the Ubuntu section of the readme.