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

On Fri, 6 Jan 2017, Klaij, Christiaan wrote: > Satish, > > Our sysadmin is not keen on downgrading glibc. sure > I'll stick with "--with-shared-libraries=0" for now thats fine. > and wait for SL7.3 with intel 17. Well they are not related so if you can - you should upgrade to intel-17

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

v> Sent: Thursday, January 05, 2017 7:02 PM To: Matthew Knepley Cc: Klaij, Christiaan; petsc-users Subject: Re: [petsc-users] problems after glibc upgrade to 2.17-157 On Thu, 5 Jan 2017, Matthew Knepley wrote: > On Thu, Jan 5, 2017 at 2:37 AM, Klaij, Christiaan <c.kl...@marin.nl>

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

On Thu, 5 Jan 2017, Satish Balay wrote: > Well its more of RHEL - than SL. And its just Intel .so files [as far > as we know] thats triggering this issue. > > RHEL generally doesn't make changes that break old binaries. But any > code change [wihch bug fixes are] - can introduce changed behavior

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

On Thu, 5 Jan 2017, Matthew Knepley wrote: > On Thu, Jan 5, 2017 at 2:37 AM, Klaij, Christiaan wrote: > > 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

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

; > MARIN news: http://www.marin.nl/web/News/News-items/Comparison-of- > uRANS-and-BEMBEM-for-propeller-pressure-pulse-prediction.htm > > ____ > From: Satish Balay <ba...@mcs.anl.gov> > Sent: Wednesday, January 04, 2017 7:24 PM > To: petsc-users > Cc: Klaij, Ch

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

From: Satish Balay <ba...@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 upgrad

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@el7 benchmarks]$ icc --version icc (ICC) 17.0.1 20161005 Copyright (C) 1985-2016 Intel Corporation. All rights reserved. [balay@el7 benchmarks]$

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

