Re: configure warnings although all present.

[Daniel J Sebald]

On 06/30/2016 09:37 AM, Ernst Reissner wrote:
> Hi all,
> running configure, i obtain the following warnings:
>
> configure: WARNING: PortAudio library fails tests.  The audioplayer,
> audiorecorder classes, and audiodevinfo function for audio playback and
> recording will not be fully functional.
> configure: WARNING: Qt libraries not found; disabling Qt GUI
> configure: WARNING: AMD library not found.  This will result in some
> lack of functionality for sparse matrices.
> configure: WARNING: CAMD library not found.  This will result in some
> lack of functionality for sparse matrices.
> configure: WARNING: COLAMD library not found.  This will result in some
> lack of functionality for sparse matrices.
> configure: WARNING: CCOLAMD library not found.  This will result in some
> lack of functionality for sparse matrices.
> configure: WARNING: CHOLMOD library not found.  This will result in some
> lack of functionality for sparse matrices.
> configure: WARNING: CXSparse library not found.  This will result in
> some lack of functionality for sparse matrices.
> configure: WARNING: UMFPACK not found.  This will result in some lack of
> functionality for sparse matrices.
> configure:
> configure: NOTE: Libraries or auxiliary programs may be skipped if they are
> configure: NOTE: not found OR if they are missing required features on your
> configure: NOTE: system.
>
>
> although, all of it is present on my system.
> The problem seems, that it is not at the right place.
> How to solve this problem?
>
> Thank you in advance.

Ernst,

Sometimes if one looks at the config.log file they'll see more detailed 
information about what was tested and found or not found on the linux 
system.  For example, there are two different setups for Qt, basically 
pre-version-5 and version-5.  The way these are organized and included 
differ.  Also, sometimes you may have a software package installed, but 
not the development tools for that application which usually is in an 
additional package.

What you need to do is search config.log for a key executable or header 
file that is missing and then find where in your linux bundle's package 
manager that might be located.  It's not always the easiest thing to 
find those files (might be tucked away in some package with a seemingly 
unrelated name).

On top of that, documentation hasn't compiled well for some folks for 
years.  You may want to configure the documentation out of your build 
with the --disable-docs option.

Dan