[petsc-dev] Experimental GNU make build system
Satish Balay
balay at mcs.anl.gov
Wed May 22 18:22:16 CDT 2013
Looks like it can will work on windows.
For one it doesn't like gcc options like -MDD. [gives warnings] - so I removed that.
And - cl [or win32fe?] is not liking empty LOCDIR for "-D__INSDIR__=${LOCDIR}"
so I removed that.
The build with 'make -j 8' goes through quickly until:
CLINKER /home/balay/petsc.clone/arch-gmake/lib/libpetsc.so
[so a static library target will perhaps fix this issue]
Satish
---------
CLINKER /home/balay/petsc.clone/arch-gmake/lib/libpetsc.so
0 [main] sh 3108 child_info_fork::abort: can't commit memory for stack 0x2
8A000(90112), Win32 error 487
/usr/bin/sh: fork: retry: Resource temporarily unavailable
0 [main] sh 1824 child_info_fork::abort: can't commit memory for stack 0x2
8A000(90112), Win32 error 487
/usr/bin/sh: fork: retry: Resource temporarily unavailable
0 [main] sh 3548 child_info_fork::abort: can't commit memory for stack 0x2
8A000(90112), Win32 error 487
/usr/bin/sh: fork: retry: Resource temporarily unavailable
0 [main] sh 2908 child_info_fork::abort: can't commit memory for stack 0x2
8A000(90112), Win32 error 487
/usr/bin/sh: fork: retry: Resource temporarily unavailable
0 [main] sh 2872 child_info_fork::abort: can't commit memory for stack 0x2
8A000(90112), Win32 error 487
/usr/bin/sh: fork: Resource temporarily unavailable
gmakefile:59: recipe for target `/home/balay/petsc.clone/arch-gmake/lib/libpetsc
.so' failed
make: *** [/home/balay/petsc.clone/arch-gmake/lib/libpetsc.so] Error 254
balay at msnehalem2 ~/petsc.clone
$
On Mon, 20 May 2013, Barry Smith wrote:
>
> And does this solve the Windows problem?
>
> On May 20, 2013, at 4:46 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
>
> > I just merged 'jed/gnumake' to 'next'. I haven't added support for
> > static libraries yet, but it should work with pretty much all other
> > configurations using compilers that support '-MMD -MP' (tested with gcc,
> > clang, and intel; C, C++, and Fortran; single and multiple library).
> >
> > $ make -f gmakefile -j20 PETSC_ARCH=your-choice
> >
> > The makefile is 100 lines and the Python for figuring out what to
> > include in the build is about the same (conf/gmakegen.py; neglecting
> > python-2.4 compatibility stuff). Simplifying the rules would reduce
> > that, naturally.
> >
> > Let me know how it works for you.
>
>
More information about the petsc-dev
mailing list