Discussion:
[suggest] meep-mpi, h5utils
kmedri
2010-01-30 05:29:07 UTC
Permalink
On CentOS 5.3 I would like to "yum install meep-mpi h5utils"

http://www.centos.org/

http://ab-initio.mit.edu/wiki/index.php/Meep

http://ab-initio.mit.edu/wiki/index.php/H5utils

I currently use:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstaller

to which I could add say

rpm -Uvh
http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm

What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?

Thanks!

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Yury V. Zaytsev
2010-01-31 18:05:07 UTC
Permalink
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-04 16:56:22 UTC
Permalink
I noticed they discuss:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to

For reference:
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE

Using:
http://www.doe.carleton.ca/~kmedri/research/meep.spec

I was able to build:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m

I will continue working on this and appreciate input from anyone who can
help.

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: January 31, 2010 1:05 PM
To: kmedri at doe.carleton.ca
Cc: suggest at lists.rpmforge.net
Subject: Re: [suggest] meep-mpi, h5utils
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
Yury V. Zaytsev
2010-02-05 09:57:02 UTC
Permalink
Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-05 17:43:38 UTC
Permalink
How about:

http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE

the reason I was making my own meep.spec was I didn't have the above yet and
wanted to get testing. I noticed my build machine is a bit broken so I will
possibly have to reinstall it next week since I was having trouble
configuring --with-mpi (very important for me, and realistically the only
way to create a useable simulation environment) while someone else tried it
for me and did not have trouble. They are looking into why my yum -y
reinstall mpich2.x86_64 mpich2-devel.x86_64 does not function correctly.

If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well? Or is there
some way of using the above and setting it to configure --with-mpi?

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: February 5, 2010 4:57 AM
To: Kristian Medri
Cc: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Yury V. Zaytsev
2010-02-05 18:25:01 UTC
Permalink
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)

Normally you should be able to change

%configure F77=gfortran --enable-shared

to

%configure F77=gfortran --enable-shared --with-mpi

add corresponding build requirements

BuildRequires: mpich2 mpich2-devel

and it should work.
--
Sincerely yours,
Yury V. Zaytsev
kmedri
2010-02-08 05:07:37 UTC
Permalink
Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_64.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rpm

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rpm
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Kristian Medri
2010-02-18 23:13:21 UTC
Permalink
As I've posted here:

http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083

I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Yury V. Zaytsev
2010-02-19 08:21:22 UTC
Permalink
Hi!

Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
kmedri
2010-02-19 15:21:35 UTC
Permalink
This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Kristian Medri
2010-02-20 01:08:32 UTC
Permalink
Running both the holey waveguide cavity and 1D Fabry-Perot examples on our
cluster has shown that though certain functions run more quickly the overall
execution time is slower for these test cases. When I come across a more
suitable example I will post it.

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 19, 2010 10:22 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
Post by Yury V. Zaytsev
Post by Kristian Medri
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
/var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
Post by Yury V. Zaytsev
Post by Kristian Medri
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Kristian Medri
2010-02-20 01:08:32 UTC
Permalink
Running both the holey waveguide cavity and 1D Fabry-Perot examples on our
cluster has shown that though certain functions run more quickly the overall
execution time is slower for these test cases. When I come across a more
suitable example I will post it.

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 19, 2010 10:22 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
Post by Yury V. Zaytsev
Post by Kristian Medri
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
/var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
Post by Yury V. Zaytsev
Post by Kristian Medri
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Kristian Medri
2010-02-20 01:08:32 UTC
Permalink
Running both the holey waveguide cavity and 1D Fabry-Perot examples on our
cluster has shown that though certain functions run more quickly the overall
execution time is slower for these test cases. When I come across a more
suitable example I will post it.

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 19, 2010 10:22 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
Post by Yury V. Zaytsev
Post by Kristian Medri
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
/var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
Post by Yury V. Zaytsev
Post by Kristian Medri
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Kristian Medri
2010-02-20 01:08:32 UTC
Permalink
Running both the holey waveguide cavity and 1D Fabry-Perot examples on our
cluster has shown that though certain functions run more quickly the overall
execution time is slower for these test cases. When I come across a more
suitable example I will post it.

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 19, 2010 10:22 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
Post by Yury V. Zaytsev
Post by Kristian Medri
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
/var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
Post by Yury V. Zaytsev
Post by Kristian Medri
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Kristian Medri
2010-02-20 01:08:32 UTC
Permalink
Running both the holey waveguide cavity and 1D Fabry-Perot examples on our
cluster has shown that though certain functions run more quickly the overall
execution time is slower for these test cases. When I come across a more
suitable example I will post it.

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 19, 2010 10:22 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
Post by Yury V. Zaytsev
Post by Kristian Medri
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
Post by Yury V. Zaytsev
Post by Kristian Medri
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
/var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
Post by Yury V. Zaytsev
Post by Kristian Medri
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
Post by Yury V. Zaytsev
Post by Kristian Medri
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

