Re: [petsc-dev] CMake on Catalina

Yeah - there as prior e-mail on OSX discrepancies. Note all 3 boxes are on 10.15 - and Xcode-11+. Is 10.14 SDK a reference to Xcode-10? Satish --- balay@jpro^~ $ xcodebuild -version Xcode 11.3.1 Build version 11C504 The other tow boxes are now giving: ipro:~ balay$ xcodebuild -V xcode-select:

Re: [petsc-dev] CMake on Catalina

This looks similar to last month message "[petsc-maint] GNU toolchain on macOS”, you probably need to go back to the 10.14 SDK. Thanks, Pierre > On 18 Apr 2020, at 3:59 AM, Satish Balay via petsc-dev > wrote: > > I just did the following build on 3 of the OSX test boxes. [with brew gcc >

Re: [petsc-dev] CMake on Catalina

I just did the following build on 3 of the OSX test boxes. [with brew gcc etc..] balay@jpro^~/petsc(maint) $ ./configure --with-mpi=0 CC=gcc-9 CXX=g++-9 FC=gfortran-9 --download-cmake Worked on 2 of them. The 3rd failed with PETSc configure errors. As far as I can tell - all 3 systems should

Re: [petsc-dev] CMake on Catalina

CMake itself. On Catalina, the SSL/TLS headers use special syntax that only Clang can parse. You should check for this in the configure stage, but they do not. The response for the error reports on the CMake Github was that you should not be building on Apple with something that won't parse some

Re: [petsc-dev] CMake on Catalina

Build cmake or a package using cmake? balay@sb /home/balay/petsc (master=) $ grep download-cmake config/examples/arch-ci-osx-* config/examples/arch-ci-osx-cxx-cmplx-pkgs-dbg.py: '--download-cmake=1', config/examples/arch-ci-osx-cxx-pkgs-opt.py: '--download-cmake=1',

Re: [petsc-dev] CMake on Catalina

CMake is a great tool, > On Apr 18, 2020, at 06:36, Matthew Knepley wrote: > > I have just spent hours trying to build CMake on Catalina. This is not a > configure system. I finally had to just comment out a bunch of source files > in their build system, and define out a bunch of code. I

[petsc-dev] CMake on Catalina

I have just spent hours trying to build CMake on Catalina. This is not a configure system. I finally had to just comment out a bunch of source files in their build system, and define out a bunch of code. I can't believe this works anywhere. Matt -- What most experimenters take for granted

[petsc-dev] CMake

Can we remove all packages that use CMake before the next release? See also "/PETSc3/petsc/petsc-pylith/arch-next-debug/externalpackages/hg.eigen/build/CMakeFiles/CMakeOutput.log".CMake Error at /PETSc3/petsc/petsc-pylith/arch-pylith-debug/share/cmake-3.0/Modules/Platform/Darwin.cmake:211

Re: [petsc-dev] CMake: make, install, find_package ?

ot; <knep...@gmail.com>, "petsc-dev" <petsc-dev@mcs.anl.gov> > Envoyé: Mardi 7 Novembre 2017 10:28:31 > Objet: Re: [petsc-dev] CMake: make, install, find_package ? > > On 7 November 2017 at 09:17, Franck Houssen <franck.hous...@inria.fr> wrote: > > See

Re: [petsc-dev] CMake: make, install, find_package ?

; À: "Franck Houssen" <franck.hous...@inria.fr> > Cc: "petsc-dev" <petsc-dev@mcs.anl.gov> > Envoyé: Lundi 6 Novembre 2017 19:28:57 > Objet: Re: [petsc-dev] CMake: make, install, find_package ? > > On Mon, Nov 6, 2017 at 12:49 PM, Franck Houssen <franck

Re: [petsc-dev] CMake: make, install, find_package ?

ia.fr> > Cc: "petsc-dev" <petsc-dev@mcs.anl.gov> > Envoyé: Lundi 6 Novembre 2017 19:28:57 > Objet: Re: [petsc-dev] CMake: make, install, find_package ? > On Mon, Nov 6, 2017 at 12:49 PM, Franck Houssen < franck.hous...@inria.fr > > wrote: > > - Mail ori

Re: [petsc-dev] CMake: make, install, find_package ?

