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 ver
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
/
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
wrote:
> Ok.
>
> Let me know if I can do anything to help!
>
> On Wed, Feb 27, 2019 a
Ok.
Let me know if I can do anything to help!
On Wed, Feb 27, 2019 at 3:09 PM Ed Kern (ejk) 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 Vinciguerr
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
mailto:pvi...@vinciconsulting.com>> wrote:
Ed,
There is an issue. I am testing a fix.
See: https://gerrit.fd.i
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 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 s
just so you know…it does already echo the version id and os id in the console
log
16:47:00 + OS_VERSION_ID=15.0
16:47:00 + echo OS_ID: opensuse
16:47:00 OS_ID: opensuse
16:47:00 + echo OS_VERSION_ID: 15.0
16:47:00 OS_VERSION_ID: 15.0
16:47:00 + hostname
16:47:00 1f2fe1a3f253
16:47:00 + export CC
when i pull your change
i see a different makefile then what you pasted below….
ifeq ($(SUSE_ID),15.0)
RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
libboost_thread1_68_0-devel-1.68.0 gcc6
RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
else
RPM_SUSE_DEVEL_DEPS +
so that wil
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...@vincicon
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="o
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 th
11 matches
Mail list logo
