[petsc-dev] Fwd: [petsc-maint #149715] Making a PetSc Roll and Rocks Module
Barry Smith
bsmith at mcs.anl.gov
Mon Feb 4 23:05:27 CST 2013
Satish,
It looks like the module name should simply be PETSC_VERSION
Could you please make this change? (modules don't make much sense for people self-installs with PETSC_ARCH anyways so no reason to attach PETSC_ARCH to name)
Then the installer person moves the module file (and changes the name if they like) after installing.
Also, check what is inside a PETSc module file at Nersc to make sure we are capturing everything we should capture.
Thanks
Barry
On Feb 4, 2013, at 10:31 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> On Mon, 4 Feb 2013, Barry Smith wrote:
>
>>
>> On Feb 4, 2013, at 8:02 PM, Satish Balay <balay at mcs.anl.gov> wrote:
>>
>>> On Mon, 4 Feb 2013, Barry Smith wrote:
>>>
>>>
>>> If PETSC_ARCH is not specified by user - configure creates one and
>>> uses it. It looks ugly for prefix build - but then - making one build
>>> better means compromising somewere else.
>>>
>>> options:
>>>
>>> - don't use PETSC_ARCH in the module file name [but then rely on users
>>> to rename it when they copy it over to the appropriate location.
>>> - don't use PETSC_ARCH in module name for only prefix installs.
>>> But this becomes inconsistant.
>>> - provide a configure option for users to specify a name for this modulefile.
>>> [defalt always uses PETSC_ARCH]
>>> - [others?]
>>
>> What about ${PETSC_VERSION}${PETSC_ARCH}?
>>
>> The user has to rename/move the module files for prefix installs so maybe we don't need to give it any particular name, just petsc-module?
>>
>> Yes it is ugly without the hyphen but at least without PETSC_ARCH it is consistent.
>>
>> The concept of module file seems silly with PETSC_DIR/PETSC_ARCH installs, should we even make them in that case?
>>
>>
>>
>> BTW: Can you check what the PETSc module files look like at Nersc?
>
> balay at hopper05:~> module avail petsc
>
> ---------------------------------------- /opt/cray/modulefiles -----------------------------------------
> petsc/3.1.04 petsc/3.3.00 petsc-complex/3.2.02(default)
> petsc/3.2.02(default) petsc-complex/3.1.04 petsc-complex/3.3.00
>
> ------------------------------------------- /opt/modulefiles -------------------------------------------
> petsc/3.1.04 petsc/3.3.00 petsc-complex/3.2.02(default)
> petsc/3.2.02(default) petsc-complex/3.1.04 petsc-complex/3.3.00
>
> --------------------------------- /usr/common/acts/Modules/modulefiles ---------------------------------
> petsc/3.1 petsc/3.1_g petsc/3.2_g_complex
> petsc/3.1-opkgs_O petsc/3.1_g_c++ petsc/3.3
> petsc/3.1-opkgs_O_c++ petsc/3.1_g_complex petsc/3.3_O
> petsc/3.1-opkgs_O_complex petsc/3.2 petsc/3.3_O_c++
> petsc/3.1-opkgs_g petsc/3.2_O petsc/3.3_O_complex
> petsc/3.1-opkgs_g_c++ petsc/3.2_O_c++ petsc/3.3_O_tau
> petsc/3.1-opkgs_g_complex petsc/3.2_O_complex petsc/3.3_g
> petsc/3.1_O petsc/3.2_O_tau petsc/3.3_g_c++
> petsc/3.1_O_c++ petsc/3.2_g petsc/3.3_g_complex
> petsc/3.1_O_complex petsc/3.2_g_c++
> balay at hopper05:~>
>
>>
>>
>>
>>>
>>> BTW: I'm not usre if 'lib' is the correct location to stash module/pkgconfig files.
>>> Autoconf install might provide options like --prefix --module-prefix --pkgconfig-prefix?
>>
>> Barrys-MacBook-Pro:petsc-dev barrysmith$ ls /usr/lib/pkgconfig/
>> apr-1.pc apr-util-1.pc libcrypto.pc libedit.pc libiodbc.pc libpcre.pc libpcreposix.pc libssl.pc openssl.pc
>> Barrys-MacBook-Pro:petsc-dev barrysmith$ ls /usr/local/lib/pkgconfig/
>> PETSc.pc libpcre.pc libpcrecpp.pc libpcreposix.pc libpng.pc libpng15.pc libtiff-4.pc tesseract.pc valgrind.pc
>>
>> bsmith at login2:~$ ls /usr/lib/pkgconfig/
>> apr-1.pc dbus-python.pc fontutil.pc glew.pc ibus-table.pc mpich2-c.pc nautilus-sendto.pc printproto.pc python2.pc sawfish.pc
>> apr-util-1.pc fftw3f.pc fuse.pc gnome-system-tools.pc libquvi-scripts.pc mpich2-cxx.pc netcdf.pc pygtksourceview-2.0.pc python-dbg.pc scrnsaverproto.pc
>> cln.pc fftw3l.pc ginac.pc gsl.pc libR.pc mpich2-f77.pc notify-python.pc python-2.7-dbg.pc python.pc valgrind.pc
>> cppunit.pc fftw3.pc ginn.pc gts.pc mcabber.pc mpich2-f90.pc pm-utils.pc python-2.7.pc rep-gtk.pc xorg-wacom.pc
>
> My machine has it at '/usr/
>
> asterix:/home/balay>ls /usr/share/pkgconfig
> bash-completion.pc glproto.pc renderproto.pc xextproto.pc
> bigreqsproto.pc gnome-icon-theme.pc resourceproto.pc xf86bigfontproto.pc
> compositeproto.pc gnome-keybindings.pc scrnsaverproto.pc xf86dgaproto.pc
> damageproto.pc gnome-video-effects.pc shared-mime-info.pc xf86driproto.pc
> dmxproto.pc gtk-doc.pc spice-protocol.pc xf86miscproto.pc
> dri2proto.pc inputproto.pc systemd.pc xf86vidmodeproto.pc
> emacs.pc kbproto.pc udev.pc xineramaproto.pc
> evieproto.pc libquvi-scripts.pc usbutils.pc xproto.pc
> fixesproto.pc randrproto.pc videoproto.pc xproxymngproto.pc
> fontsproto.pc recordproto.pc xcmiscproto.pc
> asterix:/home/balay>
>
>
> Satish
More information about the petsc-dev
mailing list