t; <petsc-dev@mcs.anl.gov> > > Envoyé: Lundi 6 Novembre 2017 16:08:55 > > Objet: Re: [petsc-dev] CMake: make, install, find_package ? > > > > On Mon, 6 Nov 2017, Franck Houssen wrote: > > > > > > > > Yes ! Your friend let you the keys of his car. The car

Re: [petsc-dev] CMake: make, install, find_package ?

- Mail original - > De: "Satish Balay" <ba...@mcs.anl.gov> > À: "Franck Houssen" <franck.hous...@inria.fr> > Cc: "petsc-dev" <petsc-dev@mcs.anl.gov> > Envoyé: Lundi 6 Novembre 2017 16:08:55 > Objet: Re: [petsc-dev] CMake

Re: [petsc-dev] CMake: make, install, find_package ?

On Mon, 6 Nov 2017, Franck Houssen wrote: > > Yes ! Your friend let you the keys of his car. The car has no wheel. Why did > he gave you his keys ?!... :D (joking) Actually - its more akin to - friend gives you a car - and leaves the keys in the console, with instructions there. However you

Re: [petsc-dev] CMake: make, install, find_package ?

Looks like you had a bad experience with CMake up to a point of no return (probably a shame, but, I can understand that !). I will use pkg-config: that's fine to me. I was just trying to help here for sake of community ! No more, no less ! Franck - Mail original - > De: "Satish Balay"

Re: [petsc-dev] CMake: make, install, find_package ?

> On Nov 5, 2017, at 8:01 AM, Jed Brown wrote: > >> >> Sure - if you hunt arround the PETSc source tree - you will find bunch >> of stuff.. [but that would be ignoring the primary doc]. >> >> Also There was some reason Jed didn't want to strip out the cmake >> stuff.

Re: [petsc-dev] CMake: make, install, find_package ?

! Bonne journée, Franck - Mail original - > De: "Satish Balay" <ba...@mcs.anl.gov> > À: "Jed Brown" <j...@jedbrown.org> > Cc: "Franck Houssen" <franck.hous...@inria.fr>, "petsc-dev" > <petsc-dev@mcs.anl.gov> >

Re: [petsc-dev] CMake: make, install, find_package ?

gt; > Scanning dependencies of target petsc > > [ 0%] Building Fortran object > > CMakeFiles/petsc.dir/src/sys/f90-mod/petscsysmod.F.o > > [ 0%] Building Fortran object > > CMakeFiles/petsc.dir/src/vec/f90-mod/petscvecmod.F.o > > ... > > > > - Mail original

Re: [petsc-dev] CMake: make, install, find_package ?

t;Satish Balay" <ba...@mcs.anl.gov> >> À: "Franck Houssen" <franck.hous...@inria.fr> >> Cc: "petsc-dev" <petsc-dev@mcs.anl.gov>, "Jed Brown" <j...@jedbrown.org> >> Envoyé: Dimanche 5 Novembre 2017 15:52:44 >> Objet

Re: [petsc-dev] CMake: make, install, find_package ?

Satish Balay writes: > On Sun, 5 Nov 2017, Franck Houssen wrote: > >> Personal opinion: either you decide to have a fresh look at this (things may >> be better now), or, you should unplug the generation of CMakeLists.txt >> (misleading). > > Hm - configure prints at the

Re: [petsc-dev] CMake: make, install, find_package ?

ail original - > De: "Satish Balay" <ba...@mcs.anl.gov> > À: "Franck Houssen" <franck.hous...@inria.fr> > Cc: "petsc-dev" <petsc-dev@mcs.anl.gov>, "Jed Brown" <j...@jedbrown.org> > Envoyé: Dimanche 5 Novembre 2017 15:

Re: [petsc-dev] CMake: make, install, find_package ?

he development version of PETSc" < > petsc-dev@mcs.anl.gov> > *Envoyé: *Dimanche 5 Novembre 2017 15:09:30 > *Objet: *Re: [petsc-dev] CMake: make, install, find_package ? > > On Sun, Nov 5, 2017 at 8:57 AM, Franck Houssen <franck.hous...@inria.fr> > wrote: > &

Re: [petsc-dev] CMake: make, install, find_package ?

On Sun, 5 Nov 2017, Franck Houssen wrote: > > Or are you having trouble with > > https://github.com/jedbrown/cmake-modules/blob/master/FindPETSc.cmake ? > > [and not with PETSc build?] > > At first, I was trying to understand why find_package(petsc) was not working. > So then, I looked at the

