Problems building sowing


Up: Problems Next: General Previous: General



Up: Problems Next: General Previous: General


General


Up: Problems building sowing Next: SGI Previous: Problems building sowing

    1. Q: When running make on sowing, I get this error:
    ar: write error: No such file or directory 
    *** Error code 1 
    
    I've looked, and all the files are accessible and have the proper permissions.

    A: Check the amount of space in /tmp. This error is sometimes generated when there is insufficient space in /tmp to copy the archive (this is a step that ar takes when updating a library). The command df /tmp will show you how much space is available. Try to insure that at least twice the size of the library is available.


    2. Q: When running make on sowing, I get errors when executing ranlib.

    A: Many systems implement ranlib with the ar command, and they use the /tmp directory by default because it ``seems'' obvious that using /tmp would be faster (/tmp is often a local disk). Unfortunately, a large number of systems have ridiculously small /tmp partitions, and making any use of /tmp is very risky. In some cases, the ar commands used by SOWING will succeed because they use the l option---this forces ar to use the local directory instead of /tmp. The ranlib command, on the other hand, may use /tmp and cannot be fixed.

    In some cases, you will find that the ranlib command is unnecessary. In these cases, you can reconfigure with -noranlib. If you must use ranlib, either reduce the space used in /tmp or increase the size of the /tmp partition (your system administrator will need to do this). There should be at least 20--30 MBytes free in /tmp.


    3. Q: When doing the link test, the link fails and does not seem to find any of the sowing system routines:

      /homes/them/burgess/sowing/lib/IRIX32/ch_p4/mpicc \ 
                                             -o overtake overtake.o test.o  
      ld: WARNING 126: The archive \ 
         /homes/them/burgess/sowing/lib/IRIX32/ch_p4/libmpi.a \ 
                                       defines no global symbols. Ignoring. 
      ld: WARNING 84: /usr/lib/libsun.a is not used for resolving any symbol. 
    ld: ERROR 33: Unresolved data symbol "MPI_COMM_WORLD" -- \ 
                                              1st referenced by overtake.o. 
    ld: ERROR 33: Unresolved text symbol "MPI_Send" -- \ 
                                              1st referenced by overtake.o. 
    ... 
    
    A: Check that the ar and ranlib programs are compatible. One site installed the Gnu ranlib in such a way that it would be used with the vendors ar program, with which it was incompatible. Use the -noranlib option to configure if this is the case.



Up: Problems building sowing Next: SGI Previous: Problems building sowing


SGI


Up: Problems building sowing Next: DEC ULTRIX Previous: General

    1. Q: The build on an SGI Power Challenge fails with
    Signal: SIGSEGV in Back End Driver phase. 
    > ### Error: 
    > ### Signal SIGSEGV in phase Back End Driver -- processing aborted 
    > f77 ERROR:  /usr/lib64/cmplrs/be died due to signal 4 
    > f77 ERROR:  core dumped 
    > *** Error code 2 (bu21) 
    > *** Error code 1 (bu21) 
    > *** Error code 1 (bu21) 
    
    A: Our information is that setting the environment variable SGI_CC to -ansi will fix this problem.



Up: Problems building sowing Next: DEC ULTRIX Previous: General


DEC ULTRIX


Up: Problems building sowing Next: Acknowledgments Previous: SGI

    1. Q: When trying to build, the make aborts early during the cleaning phase:
    amon:SOWING/sowing>make clean 
            /bin/rm -f *.o *  nupshot 
    *** Error code 1 
    
    A: This is a bug in the shell support on some DEC ULTRIX systems. You may be able to work around this with


    setenv PROG_ENV SYSTEM_FIVE 
    
    Configuring with -make=s5make may also work.



Up: Problems building sowing Next: Acknowledgments Previous: SGI