whizard is hosted by Hepforge, IPPP Durham
close Warning: Error with navigation contributor "BrowserModule"

Changes between Version 4 and Version 5 of BuildProblems


Ignore:
Timestamp:
Apr 13, 2010, 2:02:24 PM (14 years ago)
Author:
ohl
Comment:

Compilation problems $builddir=$srcdir

Legend:

Unmodified
Added
Removed
Modified
  • BuildProblems

    v4 v5  
    22
    33Here's a list of not so common problems that you might encounter when building WHIZARD that didn't make it into the [source:/trunk/INSTALL INSTALL file].
     4
     5=== Compiling in the Source Directory ===
     6If you don't take advantage of the possibility to keep your WHIZARD sources pristine by compiling in a different directory, you may encounter the following error:
     7{{{
     8...
     9libtool: compile:  gfortran45 -I../misc -I../vamp -g -O2 -c processes.f90  -fPIC -o .libs/processes.o
     10libtool: compile:  gfortran45 -I../misc -I../vamp -g -O2 -c processes.f90 -o processes.o >/dev/null 2>&1
     11make[2]: *** No rule to make target `limits.lo', needed by `decays.lo'.  Stop.
     12...
     13make: *** [all-recursive] Error 1
     14}}}
     15In this case, please unpack a fresh copy of WHIZARD and configure it in a separate directory (not necessarily a subdirectory).  Then the compilation will go through
     16{{{
     17$ zcat whizard-2.0.0.tar.gz | tar xf -
     18$ cd whizard-2.0.0
     19$ mkdir _build
     20$ cd _build
     21$ ../configure FC=gfortran-4.5
     22$ make
     23}}}
     24(The developers use this setup to be able to test different compilers.  Therefore building in the same directory is not as thoroughly tested.)
    425
    526=== Compiler and Shared Library search PATHs ===