Re: [petsc-dev] CMake: make, install, find_package ?

On Sun, 5 Nov 2017, Franck Houssen wrote: > Personal opinion: either you decide to have a fresh look at this (things may > be better now), or, you should unplug the generation of CMakeLists.txt > (misleading). Hm - configure prints at the end:

Re: [petsc-dev] CMake: make, install, find_package ?

- Mail original - > De: "Satish Balay" <ba...@mcs.anl.gov> > À: "petsc-dev" <petsc-dev@mcs.anl.gov> > Cc: "Franck Houssen" <franck.hous...@inria.fr> > Envoyé: Dimanche 5 Novembre 2017 15:16:48 > Objet: Re: [petsc-dev] CMake

Re: [petsc-dev] CMake: make, install, find_package ?

- Mail original - > De: "Matthew Knepley" <knep...@gmail.com> > À: "Franck Houssen" <franck.hous...@inria.fr> > Cc: "For users of the development version of PETSc" <petsc-dev@mcs.anl.gov> > Envoyé: Dimanche 5 Novembre

Re: [petsc-dev] CMake: make, install, find_package ?

BTW: why are prefering all-cmake build over all-gnumake build? Or are you having trouble with https://github.com/jedbrown/cmake-modules/blob/master/FindPETSc.cmake ? [and not with PETSc build?] Satish On Sun, 5 Nov 2017, Satish Balay wrote: > PETSc has 3 modes of building libraries > > 1.

Re: [petsc-dev] CMake: make, install, find_package ?

On Sun, Nov 5, 2017 at 8:57 AM, Franck Houssen wrote: > Hello, > > Does PETSc provide support for CMake ? I would say this is an on-going > feature that is not yet fully working, right ? > > My understanding is that "./configure" generates the CMakeLists.txt. But > then,

[petsc-dev] CMake: make, install, find_package ?

Hello, Does PETSc provide support for CMake ? I would say this is an on-going feature that is not yet fully working, right ? My understanding is that "./configure" generates the CMakeLists.txt. But then, when using cmake, make fails. Is this supposed to work yet ? Or is this on-going dev ?

Re: [petsc-dev] CMake

Matthew Knepley knep...@gmail.com writes: Now that it is no longer the default build, can we stop it generating Makefile in $PETSC_ARCH? Should we just stop autodetecting the cmake executable? Users that want it can use --with-cmake=/usr/bin/cmake. pgp50uArkwQaa.pgp Description: PGP

Re: [petsc-dev] CMake

On Wed, 18 Dec 2013, Jed Brown wrote: Matthew Knepley knep...@gmail.com writes: Now that it is no longer the default build, can we stop it generating Makefile in $PETSC_ARCH? Should we just stop autodetecting the cmake executable? Users that want it can use

Re: [petsc-dev] CMake

Satish Balay ba...@mcs.anl.gov writes: Alternate is to have all cmake files in PETSC_DIR/PETSC_ARCH/cmakebuild [instead of the current location PETSC_DIR/PETSC_ARCH] I think Matt is annoyed with the presence of Makefile causing noise in his detector (which is supposed to enforce that PETSc

[petsc-dev] CMake

Now that it is no longer the default build, can we stop it generating Makefile in $PETSC_ARCH? Matt -- 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

[petsc-dev] CMake-assisted CUDA builds ready

at mcs.anl.gov] on behalf of Jose E. Roman [jroman at dsic.upv.es] Sent: Tuesday, March 26, 2013 3:44 PM To: For users of the development version of PETSc Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready El 26/03/2013, a las 21:08, Karl Rupp escribi?: Hi again, thanks, I think I

[petsc-dev] CMake-assisted CUDA builds ready

of PETSc Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready El 26/03/2013, a las 21:08, Karl Rupp escribi?: Hi again, thanks, I think I could eliminate the cause. Please give 'next' another try... Thanks and best regards, Karli Yes, it works now. Thanks.

[petsc-dev] CMake-assisted CUDA builds ready

I get errors in the cmake build (in 'next'): /usr/local/cuda/bin/nvcc /home/jroman/soft/petsc/src/mat/impls/aij/mpi/mpicusparse/mpiaijcusparse.cu -O -arch=sm_13 --compiler-options , -fPIC\,\-Wall\,\-Wwrite-strings\,\-Wno-strict-aliasing\,\-Wno-unknown-pragmas\,\-O\ \ -m64 -D__INSDIR__=

