On 2018-05-06, Ken M <k...@mack-z.com> wrote:
> Maybe this should go to ports@ but not sure I am near there yet.

ports@ is a much better place for this type of question.

> So I am trying to compile the latest ardour on 6.3, got through compiling
> rubberband and aubio and now well I am stuck here:
>
> [200~./waf configure --boost-include=/usr/local/include
> Setting top to                           : /home/superfly/git/ardour 
> Setting out to                           : /home/superfly/git/ardour/build 
> Checking for 'gcc' (c compiler)          : /usr/bin/gcc 
> Checking for 'g++' (c++ compiler)        : /usr/bin/g++ 

This should be using cc/c++ rather than gcc/g++

> Global Configuration 
>  * Install prefix                                    : /usr/local 
>   * Debuggable build                                  : True 
>    * Build documentation                               : False 
>
>    Ardour Configuration 
>     * Will build against private GTK dependency stack   : no 
>        * Will rely on libintl built into libc              : yes 
>         * Will build against private Ardour dependency stack : no 
>         Checking for boost library >= 1.39                   : ok 
>         Checking for program pkg-config                      : 
> /usr/bin/pkg-config 
>         Checking for 'glib-2.0' >= 2.28                      : yes 
>         Checking for 'gthread-2.0' >= 2.2                    : yes 
>         Checking for 'glibmm-2.4' >= 2.32.0                  : yes 
>         Checking for 'sndfile' >= 1.0.18                     : yes 
>         Checking for 'giomm-2.4' >= 2.2                      : yes 
>         Checking for 'libcurl' >= 7.0.0                      : yes 
>         Checking for 'libarchive' >= 3.0.0                   : yes 
>         Checking for 'liblo' >= 0.26                         : yes 
>         Checking for 'taglib' >= 1.6                         : yes 
>         Checking for 'vamp-sdk' >= 2.1                       : yes 
>         Checking for 'vamp-hostsdk' >= 2.1                   : yes 
>         Checking for 'rubberband'                            : yes 
>         Checking for  sndfile RF64=>RIFF support             : Found 
>         Checking for clang                                   : no 
>
>         Warning: you are building Ardour with SSE support even though your 
> system
>         does not support these instructions. (This may not be an error, 
> especially
>         if you are a package maintainer)
>         hidapi is not yet available for the given system
>         Checking for 'fftw3f'                                : yes 
>         Checking for 'aubio' >= 0.3.2                        : yes 
>         Checking for 'aubio' >= 0.4.0                        : yes 
>         Checking for 'libxml-2.0'                            : yes 
>         Checking for 'sigc++-2.0' >= 2.0                     : yes 
>         Checking for function getmntent                      : not found 
>         Checking for header execinfo.h                       : not found 
>         Checking for header unistd.h                         : not found 
>         Checking for function posix_memalign                 : no 

That's weird because we do have posix_memalign

>         Checking for function localtime_r                    : not found 
>         Checking for header boost/shared_ptr.hpp             : not found 
>         The configuration failed
>         (complete log in /home/superfly/git/ardour/build/config.log)
>
> Tail form the config.log
>
> [2/2] cxxprogram: 
> build/.conf_check_c02c9165785b1b8132b54a498262d87b/testbuild/test.cpp.1.o -> 
> build/.conf_check_c02c9165785b1b8132b54a498262d87b/testbuild/testprog
>
> ['/usr/bin/g++', '-lexecinfo', 'test.cpp.1.o', '-o', 
> '/home/superfly/git/ardour/build/.conf_check_c02c9165785b1b8132b54a498262d87b/testbuild/testprog',
>  '-Wl,-Bstatic', '-Wl,-Bdynamic']
> err: /usr/bin/ld: cannot find -lexecinfo
> collect2: ld returned 1 exit status

The reason it's failing is because it doesn't specify -L/usr/local/lib,
however in the case of libexecinfo the best option here is to figure out
how to disable it from being picked up at all.


Reply via email to