Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
12 Views

Bad Upgrade To MPSS 3.7??

Greetings,

I have three Phi hosts w/ 4x31S1P's and all three hosts have the same issue. I even wiped one of the hosts and did a fresh install to ensure that it wasn't something weird with the update itself.

My OS is Red Hat 6.7 (fully updated for 6.7...we haven't made the switch to 6.8 yet as that was just released recently...but as soon as it gets through the approval process I will). My kernel is 2.6.32-573.26.1.el6.x86_64. However, this is still the Intel recommended OS/kernel version anyway.

I am updating to MPSS 3.7. I am following the Intel Manycore Platform Software Stack User's Guide March 2016 that comes inside of the 3.7 tar file.

I followed section 3.4 "Base Intel MPSS Installation" (starting on page 39). All of it went real smooth until 3.4.7.2 pg46 validation.

$ miccheck
miccheck: error while loading shared libraries: libz.so.1: failed to map segment from shared object: Operation not permitted

All of the RPM's are installed and I can see the libraries in /opt/mpss/3.7/sysroots/x86_64-mpsssdk-linux/usr/lib/ . If I try to force the LD_LIBRARY_PATH, I get other errors like:

$ miccheck
miccheck: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /opt/mpss/3.7/sysroots/x86_64-mpsssdk-linux/usr/lib/libz.so.1)
/lib64/libc.so.6: version `GLIBC_2.14' not found (required by /opt/mpss/3.7/sysroots/x86_64-mpsssdk-linux/usr/lib/libpcre.so.0)

I haven't updated or done anything with mpss-3.7-k1om.tar yet. I figured I should probably fix the current error first. I looked around online, but didn't see anything that jumped out at me as being relevant.

Can someone give me a few pointers on where I may have gone wrong?

Thank you!

0 Kudos
2 Replies
Highlighted
Beginner
12 Views

Might I enquire as to why you're using OS and tool version that are two years old? Red Hat 7.3 and MPSS 3.8.4 are the current versions.

0 Kudos
Highlighted
New Contributor III
12 Views

Hi,

miccheck runs fine on my CentOS 6.9 machine (as it did on 6.7 & 6.8); my guess is that a system lib is not functionining correctly. what happens when you type

ldd `which miccheck`

? I get

$ ldd `which miccheck`
    linux-vdso.so.1 =>  (0x00007ffe553ff000)
    libz.so.1 => /lib64/libz.so.1 (0x00007f8a71252000)
    libdl.so.2 => /lib64/libdl.so.2 (0x00007f8a7104e000)
    libc.so.6 => /lib64/libc.so.6 (0x00007f8a70cba000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f8a71468000)

HTH,

JJK

0 Kudos