Installation/swak4Foam/Understanding Error Messages

From OpenFOAMWiki

1 Introduction

This page is dedicated to explaining how to understand the build error messages given during the build process of swak4Foam.

Note to those who are willing to help: Feel free to update and add to this page whenever you find a new error message.


2 How to check if it has installed with success

One simple way to check if the installation of swak4Foam went well, is to check the version by running:

funkySetFields

This ends with an error message, but below the usual OpenFOAM banner you will find the version of swak4Foam and the release date. If there is no swakVersion line, then the installation is older than 0.2.0 (the first version to have this banner). For example, look for banner similar to this one:

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
swakVersion: 0.2.4 (Release date: 2013-05-24)
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

On the other hand, if it only shows a message stating:

funkySetFields: command not found

then that means that it did not build as intended. If this is the case, then continue reading this page.


3 The Basics: How to look for errors

The instructions given on the pages here at Installation/swak4Foam, usually tell you run Allwmake like this:

./Allwmake > make.log 2>&1

This way you get all of the output (both normal and error messages) that the build process performs, all stored in the file "make.log". Therefore, you'll need to edit the file to check if there are any error messages, e.g. by running:

gedit make.log

The output can be a bit difficult to understand, but in swak4Foam's case, there are a few ways to figure out what went wrong, if anything at all:

  1. When everything goes well, you should get an output similar to this one (only happens after you run Allwmake 2 or 3 times):
    No 'swakConfiguration'. Python etc won't work
    Checking swak4Foam-version and generating file
    abort: no repository found in '/home/ofuser/OpenFOAM/ofuser-1.6-ext/swak4Foam' (.hg not found)!
    Swak version is 0.2.4
    Bison is version 2.5
    Flex is version 2.5.35 (Minor version: 35)
    OpenFOAM-version: Major 1 Minor 6 Patch 1.6-ext
    No change to swak4FoamParsers/foamVersion4swak.H
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswak4FoamParsers.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libgroovyBC.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakFunctionObjects.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libsimpleFunctionObjects.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libsimpleLagrangianFunctionObjects.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libsimpleSearchableSurfaces.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libsimpleSwakFunctionObjects.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakTopoSources.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakSourceFields.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakFiniteArea.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libgroovyStandardBCs.so' is up to date.
    SWAK_PYTHON_INCLUDE not defined .... no Python-Integration
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakMeshQualityFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakLocalCalculationsFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakRandomFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakFvcSchemesFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakThermoTurbFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakTransportTurbFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakSurfacesAndSetsFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakLagrangianCloudSourcesFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakVelocityFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakChemistryModelFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakRadiationModelFunctionPlugin.so' is up to date.
    '/home/ofuser/OpenFOAM/ofuser-1.6-ext/lib/linux64Gcc46DPOpt/libswakFacSchemesFunctionPlugin.so' is up to date.
    make[1]: `/home/ofuser/OpenFOAM/ofuser-1.6-ext/applications/bin/linux64Gcc46DPOpt/calcNonUniformOffsetsForMapped' is up to date.
    make[1]: `/home/ofuser/OpenFOAM/ofuser-1.6-ext/applications/bin/linux64Gcc46DPOpt/replayTransientBC' is up to date.
    make[1]: `/home/ofuser/OpenFOAM/ofuser-1.6-ext/applications/bin/linux64Gcc46DPOpt/funkyDoCalc' is up to date.
    make[1]: `/home/ofuser/OpenFOAM/ofuser-1.6-ext/applications/bin/linux64Gcc46DPOpt/funkySetBoundaryField' is up to date.
    make[1]: `/home/ofuser/OpenFOAM/ofuser-1.6-ext/applications/bin/linux64Gcc46DPOpt/funkySetFields' is up to date.
    make[1]: `/home/ofuser/OpenFOAM/ofuser-1.6-ext/applications/bin/linux64Gcc46DPOpt/funkySetAreaFields' is up to date.

    If you get something the output above, then everything is OK.

  2. If not, go to the end of the file. If there is an explicit message from swak4Foam's build process, it should indicate what you need to do. For example:
    Parser library did not compile OK. No sense continuing as everything else depends on it
    
    Requirements for Library not satisfied. I see no sense in going on
    Check the README before you go on to ask. And search: Most likely your problem occurred to 5
    other people before and has been solved on the Message Board
    

    TODO