when I saw that paul  that lead to a few searches (that for me) ended with

This is is not a real bug. The problem is that cmake check that it knows the 
version of boost that you are using and so every time that boost creates a new 
release, the cmake guys need to update the list of supported version. Since 
boost 1.66 was release after cmake 3.10, it is not in the list of supported 
boost versions. Everything should still work though, you just get these 
annoying warnings.

But again..if you find something else or that its actually serious I’m happy to 
listen since these warnings/error/messages are on all branches


Ed




On Feb 27, 2019, at 2:00 PM, Paul Vinciguerra 
<pvi...@vinciconsulting.com<mailto:pvi...@vinciconsulting.com>> wrote:

Great!

I'm not convinced that it's fully fixed.  See your log: 
https://jenkins.fd.io/job/vpp-verify-1901-osleap15/81/consoleFull
I interpret these logs as we do not have feature parity across the various 
distros at the moment.

Paul

15:21:06 -- Found Threads: TRUE
15:21:06 CMake Warning at /usr/share/cmake/Modules/FindBoost.cmake:801 
(message):
15:21:06   New Boost version may have incorrect or missing dependencies and 
imported
15:21:06   targets
15:21:06 Call Stack (most recent call first):
15:21:06   /usr/share/cmake/Modules/FindBoost.cmake:906 
(_Boost_COMPONENT_DEPENDENCIES)
15:21:06   /usr/share/cmake/Modules/FindBoost.cmake:1544 
(_Boost_MISSING_DEPENDENCIES)
15:21:06   CMakeLists.txt:27 (find_package)
15:21:06
15:21:06
15:21:06 CMake Warning at /usr/share/cmake/Modules/FindBoost.cmake:801 
(message):
15:21:06   New Boost version may have incorrect or missing dependencies and 
imported
15:21:06   targets
15:21:06 Call Stack (most recent call first):
15:21:06   /usr/share/cmake/Modules/FindBoost.cmake:906 
(_Boost_COMPONENT_DEPENDENCIES)
15:21:06   /usr/share/cmake/Modules/FindBoost.cmake:1544 
(_Boost_MISSING_DEPENDENCIES)
15:21:06   CMakeLists.txt:27 (find_package)
15:21:06
15:21:06
15:21:06 -- Could NOT find Boost
15:21:06 -- Configuring done
15:21:06 -- Generating done

On Wed, Feb 27, 2019 at 3:38 PM Ed Warnicke 
<hagb...@gmail.com<mailto:hagb...@gmail.com>> wrote:
Paul,

Looks like it was a ships in the night effect on a fix going into 
stable/1901... rebase *appears* to have fixed it:

https://gerrit.fd.io/r/#/c/17884/

Ed

On Wed, Feb 27, 2019 at 2:14 PM Paul Vinciguerra 
<pvi...@vinciconsulting.com<mailto:pvi...@vinciconsulting.com>> wrote:
Ok.

Let me know if I can do anything to help!

On Wed, Feb 27, 2019 at 3:09 PM Ed Kern (ejk) 
<e...@cisco.com<mailto:e...@cisco.com>> wrote:
thats a perfectly good and reasonable change and I support it..

But that’s not the problem that the other ed is having right now.

Ed



On Feb 27, 2019, at 12:47 PM, Paul Vinciguerra 
<pvi...@vinciconsulting.com<mailto:pvi...@vinciconsulting.com>> wrote:

Ed,

There is an issue.  I am testing a fix.
See: https://gerrit.fd.io/r/#/c/17917/

Paul

On Wed, Feb 27, 2019 at 2:23 PM Ed Warnicke 
<hagb...@gmail.com<mailto:hagb...@gmail.com>> wrote:
Paul,

Good first thing to check... I've pushed
https://gerrit.fd.io/r/#/c/17916/

to cause the opensuse jobs to cat the /etc/os-release as you suggested, and 
rechecked: https://gerrit.fd.io/r/#/c/17884/
to see what happens :)

Ed

On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra 
<pvi...@vinciconsulting.com<mailto:pvi...@vinciconsulting.com>> wrote:
Can we confirm that they are truly osleap15?

An osleap box reports correctly for me:
docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
ee4938c281e4:/ # cat /etc/os-release
NAME="openSUSE Leap"
VERSION="15.0 Beta"
ID="opensuse"
ID_LIKE="suse"
VERSION_ID="15.0"
PRETTY_NAME="openSUSE Leap 15.0 Beta"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.0"
BUG_REPORT_URL="https://bugs.opensuse.org<https://bugs.opensuse.org/>"
HOME_URL="https://www.opensuse.org/";

On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke 
<hagb...@gmail.com<mailto:hagb...@gmail.com>> wrote:
In cherry picking some fixes back to stable/1901, I've found that the builds 
for 1901 for OpenSuse Leap seem to be failing during install-deps:

https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console


10:50:21 No provider of 'libboost_thread1_68_0-devel-1.68.0' found.


Which looks like there is some upstream issue with a dependency no longer being 
available for libboost.

Digging deeper, it would appear that we are tripping on SUSE_NAME=Tumbleweed:

https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131

ifeq ($(OS_ID),opensuse)
ifeq ($(SUSE_NAME),Tumbleweed)
RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0  
libboost_thread1_68_0-devel-1.68.0 gcc
RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
endif
ifeq ($(SUSE_ID),15.0)
RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
else
RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
RPM_SUSE_PYTHON_DEPS += python-virtualenv
endif
endif

So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and being 
asked to install the wrong packages even though they are OSLEAP 15 boxes.  
Note: this same Makefile fragment is identical on master where the 
corresponding jobs are succeeding.

Do any of the OpenSuse folks have ideas as to what could be happening here?

Ed

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
Mute This Topic: https://lists.fd.io/mt/30154873/1594641
Group Owner: vpp-dev+ow...@lists.fd.io<mailto:vpp-dev%2bow...@lists.fd.io>
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[pvi...@vinciconsulting.com<mailto:pvi...@vinciconsulting.com>]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12371): https://lists.fd.io/g/vpp-dev/message/12371
Mute This Topic: https://lists.fd.io/mt/30154873/675649
Group Owner: vpp-dev+ow...@lists.fd.io<mailto:vpp-dev+ow...@lists.fd.io>
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[e...@cisco.com<mailto:e...@cisco.com>]
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12375): https://lists.fd.io/g/vpp-dev/message/12375
Mute This Topic: https://lists.fd.io/mt/30154873/675649
Group Owner: vpp-dev+ow...@lists.fd.io<mailto:vpp-dev+ow...@lists.fd.io>
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[e...@cisco.com<mailto:e...@cisco.com>]
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12377): https://lists.fd.io/g/vpp-dev/message/12377
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to