[petsc-dev] CMake-assisted CUDA builds ready

Hi Jose, No need to send the logs, I can see the problem: Something is going wrong when dealing with double-quotes. The flag string --compiler-options ,\-fPIC\,\-Wall\,\-Wwrite-strings\,\-Wno-strict-aliasing\,\-Wno-unknown-pragmas\,\-O\ gets passed through BuildSystem, which tries to put

[petsc-dev] CMake-assisted CUDA builds ready

Hi Jose, alright, the problem should be fixed in 'next' now. The problem was in CMake not consistently interpreting escaped double quotes. Best regards, Karli On 03/26/2013 09:40 AM, Jose E. Roman wrote: I get errors in the cmake build (in 'next'): /usr/local/cuda/bin/nvcc

[petsc-dev] CMake-assisted CUDA builds ready

El 26/03/2013, a las 16:19, Karl Rupp escribi?: Hi Jose, alright, the problem should be fixed in 'next' now. The problem was in CMake not consistently interpreting escaped double quotes. Best regards, Karli Not yet solved: /usr/local/cuda/bin/nvcc

[petsc-dev] CMake-assisted CUDA builds ready

Hi Jose, which host compiler do you use? nvcc seems to have problems with double-quoted flags such as -O -arch=sm_13 . Thanks and best regards, Karli On 03/26/2013 11:03 AM, Jose E. Roman wrote: El 26/03/2013, a las 16:19, Karl Rupp escribi?: Hi Jose, alright, the problem should be

[petsc-dev] CMake-assisted CUDA builds ready

El 26/03/2013, a las 17:27, Karl Rupp escribi?: Hi Jose, which host compiler do you use? nvcc seems to have problems with double-quoted flags such as -O -arch=sm_13 . Thanks and best regards, Karli $ nvcc -V nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2012 NVIDIA

[petsc-dev] CMake-assisted CUDA builds ready

Hi again, thanks, I think I could eliminate the cause. Please give 'next' another try... Thanks and best regards, Karli On 03/26/2013 11:28 AM, Jose E. Roman wrote: El 26/03/2013, a las 17:27, Karl Rupp escribi?: Hi Jose, which host compiler do you use? nvcc seems to have problems with

[petsc-dev] CMake-assisted CUDA builds ready

El 26/03/2013, a las 21:08, Karl Rupp escribi?: Hi again, thanks, I think I could eliminate the cause. Please give 'next' another try... Thanks and best regards, Karli Yes, it works now. Thanks.

[petsc-dev] CMake-assisted CUDA builds ready

: Tuesday, March 19, 2013 4:04 PM To: petsc-dev at mcs.anl.gov Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready Hi Dave, perfect, thanks! I should add that a reconfigure is needed. It won't work with re

[petsc-dev] CMake-assisted CUDA builds ready

at mcs.anl.gov] on behalf of Karl Rupp [rupp at mcs.anl.gov] Sent: Tuesday, March 19, 2013 4:04 PM To: petsc-dev at mcs.anl.gov Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready Hi Dave, perfect, thanks! I should add

[petsc-dev] CMake-assisted CUDA builds ready

From: petsc-dev-bounces at mcs.anl.gov [petsc-dev-bounces at mcs.anl.gov] on behalf of Karl Rupp [rupp at mcs.anl.gov] Sent: Tuesday, March 19, 2013 4:04 PM To: petsc-dev at mcs.anl.gov Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready

[petsc-dev] CMake-assisted CUDA builds ready

: Re: [petsc-dev] CMake-assisted CUDA builds ready Hi Dave, perfect, thanks! I should add that a reconfigure is needed. It won't work with re-running make only. Best regards, Karli On 03/19/2013 04:59 PM, Nystrom, William D wrote: Hi

[petsc-dev] CMake-assisted CUDA builds ready

: Tuesday, March 19, 2013 4:04 PM To: petsc-dev at mcs.anl.gov Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready Hi Dave, perfect, thanks! I should add that a reconfigure is needed. It won't work with re-running make only. Best regards, Karli On 03/19/2013 04:59 PM, Nystrom, William D

[petsc-dev] CMake-assisted CUDA builds ready

