Aleksej
Cc: to the OpenMPI list as the oftdump clash might be of interest
elsewhere.
> I attach a patch, but it doesn't work and I don't see where the
> error lies now. It may be that I'm doing something stupid.
> It produces working OpenMPI-1.3.4 package on Dragonfly though.
Ok, I'll try and merge it in to the working stuff we have here.
I, obviously, just #ifdef'd for NetBSD as that is all I have to
try stuff out against.
> Kevin, I've tried your chunk but it doesn't make any better.
> Do you really have working OpenMPI on NetBSD?
Oh yes!
This was the output from a slightly modified hello_c.c that I ran
against my non-PkgSrc build a couple of days ago
% cat my_mpirun_job.sh.o419867
Hello world, I am 0 of 8 on old-bailey.ecs.vuw.ac.nz
Hello world, I am 2 of 8 on pulcinella.ecs.vuw.ac.nz
Hello world, I am 4 of 8 on citron.ecs.vuw.ac.nz
Hello world, I am 1 of 8 on petit-lyon.ecs.vuw.ac.nz
Hello world, I am 6 of 8 on kipp-cafe.ecs.vuw.ac.nz
Hello world, I am 3 of 8 on stellar.ecs.vuw.ac.nz
Hello world, I am 7 of 8 on matterhorn.ecs.vuw.ac.nz
Hello world, I am 5 of 8 on khmer.ecs.vuw.ac.nz
Note the EIGHT different hosts there - so it is working on NetBSD !
I am currently installing the PkgSrc build, having prevented the
install binary clash, and will post the results of that soon.
I have placed the tar of current patches from our PkgSrc build in
http://www.ecs.vuw.ac.nz/~kevin/forMPI/openmpi-1.3.4-20091208-netbsd.tar.gz
in case you want to try something out from an actual NetBSD build.
How does your installtion fail ?
>
> (What conflict do you observe with pkgsrc-wip package by the way?)
>
That was detailed in another email but basically the Open Trace Format
that the Vampire Trace (VT) stuff is looking to install tries to install:
${LOCALBASE}/bin/otfdump
and that binary is already installed there as part of another
package.
You can get around this for a NetBSD OpenMPI deployment by adding this
patch to the PkgSrc Makefile which just removes the VT toolkit:
26a27
> CONFIGURE_ARGS+= --enable-contrib-no-build=vt
I have no idea how NetBSD go about resolving such clashes in the long
term though?
I repeat the info from my previous email:
# pkg_info -F /usr/pkg/bin/otfdump
Information for libotf-0.9.9:
Comment:
Library for handling OpenType fonts (OTF)
Requires:
Xaw3d>=1.5Enb1
freetype2>=2.1.10nb1
Required by:
m17n-lib-1.5.4nb1
emacs-23.1nb2
Description:
The library "libotf" provides the following facilites.
o Read Open Type Layout Tables from OTF file. Currently these
tables are supported; head, name, cmap, GDEF, GSUB, and GPOS.
o Convert a Unicode character sequence to a glyph code sequence by
using the above tables.
The combination of libotf and the FreeType library (Ver.2) realizes
CTL (complex text layout) by OpenType fonts.
Homepage:
http://www.m17n.org/libotf/
--
Kevin M. Buckley Room: CO327
School of Engineering and Phone: +64 4 463 5971
Computer Science
Victoria University of Wellington
New Zealand
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}