Ubuntu 18.04 LTS support

[francovz96]

Setting up Warp17 according to the instructions on the Warp17 Git on an Ubuntu 18.04 LTS system, I ran into problems building Warp17 with the protobuf compilers given in the guide. Is there an updated guide for Ubuntu 18.04, or when will there be support for Ubuntu 18.04 ?

[davvore33]

Hi @francovz96 ,
can you please paste protoc --version and protoc-c --version?

[francovz96]

Hi @davvore33 thanks for the reply,

~# protoc --version
libprotoc 3.0.0

~# protoc-c --version
protobuf-c 1.2.1
libprotoc 3.0.0

[davvore33]

ok @francovz96 so here the problem is that we don't support protobuf 3 yet, what you can do is uninstall the 3.0 packets like this
sudo apt remove libprotobuf-c0 libprotobuf-c0-dev libprotobuf8 libprotoc8 protobuf-c-compiler
and follow the README under the Otherwise (Ubuntu version >= 15.10) title.

let me know if this solves the problem

[francovz96]

Hi @davvore33, I did do the install according to the Ubuntu version >= 15.10 and I get the following result when trying to make.

~/warp17-1.8# make make[1]: Entering directory '/root/warp17-1.8/api' google/protobuf/descriptor.proto:388:3: Expected "required", "optional", or "repeated". google/protobuf/descriptor.proto:388:12: Expected field name. Makefile.api:101: recipe for target 'generated/c/google/protobuf/descriptor.pb-c.h' failed make[1]: *** [generated/c/google/protobuf/descriptor.pb-c.h] Error 1 make[1]: Leaving directory '/root/warp17-1.8/api' Makefile:72: recipe for target 'all' failed make: *** [all] Error 2
When running the protoc versions I get the following
~# protoc-c --version libprotoc 2.5.0 :~# protoc --version libprotoc 3.0.0

[davvore33]

hi @francovz96,
I guess you've sort out something, if you can put here the solution you dig out so the next ones can use your contribution

[francovz96]

Hi @davvore33,

I haven't got it working on Ubuntu 18.04 LTS yet, I am running Warp on Ubuntu 14.04 LTS currently.

[mvdroest]

Seems to go wrong here also. Uninstalled the default stuff and packed all the old packages.
Still fails and is a pain in the ass to get the old stuff working. Is there any update to get it in a more modern system?

[davvore33]

Seems to go wrong here also. Uninstalled the default stuff and packed all the old packages.
Still fails and is a pain in the ass to get the old stuff working. Is there any update to get it in a more modern system?

Hi @mvdroest, I've tried lately to update to protobuf 3 but sadly Google changed the rpc under our feet dropping the old ones, so I'll have to change the API definition to the newer gRPC hoping that someone has done the C version (since google don't support it at all)

[mvdroest]

Thanks for that update. Downloaded the OFV to see if that also helps. Like to make it also work for ppl here that dont love Trex to much. So this seems to be a good way to go forward. Need to test also how i can fix i and help also.
@davvore33 Thanks for the update

[mcaulifn]

trusty is no longer available:

2019-04-23
    Reflect disco release, add eoan, remove trusty.

[davvore33]

trusty is no longer available:

2019-04-23
    Reflect disco release, add eoan, remove trusty.

I see, I'll repackage those old packets as temporary solution for protobuf

[mcaulifn]

any update on the legacy packages? do you have instructions on compiling each component from source?

[davvore33]

any update on the legacy packages? do you have instructions on compiling each component from source?

Hi @mcaulifn, I've tried creating a ppa for ubuntu but seems a quite complex procedure and sadly I'm in shortage of time, so right now I've uploaded the old debs on cloud and I'm writing a small bashscript that automatically installs the whole deps, those included, I'm going to share the branch today [CET]

[kentang-gs]

I run into the same problem here, is there any update on this?

[dfitzpatrick128]

@kentang-gs If i understand correctly this project has minimal/no development going forward. I hope i am wrong but looking at the commit history this appears to have fallen upon the wayside

[davvore33]

Hi all, yes as @dfitzpatrick128 correctly stated nobody is working on this anymore (since few years),
if my memory is not failing me the problem was with protobuf (we use proto2 in this project) and python (python2 as well)
moreover some other packets are old as well