On Wed, 4 Jan 2017, Satish Balay wrote: > BTW - You have: > > Machine platform: > ('Linux', 'marclus4login3', '3.10.0-327.36.3.el7.x86_64', '#1 SMP Mon Oct 24 > 09:16:18 CDT 2016', 'x86_64', 'x86_64') > > > So glibc is updated - but not kernel - so its a partial update? [or > machine not

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

BTW - You have: Machine platform: ('Linux', 'marclus4login3', '3.10.0-327.36.3.el7.x86_64', '#1 SMP Mon Oct 24 09:16:18 CDT 2016', 'x86_64', 'x86_64') So glibc is updated - but not kernel - so its a partial update? [or machine not rebooted after a major upgrade (7.2 -> 7.3) ?] I wonder if

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

On Wed, 4 Jan 2017, Matthew Knepley wrote: > On Wed, Jan 4, 2017 at 9:19 AM, Klaij, Christiaan wrote: > > > Attached is the log for > > > > > > LIBS="-L/cm/shared/apps/intel/compilers_and_libraries_2016. > > 3.210/linux/compiler/lib/intel64_lin -lifcore" > > > Something is

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

--- > *From:* Klaij, Christiaan > *Sent:* Wednesday, January 04, 2017 4:05 PM > > *To:* Matthew Knepley > *Cc:* petsc-users; Satish Balay > *Subject:* Re: [petsc-users] problems after glibc upgrade to 2.17-157 > > > By the way, petsc did compile and install metis and

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

From: Klaij, Christiaan Sent: Wednesday, January 04, 2017 3:53 PM To: Matthew Knepley Cc: petsc-users; Satish Balay Subject: Re: [petsc-users] problems after glibc upgrade to 2.17-157 So how would I do that? Does LIBS= accept spaces in the string? Something like this perhaps: LIBS="

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

rediction.htm> From: Matthew Knepley <knep...@gmail.com> Sent: Wednesday, January 04, 2017 3:13 PM To: Klaij, Christiaan Cc: petsc-users; Satish Balay Subject: Re: [petsc-users] problems after glibc upgrade to 2.17-157 On Wed, Jan 4, 2017 at 7:37 AM, Klaij, Christ

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

ems/MARIN-Report-119-highlighting-naval-research-projects.htm> > > -- > *From:* Matthew Knepley <knep...@gmail.com> > *Sent:* Wednesday, January 04, 2017 1:43 PM > *To:* Klaij, Christiaan > *Cc:* petsc-users; Satish Balay > *Subject:* Re

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

From: Satish Balay <ba...@mcs.anl.gov<mailto:ba...@mcs.anl.gov>> Sent: Tuesday, January 03, 2017 5:00 PM To: Matthew Knepley Cc: Klaij, Christiaan; petsc-users@mcs.anl.gov<mailto:petsc-users@mcs.anl.gov> Subject: Re: [petsc-users] problems after glibc upgrade to

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

N news: http://www.marin.nl/web/News/News-items/Comparison-of- > uRANS-and-BEMBEM-for-propeller-pressure-pulse-prediction.htm > > > From: Satish Balay <ba...@mcs.anl.gov> > Sent: Tuesday, January 03, 2017 4:37 PM > To: Klaij, Christiaan

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

e, the new > configure.log is attached. It's slightly larger but not much > clearer too me... > > Chris > ________ > From: Satish Balay <ba...@mcs.anl.gov> > Sent: Tuesday, January 03, 2017 5:00 PM > To: Matthew Knepley > Cc: Klaij, Christiaan

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

<ba...@mcs.anl.gov> Sent: Tuesday, January 03, 2017 5:00 PM To: Matthew Knepley Cc: Klaij, Christiaan; petsc-users@mcs.anl.gov Subject: Re: [petsc-users] problems after glibc upgrade to 2.17-157 On Tue, 3 Jan 2017, Matthew Knepley wrote: > Or get the new tarball when it spins tonight, si

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

On Tue, 3 Jan 2017, Matthew Knepley wrote: > Or get the new tarball when it spins tonight, since Satish has just > added the fix to maint. We don't spin 'maint/patch-release' tarballs everynight. Its every 1-3 months - [partly depending upon the number of outstanding patches - or their severity]

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

ail.com> > Sent: Tuesday, January 03, 2017 4:36 PM > To: Klaij, Christiaan > Cc: petsc-users@mcs.anl.gov > Subject: Re: [petsc-users] problems after glibc upgrade to 2.17-157 > > On Tue, Jan 3, 2017 at 9:04 AM, Klaij, Christiaan > <c.kl...@marin.nl<mailto:c.kl...@marin.

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

News-items/Modelling-natural-transition-on-hydrofoils-for-application-in-underwater-gliders-1.htm> > > -- > *From:* Matthew Knepley <knep...@gmail.com> > *Sent:* Tuesday, January 03, 2017 4:36 PM > *To:* Klaij, Christiaan > *Cc:* petsc-users@mcs.anl.gov > *S

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

thew Knepley <knep...@gmail.com> Sent: Tuesday, January 03, 2017 4:36 PM To: Klaij, Christiaan Cc: petsc-users@mcs.anl.gov Subject: Re: [petsc-users] problems after glibc upgrade to 2.17-157 On Tue, Jan 3, 2017 at 9:04 AM, Klaij, Christiaan <c.kl...@marin.nl<mailto:c.kl...@marin.nl>>

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

On Tue, 3 Jan 2017, Matthew Knepley wrote: > We previously fixed a bug with this error reporting: > > https://bitbucket.org/petsc/petsc/commits/32cc76960ddbb48660f8e7c667e293c0ccd0e7d7 > > in August. Is it possible that your PETSc is older than this? Could > you apply that patch, or run the

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

Do you have similar issues with gnu compilers? It must be some incompatibility with intel compilers with this glibc change. > compilers: Check that C libraries can be used from Fortran Pushing language FC Popping language FC

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

On Tue, Jan 3, 2017 at 9:04 AM, Klaij, Christiaan wrote: > > I've been using petsc-3.7.4 with intel mpi and compilers, > superlu_dist, metis and parmetis on a cluster running > SL7. Everything was working fine until SL7 got an update where > glibc was upgraded from 2.17-106 to