[PROTON-2233] Problem building c examples with qpid-proton 0.31.0

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-c-0.31.0
• Fix Version/s: proton-c-0.33.0
• Component/s: examples
• Assignee: Andrew Stitcher
• Reporter: Irina Boverman
• Created: 29/May/20 15:31
• Updated: 25/Nov/20 15:41
• Resolved: 08/Oct/20 01:45

Description

Fedora distributes proton examples and cmake files to build them.

0.31.0 update of qpid-proton fails to build c examples.

 
To reproduce:
 
sudo docker run -it fedora:latest bash

1. dnf update
2. dnf install make cmake gcc gcc-c++ libstdc++-devel rubygem-json wget procps-ng findutils python3-case python3-tornado net-tools nodejs-yargs nodejs-ws mocha
3. dnf --enablerepo=updates-testing -y --nogpgcheck --setopt tsflags= install nodejs-rhea python3-pyngus qpid-tests python2-qpid qpid-qmf-devel perl-qpid-messaging qpid-cpp-server qpid-cpp-client qpid-cpp-client-rdma qpid-qmf qpid-cpp-server-ha qpid-cpp-server-rdma qpid-cpp-server-linearstore python2-qpid-messaging python2-qpid-qmf qpid-cpp-client-devel qpid-tools qpid-cpp-client-docs qpid-dispatch-router qpid-dispatch-tools qpid-dispatch-docs python-qpid-proton python-qpid-proton python3-qpid-proton qpid-proton-cpp qpid-proton-cpp-devel qpid-proton-c-devel qpid-proton-c python-qpid-proton-docs qpid-proton-c-docs qpid-proton-cpp-docs rubygem-qpid_messaging-doc rubygem-qpid_messaging rubygem-qpid_proton rubygem-qpid_proton-doc
    # find /usr/share/proton -path 'proton/examples'
    # cd /usr/share/proton/examples/c
    # cmake .
   CMake Warning (dev) in CMakeLists.txt:
     No project() command is present.  The top-level CMakeLists.txt file must
     contain a literal, direct call to the project() command.  Add a line of
     code such as

    project(ProjectName)

  near the top of the file, but after cmake_minimum_required().

  CMake is pretending there is a "project(Project)" command on the first
  line.
This warning is for project developers.  Use -Wno-dev to suppress it.

– The C compiler identification is GNU 9.3.1
– The CXX compiler identification is GNU 9.3.1
– Check for working C compiler: /usr/bin/cc
– Check for working C compiler: /usr/bin/cc - works
– Detecting C compiler ABI info
– Detecting C compiler ABI info - done
– Detecting C compile features
– Detecting C compile features - done
– Check for working CXX compiler: /usr/bin/c++
– Check for working CXX compiler: /usr/bin/c++ - works
– Detecting CXX compiler ABI info
– Detecting CXX compiler ABI info - done
– Detecting CXX compile features
– Detecting CXX compile features - done
– Looking for pthread.h
– Looking for pthread.h - found
– Performing Test CMAKE_HAVE_LIBC_PTHREAD
– Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
– Looking for pthread_create in pthreads
– Looking for pthread_create in pthreads - not found
– Looking for pthread_create in pthread
– Looking for pthread_create in pthread - found
– Found Threads: TRUE  
– Found PythonInterp: /usr/bin/python3.7 (found version "3.7.7")
CMake Error at CMakeLists.txt:50 (pn_add_test):
  Unknown CMake command "pn_add_test".

– Configuring incomplete, errors occurred!
See also "/usr/share/proton/examples/c/CMakeFiles/CMakeOutput.log".
See also "/usr/share/proton/examples/c/CMakeFiles/CMakeError.log".

Issue Links

• is caused by: PROTON-2135 C, cpp, and fuzz tests do not set TEST_ENV on Linux
• relates to: PROTON-1995 [c] Instructions for installable tests appear to be incorrect