[petsc-users] problems after glibc upgrade to 2.17-157

[Matthew Knepley]

On Thu, Jan 5, 2017 at 2:37 AM, Klaij, Christiaan <C.Klaij at marin.nl> wrote:

> Satish, Matt
>
> Our sysadmin tells me Scientific Linux is still busy with the
> RedHat 7.3 update, so yes, this is a partial update somewhere
> between 7.2 and 7.3...
>
> No luck with the quotes on my system, but the option
> --with-shared-libraries=0 does work! make test gives:
>
> Running test examples to verify correct installation
> Using PETSC_DIR=/projects/developers/cklaij/ReFRESCO/
> Dev/trunk/Libs/install/petsc-3.7.4 and PETSC_ARCH=
> C/C++ example src/snes/examples/tutorials/ex19 run successfully with 1
> MPI process
> C/C++ example src/snes/examples/tutorials/ex19 run successfully with 2
> MPI processes
> Fortran example src/snes/examples/tutorials/ex5f run successfully with 1
> MPI process
> Completed test examples
>
> I've also tested the standalone program of metis, that works too:
>
> $ ./gpmetis
> Missing parameters.
>    Usage: gpmetis [options] <filename> <nparts>
>           use 'gpmetis -help' for a summary of the options.
>
> So problem solved for now, thanks to you and Matt for all your
> help! On the long run I will go for Intel-17 on SL7.3.
>
> What worries me though is that a simple update (which happens all
> the time according to sysadmin) can have such a dramatic effect.
>

I agree. It seems SL has broken the ability to use shared libraries with a
simple point release.
It seems the robustness of all this process is a myth.

  Thanks,

      Matt


> Thanks again,
> Chris
>
>
>
> dr. ir. Christiaan Klaij  | CFD Researcher | Research & Development
> MARIN | T +31 317 49 33 44 | mailto:C.Klaij at marin.nl | http://www.marin.nl
>
> MARIN news: http://www.marin.nl/web/News/News-items/Comparison-of-
> uRANS-and-BEMBEM-for-propeller-pressure-pulse-prediction.htm
>
> ________________________________________
> From: Satish Balay <balay at mcs.anl.gov>
> Sent: Wednesday, January 04, 2017 7:24 PM
> To: petsc-users
> Cc: Klaij, Christiaan
> Subject: Re: [petsc-users] problems after glibc upgrade to 2.17-157
>
> On Wed, 4 Jan 2017, Satish Balay wrote:
>
> > So I guess your best bet is static libraries..
>
> Or upgrade to intel-17 compilers.
>
> Satish
>
> -------
>
> [balay at el7 benchmarks]$ icc --version
> icc (ICC) 17.0.1 20161005
> Copyright (C) 1985-2016 Intel Corporation.  All rights reserved.
>
> [balay at el7 benchmarks]$ icc sizeof.c -lifcore
> [balay at el7 benchmarks]$ ldd a.out
>         linux-vdso.so.1 =>  (0x00007ffed4b02000)
>         libifcore.so.5 => /soft/com/packages/intel/17/
> u1/compilers_and_libraries_2017.1.132/linux/compiler/lib/intel64/libifcore.so.5
> (0x00007f5a65430000)
>         libm.so.6 => /lib64/libm.so.6 (0x00007f5a65124000)
>         libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f5a64f0e000)
>         libc.so.6 => /lib64/libc.so.6 (0x00007f5a64b4c000)
>         libdl.so.2 => /lib64/libdl.so.2 (0x00007f5a64948000)
>         libimf.so => /soft/com/packages/intel/17/
> u1/compilers_and_libraries_2017.1.132/linux/compiler/lib/intel64/libimf.so
> (0x00007f5a6445c000)
>         libsvml.so => /soft/com/packages/intel/17/
> u1/compilers_and_libraries_2017.1.132/linux/compiler/lib/intel64/libsvml.so
> (0x00007f5a63550000)
>         libintlc.so.5 => /soft/com/packages/intel/17/
> u1/compilers_and_libraries_2017.1.132/linux/compiler/lib/intel64/libintlc.so.5
> (0x00007f5a632e6000)
>         /lib64/ld-linux-x86-64.so.2 (0x00007f5a65793000)
> [balay at el7 benchmarks]$ ./a.out
> long double : 16
> double      : 8
> int         : 4
> char        : 1
> short       : 2
> long        : 8
> long long   : 8
> int *       : 8
> size_t      : 8
> [balay at el7 benchmarks]$
>



-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20170105/95fcc4ad/attachment.html>