kmedri
2010-02-19 15:21:35 UTC
Permalink
This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
kmedri
2010-02-19 15:21:35 UTC
Permalink
This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
kmedri
2010-02-19 15:21:35 UTC
Permalink
This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
kmedri
2010-02-19 15:21:35 UTC
Permalink
This is what I do right now and it works with MPI to make use of
multiple cores on a single machine:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstall.html

Regarding multiple machines, I will test some more once the install on
the machines in our cluster has been homologated.
Post by Yury V. Zaytsev
Hi!
Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Yury V. Zaytsev
2010-02-19 08:21:22 UTC
Permalink
Hi!

Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
Yury V. Zaytsev
2010-02-19 08:21:22 UTC
Permalink
Hi!

Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
Yury V. Zaytsev
2010-02-19 08:21:22 UTC
Permalink
Hi!

Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
Yury V. Zaytsev
2010-02-19 08:21:22 UTC
Permalink
Hi!

Did you find a way of building it with MPI yet? To me this is what seems
to be a major issue. I will try to look into HDF5 ASAP since I might
need it for a project of mine anyway.
--
Sincerely yours,
Yury V. Zaytsev
Post by Kristian Medri
http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083
I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).
-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to
configure
Post by Yury V. Zaytsev
Post by Kristian Medri
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
Kristian Medri
2010-02-18 23:13:21 UTC
Permalink
As I've posted here:

http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083

I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Kristian Medri
2010-02-18 23:13:21 UTC
Permalink
As I've posted here:

http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083

I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Kristian Medri
2010-02-18 23:13:21 UTC
Permalink
As I've posted here:

http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083

I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Kristian Medri
2010-02-18 23:13:21 UTC
Permalink
As I've posted here:

http://thread.gmane.org/gmane.comp.science.electromagnetism.meep.general/307
7/focus=3083

I am curious as to what kind of run times other people can achieve (code,
commands, and execution times available in that thread).

-----Original Message-----
From: suggest-bounces at lists.rpmforge.net
[mailto:suggest-bounces at lists.rpmforge.net] On Behalf Of
kmedri at doe.carleton.ca
Sent: February 8, 2010 12:08 AM
To: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_6
4.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_6
4.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rp
m

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
kmedri
2010-02-08 05:07:37 UTC
Permalink
Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_64.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rpm

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rpm
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
kmedri
2010-02-08 05:07:37 UTC
Permalink
Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_64.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rpm

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rpm
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
kmedri
2010-02-08 05:07:37 UTC
Permalink
Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_64.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rpm

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rpm
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
kmedri
2010-02-08 05:07:37 UTC
Permalink
Progress:

Used:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/h5utils-1.12.1-2.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/h5utils-debuginfo-1.12.1-2.x86_64.rpm

Used:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/harminv.spec

To build:
http://www.doe.carleton.ca/~kmedri/research/harminv-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-debuginfo-1.3.1-16.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/harminv-devel-1.3.1-16.x86_64.rpm