, March 19, 2013 4:04 PM To: petsc-dev at mcs.anl.gov Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready Hi Dave, perfect, thanks! I should add that a reconfigure is needed. It won't work with re-running make only. Best regards, Karli On 03/19/2013 04:59 PM, Nystrom, William D

[petsc-dev] CMake-assisted CUDA builds ready

:04 PM To: petsc-dev at mcs.anl.gov Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready Hi Dave, perfect, thanks! I should add that a reconfigure is needed. It won't work with re-running make only. Best regards, Karli On 03/19/2013 04:59 PM, Nystrom, William D wrote: Hi Karli

[petsc-dev] CMake-assisted CUDA builds ready

On Wed, Mar 20, 2013 at 2:03 PM, Karl Rupp rupp at mcs.anl.gov wrote: I also found that in some occasions one should issue gt; rm -rf PETSC_ARCH/CMake* prior to running a reconfigure in order to circumvent a bug [1] in CMake. @Jed, Matt: The current cmakeboot.py removes

[petsc-dev] CMake-assisted CUDA builds ready

Hi Jed, On 03/20/2013 02:09 PM, Jed Brown wrote: On Wed, Mar 20, 2013 at 2:03 PM, Karl Rupp rupp at mcs.anl.gov mailto:rupp at mcs.anl.gov wrote: I also found that in some occasions one should issue gt; rm -rf PETSC_ARCH/CMake* prior to running a reconfigure in order to

[petsc-dev] CMake-assisted CUDA builds ready

On Wed, Mar 20, 2013 at 3:19 PM, Karl Rupp rupp at mcs.anl.gov wrote: Yes, I know that this is a heavy operation. On the other hand, it only occurs after a reconfigure, so it's not supposed to happen too often. Anyway, with CUDA enabled I can deterministically reproduce the error in `next`:

[petsc-dev] CMake-assisted CUDA builds ready

From: petsc-dev-bounces at mcs.anl.gov [petsc-dev-bounces at mcs.anl.gov] on behalf of Karl Rupp [rupp at mcs.anl.gov] Sent: Tuesday, March 19, 2013 4:04 PM To: petsc-dev at mcs.anl.gov Subject: Re: [petsc-dev] CMake-assisted CUDA

[petsc-dev] cmake 2.8-10.1 failing on my mac

I upgraded cmake on my mac and now configure hangs will running cmake. If I kill the cmake process I see the following in configure.log When I use --download-cmake and it gets the old version then that runs fine. Has PETSc's cmake stuff been tested with 2.8-10.1? Barry

[petsc-dev] cmake 2.8-10.1 failing on my mac

Yup this also works on Mountain lion with the latest Xcode. Must be something about the .dmg Mac specific Application build that fucks it up. No worries, I've just backed out to using the the older version for my work. BTW: whoever added support for --download-xxx=http: thanks!

[petsc-dev] cmake 2.8-10.1 failing on my mac

On Wed, Nov 7, 2012 at 10:32 PM, Satish Balay balay at mcs.anl.gov wrote: Could not read file /Users/barrysmith/Src/petsc-dev/arch-test/CMakeCache.txt: IOError(2, 'No such file or directory') I'm not sure what this means. Jed might have ideas. It means you have to wipe the disk and

[petsc-dev] CMake version

*** lib/petsc-dev cmake cmake version 2.8.4 Just tell me, something has been changed in petsc or it's rather my machine? Regards, Alexander

[petsc-dev] CMake version

/config/package.py, line 183, in getInstallDir return os.path.abspath(self.Install()) File /home/lib/petsc-dev/config/PETSc/packages/metis.py, line 30, in Install raise RuntimeError('CMake 2.8.5 is needed to build METIS') lib/petsc-dev cmake -version cmake version 2.8.6

[petsc-dev] CMake version

') lib/petsc-dev cmake -version cmake version 2.8.6 On 09.12.2011 09:56, Alexander Grayver wrote: Hi dev-team, Yesterday I duilt petsc-dev successfully, today I updated it and tried to reconfigure: --- CMake

[petsc-dev] cmake problem

Jed, Please see the error below. What is the approved way to recover from something incomprehensible to me like this? Shouldn't a reconfigure clean up all possible dangers? Thanks Barry barry-smiths-macbook-pro:petsc-dev barrysmith$ ./arch-gnu/conf/reconfigure-arch-gnu.py

