Pagmo2 2.19 cannot build

[montanaviking]

Hi,
I'm attempting to build Pagmo 2.19 on Ubuntu 22.04. I have NLOPT installed on my system but apparently after downloading the source, I am not able to build the code. I get an error that NLOPT was not found.
Here is my command line build:
##################
viking@hydra:/opt/pagmosource/pagmo2-2.19.0/build$ cmake ../ -DPAGMO_BUILD_TESTS=ON -DPAGMO_BUILD_TUTORIALS=ON -DPAGMO_WITH_EIGEN3=ON -DPAGMO_WITH_NLOPT=ON -DPAGMO_WITH_IPOPT=ON -DCMAKE_INSTALL_PREFIX=/opt/pagmo
-- System name: Linux
-- The fork_island UDI will be available.
-- The C++ compiler ID is: GNU
-- YACMA autodetected C++ flags: -fdiagnostics-color=auto;-ftemplate-depth=1024;-fdiagnostics-show-template-tree;-Wno-attributes
-- YACMA autodetected C++ debug flags: -Waddress-of-packed-member;-Wall;-Wextra;-Wnon-virtual-dtor;-Wlogical-op;-Wconversion;-Wdeprecated;-Wold-style-cast;-Wdisabled-optimization;-ftemplate-backtrace-limit=0;-fstack-protector-all;-Wodr;-Wsuggest-final-types;-Wsuggest-final-methods;-Wsuggest-override;-Wshift-negative-value;-Wshift-overflow=2;-Wduplicated-cond;-Wnull-dereference;-Wrestrict;-Waligned-new;-Wcast-align=strict;-Wno-maybe-uninitialized;-Wmismatched-tags;-Wredundant-tags
-- Thread library:
-- POSIX threads detected.
-- POSIX threads affinity extensions detected.
-- The 'thread_local' keyword is supported.
-- Library installation directory: lib
-- TBB found using config mode.
-- Requested IPOPT components: header;libipopt
-- Creating the 'pagmo::IPOPT::header' imported target.
-- Path to the ipopt headers: /usr/include/coin
-- Creating the 'pagmo::IPOPT::libipopt' imported target.
-- Path to libipopt: /usr/lib/libipopt.so
-- Required Boost libraries: serialization;unit_test_framework
-- Detected Boost version: 1.74.0
-- Boost include dirs: /usr/include
-- Configuring done
CMake Error at CMakeLists.txt:394 (target_link_libraries):
Target "pagmo" links to:

NLopt::nlopt

but the target was not found. Possible reasons include:

* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.

-- Generating done
CMake Generate step failed. Build files cannot be regenerated correctly.
########################################################################

oddly, Pagmo2 2.18 built correctly with NLOPT a few months ago on this same system.
Any ideas would be very welcome.
Thanks in advance,
Phil

[montanaviking]

Sorry, My bad. It turns out that I needed to be root to build. Thanks, Phil

[montanaviking]

Hi Again,
I'd tried to build Pagmo 2.19. This is a continuation of my above discussion.
When I tried to rebuild Pagmo 2.19 as root after cleaning out the built *.o files, because I wanted to build with MPI, https://esa.github.io/pagmo/mpi_support.html
using the ENABLE_MPI=ON option, I found that I could not get the build to work again, even as root, and it gave the above errors about not being able to find nlopt libraries. The reason I'd gotten it to finally build as root is that I also modified the
/pagmosource/build/CMakeCache.txt file where pagmosource is your location for your pagmo source files.
I had found that in my previous build for Pagmo 2.18 my CMakeCache.txt had lines:
//The directory containing a CMake configuration file for NLopt.
NLopt_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/nlopt

whereas the as-autobuilt file for my Pagmo 2.19 source had the corresponding CMakeCache.txt entry as:
//The directory containing a CMake configuration file for NLopt.
NLopt_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/nlopt_cxx
########################################
changing the NLopt_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/nlopt_cxx to NLopt_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/nlopt
in the Pagmo 2.19 CMakeCache.txt file and running the
$ sudo cmake ../ -DPAGMO_BUILD_TESTS=ON -DPAGMO_BUILD_TUTORIALS=ON -DPAGMO_WITH_EIGEN3=ON -DPAGMO_WITH_NLOPT=ON -DPAGMO_WITH_IPOPT=ON -DENABLE_MPI=ON -DCMAKE_INSTALL_PREFIX=/opt/pagmo
command with the above modification of Pagmo 2.19 CMakeCache.txt file
appeared to result in a successful build.
Therefore, I'm lead to believe this could be a bug or nuance of my Ubuntu 22.04 system?
Thanks and best,
Phil