Tried:
http://www.doe.carleton.ca/~kmedri/research/libctl-3.1.tar.gz
http://www.doe.carleton.ca/~kmedri/research/libctl.spec
but need to consider the following instead of the newest rpms available?
http://www.doe.carleton.ca/~kmedri/research/libtool-2.2.6a.tar.gz
weird since when not using the spec I do not recall running into this
problem when installing it from source. It is a optional front end
(though used by many including the authors of meep), thus could
continue by removing it from BuildRequires:

Tried:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3.tar.gz
http://www.doe.carleton.ca/~kmedri/research/meep.spec.fromSuSE as meep.spec
but File not found by glob: /var/tmp/meep-1.0.3-2-root-root/usr/lib64/*.so.*
I will try to obtain a newer spec file from a SuSE SRPM and see if
this persist since using
http://www.doe.carleton.ca/~kmedri/research/meep.spec.old as meep.spec
Builds:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rpm
Post by Yury V. Zaytsev
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)
Normally you should be able to change
%configure F77=gfortran --enable-shared
to
%configure F77=gfortran --enable-shared --with-mpi
add corresponding build requirements
BuildRequires: mpich2 mpich2-devel
and it should work.
--
Sincerely yours,
Yury V. Zaytsev
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Yury V. Zaytsev
2010-02-05 18:25:01 UTC
Permalink
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)

Normally you should be able to change

%configure F77=gfortran --enable-shared

to

%configure F77=gfortran --enable-shared --with-mpi

add corresponding build requirements

BuildRequires: mpich2 mpich2-devel

and it should work.
--
Sincerely yours,
Yury V. Zaytsev
Yury V. Zaytsev
2010-02-05 18:25:01 UTC
Permalink
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)

Normally you should be able to change

%configure F77=gfortran --enable-shared

to

%configure F77=gfortran --enable-shared --with-mpi

add corresponding build requirements

BuildRequires: mpich2 mpich2-devel

and it should work.
--
Sincerely yours,
Yury V. Zaytsev
Yury V. Zaytsev
2010-02-05 18:25:01 UTC
Permalink
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)

Normally you should be able to change

%configure F77=gfortran --enable-shared

to

%configure F77=gfortran --enable-shared --with-mpi

add corresponding build requirements

BuildRequires: mpich2 mpich2-devel

and it should work.
--
Sincerely yours,
Yury V. Zaytsev
Yury V. Zaytsev
2010-02-05 18:25:01 UTC
Permalink
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
Hmmm... this SPEC looks more or less good to me, can be adopted with
minor changes if no dependency issues arise.
Post by Kristian Medri
If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well?
Authority is normally the person who manages the committed SPECs withing
the RPMForge repo. In this case it will be me ("yury").
Post by Kristian Medri
Or is there some way of using the above and setting it to configure --with-mpi?
(I have never ever used/built anything requiring MPI before.)

Normally you should be able to change

%configure F77=gfortran --enable-shared

to

%configure F77=gfortran --enable-shared --with-mpi

add corresponding build requirements

BuildRequires: mpich2 mpich2-devel

and it should work.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-05 17:43:38 UTC
Permalink
How about:

http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE

the reason I was making my own meep.spec was I didn't have the above yet and
wanted to get testing. I noticed my build machine is a bit broken so I will
possibly have to reinstall it next week since I was having trouble
configuring --with-mpi (very important for me, and realistically the only
way to create a useable simulation environment) while someone else tried it
for me and did not have trouble. They are looking into why my yum -y
reinstall mpich2.x86_64 mpich2-devel.x86_64 does not function correctly.

If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well? Or is there
some way of using the above and setting it to configure --with-mpi?

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: February 5, 2010 4:57 AM
To: Kristian Medri
Cc: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-05 17:43:38 UTC
Permalink
How about:

http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE

the reason I was making my own meep.spec was I didn't have the above yet and
wanted to get testing. I noticed my build machine is a bit broken so I will
possibly have to reinstall it next week since I was having trouble
configuring --with-mpi (very important for me, and realistically the only
way to create a useable simulation environment) while someone else tried it
for me and did not have trouble. They are looking into why my yum -y
reinstall mpich2.x86_64 mpich2-devel.x86_64 does not function correctly.

If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well? Or is there
some way of using the above and setting it to configure --with-mpi?

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: February 5, 2010 4:57 AM
To: Kristian Medri
Cc: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-05 17:43:38 UTC
Permalink
How about:

http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE

the reason I was making my own meep.spec was I didn't have the above yet and
wanted to get testing. I noticed my build machine is a bit broken so I will
possibly have to reinstall it next week since I was having trouble
configuring --with-mpi (very important for me, and realistically the only
way to create a useable simulation environment) while someone else tried it
for me and did not have trouble. They are looking into why my yum -y
reinstall mpich2.x86_64 mpich2-devel.x86_64 does not function correctly.

If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well? Or is there
some way of using the above and setting it to configure --with-mpi?

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: February 5, 2010 4:57 AM
To: Kristian Medri
Cc: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-05 17:43:38 UTC
Permalink
How about:

http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE

the reason I was making my own meep.spec was I didn't have the above yet and
wanted to get testing. I noticed my build machine is a bit broken so I will
possibly have to reinstall it next week since I was having trouble
configuring --with-mpi (very important for me, and realistically the only
way to create a useable simulation environment) while someone else tried it
for me and did not have trouble. They are looking into why my yum -y
reinstall mpich2.x86_64 mpich2-devel.x86_64 does not function correctly.

If I am to continue making my own specific meep.spec in order to configure
--with-mpi, is it okay to set Authority: dag on mine as well? Or is there
some way of using the above and setting it to configure --with-mpi?

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: February 5, 2010 4:57 AM
To: Kristian Medri
Cc: suggest at lists.rpmforge.net
Subject: RE: [suggest] meep-mpi, h5utils

Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Yury V. Zaytsev
2010-02-05 09:57:02 UTC
Permalink
Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Yury V. Zaytsev
2010-02-05 09:57:02 UTC
Permalink
Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Yury V. Zaytsev
2010-02-05 09:57:02 UTC
Permalink
Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Yury V. Zaytsev
2010-02-05 09:57:02 UTC
Permalink
Hi!
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE
These look good to me.
Post by Kristian Medri
http://www.doe.carleton.ca/~kmedri/research/meep.spec
This one is a little bit sloppy. See template we use for pointers:

http://svn.rpmforge.net/svn/trunk/rpms/_template.spec
Post by Kristian Medri
I will continue working on this and appreciate input from anyone who can
help.
Well, I'll try to find some time during the coming week to review and
commit the prerequisites, so that we can see if Dag is able to build
this with our build system.

When that's done just let me know when meep will be ready for review.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-04 16:56:22 UTC
Permalink
I noticed they discuss:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to

For reference:
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE

Using:
http://www.doe.carleton.ca/~kmedri/research/meep.spec

I was able to build:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m

I will continue working on this and appreciate input from anyone who can
help.

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: January 31, 2010 1:05 PM
To: kmedri at doe.carleton.ca
Cc: suggest at lists.rpmforge.net
Subject: Re: [suggest] meep-mpi, h5utils
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-04 16:56:22 UTC
Permalink
I noticed they discuss:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to

For reference:
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE

Using:
http://www.doe.carleton.ca/~kmedri/research/meep.spec

I was able to build:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m

I will continue working on this and appreciate input from anyone who can
help.

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: January 31, 2010 1:05 PM
To: kmedri at doe.carleton.ca
Cc: suggest at lists.rpmforge.net
Subject: Re: [suggest] meep-mpi, h5utils
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-04 16:56:22 UTC
Permalink
I noticed they discuss:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to

For reference:
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE

Using:
http://www.doe.carleton.ca/~kmedri/research/meep.spec

I was able to build:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m

I will continue working on this and appreciate input from anyone who can
help.

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: January 31, 2010 1:05 PM
To: kmedri at doe.carleton.ca
Cc: suggest at lists.rpmforge.net
Subject: Re: [suggest] meep-mpi, h5utils
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
Kristian Medri
2010-02-04 16:56:22 UTC
Permalink
I noticed they discuss:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to

For reference:
http://www.doe.carleton.ca/~kmedri/research/harminv.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/libctl.spec.Fedora
http://www.doe.carleton.ca/~kmedri/research/meep.spec.SuSE
http://www.doe.carleton.ca/~kmedri/research/h5utils.spec.SuSE

Using:
http://www.doe.carleton.ca/~kmedri/research/meep.spec

I was able to build:
http://www.doe.carleton.ca/~kmedri/research/meep-1.0.3-1.x86_64.rpm
http://www.doe.carleton.ca/~kmedri/research/meep-debuginfo-1.0.3-1.x86_64.rp
m

I will continue working on this and appreciate input from anyone who can
help.

-----Original Message-----
From: Yury V. Zaytsev [mailto:yury at shurup.com]
Sent: January 31, 2010 1:05 PM
To: kmedri at doe.carleton.ca
Cc: suggest at lists.rpmforge.net
Subject: Re: [suggest] meep-mpi, h5utils
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
kmedri
2010-01-30 05:29:07 UTC
Permalink
On CentOS 5.3 I would like to "yum install meep-mpi h5utils"

http://www.centos.org/

http://ab-initio.mit.edu/wiki/index.php/Meep

http://ab-initio.mit.edu/wiki/index.php/H5utils

I currently use:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstaller

to which I could add say

rpm -Uvh
http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm

What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?

Thanks!

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Yury V. Zaytsev
2010-01-31 18:05:07 UTC
Permalink
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
kmedri
2010-01-30 05:29:07 UTC
Permalink
On CentOS 5.3 I would like to "yum install meep-mpi h5utils"

http://www.centos.org/

http://ab-initio.mit.edu/wiki/index.php/Meep

http://ab-initio.mit.edu/wiki/index.php/H5utils

I currently use:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstaller

to which I could add say

rpm -Uvh
http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm

What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?

Thanks!

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Yury V. Zaytsev
2010-01-31 18:05:07 UTC
Permalink
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
kmedri
2010-01-30 05:29:07 UTC
Permalink
On CentOS 5.3 I would like to "yum install meep-mpi h5utils"

http://www.centos.org/

http://ab-initio.mit.edu/wiki/index.php/Meep

http://ab-initio.mit.edu/wiki/index.php/H5utils

I currently use:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstaller

to which I could add say

rpm -Uvh
http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm

What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?

Thanks!

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Yury V. Zaytsev
2010-01-31 18:05:07 UTC
Permalink
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
kmedri
2010-01-30 05:29:07 UTC
Permalink
On CentOS 5.3 I would like to "yum install meep-mpi h5utils"

http://www.centos.org/

http://ab-initio.mit.edu/wiki/index.php/Meep

http://ab-initio.mit.edu/wiki/index.php/H5utils

I currently use:

http://www.doe.carleton.ca/~kmedri/research/centosmeepinstaller

to which I could add say

rpm -Uvh
http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm

What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?

Thanks!

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Yury V. Zaytsev
2010-01-31 18:05:07 UTC
Permalink
Post by kmedri
What is the turn around for a request such as this and what can I do
to help speed up the progress in order to get "yum install meep-mpi
h5utils" to work?
Someone has to package all this stuff.

* harminv and libctl are available in Fedora
* h5utils and meep are packaged for SuSE

The first two should be trivial to port unless they require something
else that is not in CentOS / RPMForge. The latter two are trickier,
because SuSE packaging guidelines are quite different from EL.

I might have time to review/commit the SPECs if someone comes up with
something, but otherwise I personally have no spare time / interest in
packaging and maintaining these utilities.

Maybe someone else have time to have fun with this.
--
Sincerely yours,
Yury V. Zaytsev
Loading...