[LSST|dm-users 565] Re: building stack on centos7 (ndarray failure)

[Lynne Jones]

Thanks to all for the prompt replies!
Luckily, we can choose to use CentOS6 as the base for the VM instead, so
we'll do that. The only reason for not doing it in the first place was that
we had already started with CentOS7 and installed all the prereqs there
before realizing it might be a problem.
(does that mean the ndarray stuff will still be a problem, or does that go
away with CentOS6?)

On Wed, Feb 11, 2015 at 10:48 AM, Russell Owen <rowen at uw.edu> wrote:

> First, the release does not build on gcc 4.8 due to bugs in our code that
> Jim Bosch has fixed on master. We hope to have a new release fairly soon.
>
> Second, the issue you mention is a known bug in anaconda which you can
> solve by deleting libc from anaconda (I don't have the details handy, but
> an email history search or google search should turn them up).
>
> -- Russell
>
> On Feb 11, 2015, at 10:41 AM, Lynne Jones <ljones.uw at gmail.com> wrote:
>
> Hi all,
>
> Has anyone built the stack successfully on CentOS 7?
> gcc 4.8.2
> LSST anaconda python 2.1
> stack is the current v10 stack.
>
> I'm trying to get the stack installed on a CANFAR virtual machine, but am
> getting a unit test failure when building ndarray. (ndarray 10.0+1)
>
> The test which is failing is
> tests/ndarray-python.py
>
> and the contents of the .failed file are:
>
> Traceback (most recent call last):
>   File "tests/ndarray-python.py", line 3, in <module>
>     import ndarray_python_test
> ImportError: /home/centos/lsst/Linux64/anaconda/2.1.0/bin/../lib/
> libm.so.6:
> version `GLIBC_2.15' not found (required by
> /home/centos/lsst/Linux64/fftw/3.3.3/lib/libfftw3.so.3)
>
>
> Lynne
>
> _______________________________________________
> dm-users mailing list
> dm-users at lists.lsst.org
> https://lists.lsst.org/mailman/listinfo/dm-users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lsst.org/pipermail/dm-users/attachments/20150211/34d4ff1b/attachment.html>