>
>
> i.e use :
>
> --with-cxx=g++-7
>
Thanks, that fixed it.
just to be clear
- there is no configure option --with-cc++. Its --with-cxx
- and you are trying to provide a c compiler for a c++ compiler option.
i.e use :
--with-cxx=g++-7
Satish
On Sat, 27 Jan 2018, Smith, Barry F. wrote:
>
> Well you may be trying to build with gcc-7 but you are bui
Well you may be trying to build with gcc-7 but you are building C++ with clang
gmake[2]: Leaving directory
'/Users/markadams/Codes/petsc/arch-macosx-gnu-g-omp/externalpackages/mpich-3.3a3'
gmake[1]: Leaving directory
'/Users/markadams/Codes/petsc/arch-macosx-gnu-g-omp/externalpackages/mpich-3
And NERSC started loading these by default so my manual loads where
throwing an error that trigger a false positive in PETSc's configure.
Thanks,
On Fri, Aug 11, 2017 at 1:39 AM, Jeff Hammond
wrote:
> I have automated the installation of Autotools for years because of
> projects like MPICH that
I have automated the installation of Autotools for years because of
projects like MPICH that live at the bleeding edge of Autotools version
space. Feel free to grab
https://github.com/jeffhammond/HPCInfo/blob/master/buildscripts/Autotools.md.
A more advanced version that may handle non-interactive
removing the module loads in my .bashrc file fixed it.
I asked NERSC about the auto modules, which are needed for p4est,
On Thu, Aug 10, 2017 at 10:56 AM, Mark Adams wrote:
> I commented out these module loads in my .bashrc and it seems to get
> further.
>
> This build does not have p4est. May
I commented out these module loads in my .bashrc and it seems to get
further.
This build does not have p4est. Maybe the module load error broke configure.
On Thu, Aug 10, 2017 at 10:43 AM, Mark Adams wrote:
> But this is a different failure. I am/was able to get p4est to work by
> rerunning con
But this is a different failure. I am/was able to get p4est to work by
rerunning configure. Is this failure cause by p4est. NERSC changed a lot of
stuff on Edison, that is why I am rebuilding for someone.
On Thu, Aug 10, 2017 at 10:34 AM, Tobin Isaac wrote:
>
> This seems to be a recurring theme
This seems to be a recurring theme. p4est code is quite stable at the
moment. Even though we have `--download-p4est`, it might be a better
idea to install p4est once externally to petsc and use `--with-p4est`,
especially when getting autotools are a sticking point.
Toby
On Thu, Aug 10, 2017
Yea, I saw that. I'll ask NERSC. As I recall the auto stuff was for p4est.
It seems to die before that.
On Thu, Aug 10, 2017 at 10:21 AM, Matthew Knepley wrote:
> On Wed, Aug 9, 2017 at 7:42 PM, Mark Adams wrote:
>
>> NERSC changed some stuff and my configure is crashing. Any ideas?
>>
>
> It s
On Wed, Aug 9, 2017 at 7:42 PM, Mark Adams wrote:
> NERSC changed some stuff and my configure is crashing. Any ideas?
>
It sure looks like you have a module problem:
Executing: cc -c -o /tmp/petsc-BbxLhU/config.setCompilers/conftest.o
-I/tmp/petsc-BbxLhU/config.setCompilers
/tmp/petsc-BbxLhU/co
I have attempted to fix this for BlasLapack and its download variants with
the branch
barry/update-blaslapack-support-download-batch now in next
> On Dec 29, 2016, at 11:03 AM, Satish Balay wrote:
>
> I don't understand the batch code. I suspect the change from building
> packages from pr
I don't understand the batch code. I suspect the change from building
packages from pre-reconfigure to reconfigure happened in
package.py. However blaslapack doesn't use package.py?
And blaslapack.py appears to do checksdotreturnsdouble() test - which
it needs to do during batch test - so it would
> On Dec 29, 2016, at 10:03 AM, Satish Balay wrote:
>
> I suspect blaslpack along with mpi cannot be installed in batch mode anymore.
This is nuts! It should be able to build blaslapack. And it certainly
shouldn't just chug along without a big error message instead of pretending the
optio
> On Dec 29, 2016, at 5:25 PM, Mark Adams wrote:
>
>
> BTW: Why use --download-fblaslapack on cray? [and not system blas - like
> cray-libsci]
>
> Excellent question. Same answer as how did I spend a week preintf debugging
> in November. The LAPACK invert method in MKL (at NERSC) used in Ple
>
>
> BTW: Why use --download-fblaslapack on cray? [and not system blas - like
> cray-libsci]
>
Excellent question. Same answer as how did I spend a week preintf debugging
in November. The LAPACK invert method in MKL (at NERSC) used in Plex gaves
differences (the ones that I saw were small) that r
I suspect blaslpack along with mpi cannot be installed in batch mode anymore.
[at some point all pacakges were installed before reconfigure. And I think this
was
switched to - install packages during reconfigure. Ideally there should be
proper
dependencies on the 'batch' part - so that only pack
--with-batch=0 seems to fix the problem.
On Thu, Dec 29, 2016 at 4:40 AM, Mark Adams wrote:
> BTW, I cloned this (working) config file and changed to single precision
> and 32 bit ints, and added with-batch=1.
>
> On Wed, Dec 28, 2016 at 11:20 PM, Satish Balay wrote:
>
>> I can reproduce this i
BTW, I cloned this (working) config file and changed to single precision
and 32 bit ints, and added with-batch=1.
On Wed, Dec 28, 2016 at 11:20 PM, Satish Balay wrote:
> I can reproduce this issue. [we don't notice it normally because
> default system blas is usually found - so there is no error
I can reproduce this issue. [we don't notice it normally because
default system blas is usually found - so there is no error..]
Satish
On Wed, 28 Dec 2016, Barry Smith wrote:
>
> Mark,
>
>Yes this is odd. You clearly have --download-fblaslapack=1 but then in
> the file it has
>
> TEST
Mark,
Yes this is odd. You clearly have --download-fblaslapack=1 but then in the
file it has
TEST alternateConfigureLibrary from
config.packages.fblaslapack(/global/u2/m/madams/petsc/config/BuildSystem/config/package.py:761)
TESTING: alternateConfigureLibrary from
config.packages.fblasl
WTF, I guess NERSC made aprun not visible on the login nodes. This used to
work.
Thanks, (I did see that but figured it must be cause by something esle)
On Sat, May 9, 2015 at 7:14 AM, Matthew Knepley wrote:
> It cannot find aprun in your path.
>
> Modules are absolutely the best way to use su
It cannot find aprun in your path.
Modules are absolutely the best way to use supercomputer.
Matt
On Sat, May 9, 2015 at 5:30 AM, Mark Adams wrote:
> I am getting this on Edison. This configure script has worked before.
> mark
>
--
What most experimenters take for granted before they b
Mark,
Thanks for the update. Sounds like all cmake (version) installs on
edison would benefit from this patch.
[and we should be wary of using --download-cmake on it]
Satish
On Mon, 9 Feb 2015, Mark Adams wrote:
> FYI, this why 2.8.11.2 worked and 2.8.12.2 failed. Nothing to do with real
> ve
FYI, this why 2.8.11.2 worked and 2.8.12.2 failed. Nothing to do with real
versions of Cmake.
Glad to hear 2.8.11.2 seems to do the trick! I asked around, and it sounds
like we manually commented out the -rdynamic from the platform cmake file
(Platform/Linux.cmake) for that version in order to ge
FYI, this is what NERSC tells me. I tired cmake/3.0.0 but I got an error
from PETSc I think saying Metis needs v2.8. (This should probably be
fixed.) The CRAYPE_LINK_TYPE=dynamic did not seem to play nice with my
configuration ('--with-shared-libraries=0') but cmake/2.8.11.2 seems to be
working.
Damn, this was working a week ago. I've tried many things and am now just
doing a 'make config' in metis and see this -rdynamic thing. I will ask
NERSC.
Thanks,
Mark
On Sun, Feb 8, 2015 at 10:34 AM, Satish Balay wrote:
> On Sat, 7 Feb 2015, Mark Adams wrote:
>
> > I am getting errors again w
On Sat, 7 Feb 2015, Mark Adams wrote:
> I am getting errors again with metis. This has come up on Hopper but this
> looks different.
> Mark
>
-- Check for working C compiler: /opt/cray/craype/2.2.1/bin/cc -- broken
/opt/cray/craype/2.2.1/bin/cc -fast -no-ipo
CMakeFiles/cmTryC
Fixed
I botched a manual merge
> On Oct 23, 2014, at 7:31 AM, Stefano Zampini
> wrote:
>
> just pulled from master (I'm using python 2.7.8)
>
> ===
> Configuring PETSc to compile on your system
just pulled from master (I'm using python 2.7.8)
===
Configuring PETSc to compile on your system
===
***
On 19 April 2012 18:04, Jed Brown wrote:
> On Thu, Apr 19, 2012 at 08:01, Mark F. Adams
> wrote:
>>
>> [I sent this error message but it "Your message to petsc-dev awaits
>> moderator approval" because the configure.log was > 512 Kb???]
>
>
> Configure issues (and especially configure.log attachm
On Thu, 19 Apr 2012, Lisandro Dalcin wrote:
> On 19 April 2012 18:04, Jed Brown wrote:
> > On Thu, Apr 19, 2012 at 08:01, Mark F. Adams
> > wrote:
> >>
> >> [I sent this error message but it "Your message to petsc-dev awaits
> >> moderator approval" because the configure.log was > 512 Kb???]
> >
yes - such issues [with huge attachments] shouldn't flood mailing list
user mailboxes - and are best sent to petsc-maint.
suggestion is to use:
CC=/sw/lib/gcc4.4/bin/gcc-4 CFLAGS=-malign-double
[instead of CC="/sw/lib/gcc4.4/bin/gcc-4 -malign-double"]
Satish
On Thu, 19 Apr 2012, Mark F. Adams w
On Thu, Apr 19, 2012 at 08:01, Mark F. Adams wrote:
> [I sent this error message but it "Your message to petsc-dev awaits
> moderator approval" because the configure.log was > 512 Kb???]
Configure issues (and especially configure.log attachments) belong on
petsc-maint, not petsc-dev.
---
[I sent this error message but it "Your message to petsc-dev awaits moderator
approval" because the configure.log was > 512 Kb???]
I'm moving to a serial build on my Mac and am getting this error:
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
C
I'm getting this error in a Cray:
madams/petsc-dev-new> ./cray-xe6-dbg.py
===
Configuring PETSc to compile on your system
can you also pull Buildsystem?
Satish
On Thu, 25 Aug 2011, Mark F. Adams wrote:
> I'm getting this error in a Cray:
>
> madams/petsc-dev-new> ./cray-xe6-dbg.py
> ===
> Configuring PETSc to compile on your
37 matches
Mail list logo