[petsc-dev] cmake problem

Does make -C $PETSC_ARCH clean fix the problem. I don't know what caused this in the first place. I'd rather not always have reconfigure clean because it usually means needless compiling. I guess normal make clean should clean the CMake part as well... On Sep 23, 2011 5:23 PM, Barry Smith bsmith

[petsc-dev] cmake problem

On Sep 23, 2011, at 5:54 PM, Jed Brown wrote: Does make -C $PETSC_ARCH clean fix the problem. I don't know what caused this in the first place. I started a make without the cmake part then control-ced it because I didn't want to waste time for it (a thing that could happen all the time).

[petsc-dev] cmake --with-matlab build

Jed, Looks like cmake does not do part of the matlab build.. libfast in: /sandbox/balay/petsc-dev/src/sys/viewer/impls/socket/matlab BEGINNING TO COMPILE MATLAB INTERFACE Warning: You are using gcc version 4.4.3-4ubuntu5). The version currently supported with MEX is 4.3.4.

[petsc-dev] cmake --with-matlab build

Perhaps we should pull it out to the toplevel 'matlab' target - which does this build for both cases? i.e all: make all-cmake matlab or make all-legacy matlab Also: [For Barry] from src/sys/viewer/impls/socket/matlab/makefile sread: -@${MATLAB_MEX} -g CC='${PCC}'

[petsc-dev] cmake --with-matlab build

On Aug 23, 2011, at 3:54 PM, Satish Balay wrote: Perhaps we should pull it out to the toplevel 'matlab' target - which does this build for both cases? i.e all: make all-cmake matlab or make all-legacy matlab Also: [For Barry] from src/sys/viewer/impls/socket/matlab/makefile

[petsc-dev] cmake --with-matlab build

