On Tue, 1 Feb 2000, Shaun Cloherty wrote:
> I'm trying to install mpich-1.2.0 on a GNU/Debian (Alpha) 2.1 > Linux (2.2.12) box which mounts its filesystem via nfs. I > configured the source tree using; > > # ./configure --with-device=ch_p4 --with-arch=LINUX_ALPHA --with-mpe > -opt="-mcpu=ev4" --disable-f77 --disable-f90 -disable-devdebug > -prefix=/usr/local/mpich-1.2.0 > > which succeeds, but produces a couple of messages that concern me; You are disabling f77 and f90... hmmm, I thought they were required... I am actually using Debian 2.1 and 2.2 (frozen) compiling with gcc and pgrouf f77-90 and it works well (intel xeon cpus). Stefano > > : > : > Configuring p4 subsystem... > checking for gcc... cc > checking whether the C compiler (cc ) works... yes > checking whether the C compiler (cc ) is a cross-compiler... no > checking whether we are using GNU C... yes > checking whether cc accepts -g... yes > checking for mmap... yes > checking that shared, anonymous mmap works with -1 filedes... no! > checking that semget works... undetermined > *# Could not compile program > : > : > > Could not compile program!? Can anyone shed some light on this, > what is semget?? why might it be undetermined?? I'm running > kernel 2.2.12. > > Later in the configure process, I see; > > > : > : > Configuring the test suite... > Configuring with args -basecc=cc > -cc=/home/shaunc/mpich-1.2.0/bin/mpicc -nof77 -make=make > --no-print-directory -mpichpath=/home/shaunc/mpich-1.2.0/bin > -cflags=-DMPID_NO_FORTRAN -DMPID_NO_FORTRAN -DUSE_SOCKLEN_T > -DUSE_U_INT_FOR_XDR -DHAVE_MPICHCONF_H > Don't build the tests that need Fortran > *# Unrecognized configure option > configuring for "LINUX_ALPHA" target architecture > : > : > > Humm... unrecognized configure option..... > > As I said, the configure completes ok, so I ran 'make', then > 'make testing' (in the examples/test subdir). Here's where my > problem begins, the tests start ok, but seem to take forever, > printing; > > : > : > Making testing in directory pt2pt > ./runtests -small > **** Testing MPI Point-to-point routines **** > SC-Cluster-10 : Tue Feb 1 08:42:11 /etc/localtime 2000 > /home/shaunc/mpich-1.2.0/bin/mpicc -DMPID_NO_FORTRAN > -DMPID_NO_FORTRAN -DUSE_SOCKLEN_T -DUSE_U_INT_FOR_XDR > -DHAVE_MPICHCONF_H -DHAVE_STDLIB_H=1 -DUSE_STDARG=1 > -DHAVE_LONG_DOUBLE=1 -DHAVE_LONG_LONG_INT=1 -DHAVE_PROTOTYPES=1 > -DHAVE_SIGNAL_H=1 -DHAVE_SIGACTION=1 -c sendrecv.c > /home/shaunc/mpich-1.2.0/bin/mpicc -o sendrecv sendrecv.o > test.o > **** Testing MPI_Send and MPI_Recv **** > > The machine then sits there for many hours after which time I get bored and > hit Ctrl-C, 4 instances of > 'sendrecv' are listed in the output from 'top', only two of which seem to be > doing anything. > > This is a 166MHz machine, so its not a rocket, but I would still expect the > test suite to complete within a few hours, or at least progress past the > first test. Any ideas anyone?? > > Any suggestions greatly appreciated, > > Shaun > > PS: yep, the filesystem is mounted 'noac'. > > -- > Shaun Cloherty > Graduate School of Biomedical Engineering > University of New South Wales > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