On Tue, 23 Aug 2011, Barry Smith wrote: On Aug 23, 2011, at 3:54 PM, Satish Balay wrote: Perhaps we should pull it out to the toplevel 'matlab' target - which does this build for both cases? i.e all: make all-cmake matlab or make all-legacy matlab Also: [For

[petsc-dev] cmake problem

Reran ./configure but then cmake made me trouble. Sending the configure.log only to Jed Barry xxx=xxx Configure stage complete. Now build PETSc libraries with: make PETSC_DIR=/Users/barrysmith/Src/petsc-dev

[petsc-dev] cmake problem

On Fri, Jul 8, 2011 at 14:28, Barry Smith bsmith at mcs.anl.gov wrote: Reran ./configure but then cmake made me trouble. Sending the configure.log only to Jed Barry xxx=xxx Configure stage complete. Now build

[petsc-dev] cmake problem

On Fri, Jul 8, 2011 at 14:28, Barry Smith bsmith at mcs.anl.gov wrote: cd /Users/barrysmith/Src/petsc-dev; make -j2 -C /Users/barrysmith/Src/petsc-dev/arch-gnu Scanning dependencies of target petsc Error copying Fortran module include/petscsys. Tried include/PETSCSYS.mod and

[petsc-dev] cmake problem

Seems to have worked, thanks. Barry On Jul 8, 2011, at 3:54 PM, Jed Brown wrote: On Fri, Jul 8, 2011 at 14:28, Barry Smith bsmith at mcs.anl.gov wrote: cd /Users/barrysmith/Src/petsc-dev; make -j2 -C /Users/barrysmith/Src/petsc-dev/arch-gnu Scanning dependencies of target petsc

[petsc-dev] CMake broken

CMake build is broken in the latest petsc-dev: cmakeboot does not generate the makefiles. I have made a bisection search and found this changeset in BuildSystem: http://petsc.cs.iit.edu/petsc/BuildSystem/rev/bbad23803405 If I uncomment the line USE_SUBPROCESS = 0 in config/Buildsystem/script.py

[petsc-dev] CMake broken

pushed the change. satish On Wed, 11 May 2011, Barry Smith wrote: That is my fault. I messed with that SUBPROCESS file a long time ago and forgot I changed it, then when I put in proper changes I left that bad change. Satish, can you remove the comment of the subprocess stuff and

[petsc-dev] cmake and fortranstubs

On Dec 1, 2010, at 11:48 AM, Jed Brown wrote: On Wed, Dec 1, 2010 at 18:24, Barry Smith bsmith at mcs.anl.gov wrote: It would be nice if cmake also updated the appropriate fortranstubs. Make generatefortranstubs.py have a way to update individual files and I will make cmake do the

[petsc-dev] cmake and fortranstubs

... [ 87%] Building C object CMakeFiles/petsc.dir/src/ksp/pc/impls/gasm/ftn-auto/gasmf.c.o [ 88%] Building C object CMakeFiles/petsc.dir/src/ksp/pc/impls/composite/ftn-auto/compositef.c.o /Users/barrysmith/Src/petsc-dev/src/ksp/pc/impls/gasm/ftn-auto/gasmf.c: In function

[petsc-dev] cmake and fortranstubs

On Wed, Dec 1, 2010 at 18:24, Barry Smith bsmith at mcs.anl.gov wrote: It would be nice if cmake also updated the appropriate fortranstubs. Make generatefortranstubs.py have a way to update individual files and I will make cmake do the generated files automatically. I might do it anyway, but

[petsc-dev] cmake issue

Jed, I had a file src/mat/impls/schur/ftn-auto/schurmf.c around coming from old builds, I did not noticed it until now because of hgignore . Trying to build with cmake failed because it tried to compile that outdated file. Not a big deal, but I'm wondering if it would be easy to fix? --

[petsc-dev] cmake issue

On Mon, Oct 4, 2010 at 14:21, Lisandro Dalcin dalcinl at gmail.com wrote: Jed, I had a file ?src/mat/impls/schur/ftn-auto/schurmf.c around coming from old builds, I did not noticed it until now because of hgignore . Trying to build with cmake failed because it tried to compile that outdated

[petsc-dev] cmake issue

On 4 October 2010 10:51, Jed Brown five9a2 at gmail.com wrote: On Mon, Oct 4, 2010 at 14:21, Lisandro Dalcin dalcinl at gmail.com wrote: Jed, I had a file ?src/mat/impls/schur/ftn-auto/schurmf.c around coming from old builds, I did not noticed it until now because of hgignore . Trying to build

[petsc-dev] cmake issue

On Mon, Oct 4, 2010 at 18:39, Lisandro Dalcin dalcinl at gmail.com wrote: Well, from 2 years ago up to now, I've reconfigured many times. It seems the ftn-auto directory was not automatically removed. That is because the *parent* of the ftn-auto directory was deleted from Hg. I could actually

[petsc-dev] cmake issue

On Mon, Oct 4, 2010 at 18:48, Jed Brown jed at 59a2.org wrote: On Mon, Oct 4, 2010 at 18:39, Lisandro Dalcin dalcinl at gmail.com wrote: Well, from 2 years ago up to now, I've reconfigured many times. It seems the ftn-auto directory was not automatically removed. That is because the *parent*

[petsc-dev] CMake proof of concept

On Mon, 31 May 2010 19:13:07 -0500, Barry Smith bsmith at mcs.anl.gov wrote: You have an awful lot of confidence in cmake. I have no problem at all setting up a system where PETSc can use cmake, that's great. But I don't want PETSc to ever be in a position of not being able to do

[petsc-dev] CMake proof of concept

In this latest buzz about build systems and IDE integration, I added a CMake build to PETSc. It is entirely contained in bin/maint/cmakegen.py and bin/maint/cmakeboot.py and supports multiple PETSC_ARCH, Fortran, C++ (currently only with-c-support), complex/precision/etc, with and without

[petsc-dev] CMake proof of concept

Likely we need a subdirectory somewhere to put all the make makers. I would like a subdirectory of bin/maint; likely Matt wants a subdirectory of config Currently config is almost all just config stuff, but Matt put his builder.py that makes in there. I don't object to having the make

[petsc-dev] CMake proof of concept

On Mon, 31 May 2010 11:10:36 -0500, Barry Smith bsmith at mcs.anl.gov wrote: Likely we need a subdirectory somewhere to put all the make makers. I would like a subdirectory of bin/maint; likely Matt wants a subdirectory of config Is this really important? It doesn't seem that messy at

[petsc-dev] CMake proof of concept

You have an awful lot of confidence in cmake. I have no problem at all setting up a system where PETSc can use cmake, that's great. But I don't want PETSc to ever be in a position of not being able to do something because kitware/whatever decided that they no longer or would not supported