hi, this port seems out of date. please update it. because it is not possible to compile it. current version is 1.10 dated to 11 Jul 2019 https://www.envoyproxy.io/docs/envoy/v1.10.0/intro/version_history
@Reporter If the current version of the port currently fails to build, could you please include (as an attachment), the build log, compressed if necessary.
(In reply to Kubilay Kocak from comment #1) > could you please include (as an attachment), the build log, compressed if > necessary. Kubilay, please do not ask for these files unless you want/plan to look into them yourself. Ulas, I'm well aware of the issue, there's no need to attach log files or anything else.
with respectively first of all, hi Kubilay, i also reported envoy failing compilation on another bug report, the boringssl was not able compile with security/nettle ports. you can see error on this link, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262114 (In reply to Kubilay Kocak from comment #1) Hi Alexey, i am glad that you are here. and know the pain i have about this port. thank you for understanding and help. i would like to tell you things in my mind for envoy latest version. I saw a comment on their github issues. community is not approve other than bazel builds version of envoy proxy. they think that it may cause problem if envoy is compiled by another build methods like cmake and others. because they encountered problems on some cpu architectures about compilation and it seems that they are trying to doing their best. in this case, i think compilation of envoy must be done by bazel build system. in order to give a try, i also installed bazel on freebsd port tree lucky it has 5.0 release version. 6 version is coming but it is RC. after successfully installed bazel on my freebsd 13 vanilla install. i tried to build envoy but i encountered some errors, first bazel couldnt find python 3.10 and i have to symlink as python3 than it asked pip3 but it couldnt install itself , i have to install it by python command. than it found and started to working but it gave a problem about building, i was thinking this can be related to envoy but than i tried bazel example codes to demonstrate bazel build. it tired to compile example c++ project but it gave similar jdk error. by the way openjdk11 is compiled by bazel as port dependency and working without problem. but i am thinking that can it be some software path problem like ptyhon3 ? but i couldnt find the which path bazel looking. i asked bazel github account about it. this is the link of it. i copied 2 errors for both envoy and c++ examples of bazel build. you can see to find the cause. thanks a lot for you time and have great day. https://github.com/bazelbuild/bazel/issues/14891 (In reply to Alexey Dokuchaev from comment #2)
envoy on freebsd side seems DEAD unless someone or some team do something. https://github.com/envoyproxy/envoy/issues/20130#issuecomment-1054507314
this may bring some joy : https://github.com/envoyproxy/envoy-openssl/issues/1#issuecomment-1054128983
I think there is 2 ways to install envoy latest version on freebsd. first , change build system from bazel build to cmake or make which can be usable for freebsd than install with necessary patches. wewill also need openssl support. latest version seems there is support for openssl. secondly, build bazel with toolchains, because without toolchain you cant build any project which needs toolchain.i think most of the projects needs toolchain wth bazel but bazel build system does not officially support freebsd and because of this, you need to find the way to compile tool chain on freebsd. i am not sure,any of the bazel toolchain not in the freebsd port tree. because i am not able to look and print list of tool chain ports which need to be installed. after toolchain ports installed you need to tell bazel , please use all tool chains from local ones not remote ones. in this case, bazel build system started to build envoy latest version and we can see can it be build successfully or not. is there ANY talented and knowledgeable person which can overcome this issues and get ports on its feets! i hope we have that person or people who will support FreeBSD port system.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=b988824351d62cbfffe1fc6c905ec87de85f3e3f commit b988824351d62cbfffe1fc6c905ec87de85f3e3f Author: Alexey Dokuchaev <danfe@FreeBSD.org> AuthorDate: 2023-06-09 10:16:26 +0000 Commit: Alexey Dokuchaev <danfe@FreeBSD.org> CommitDate: 2023-06-09 10:16:26 +0000 www/envoy: the port had been updated to version 1.26.1 \o/ Currently, only a limited set of extensions is being built, e.g. WASM-related code was disabled due to unsolved issues. Please send patches to enable missing functionality, there are lots of features remain to be explored. Unfortunately, it still requires BoringSSL for the moment. PR: 262115 www/envoy/Makefile | 112 +++-- www/envoy/distinfo | 36 +- www/envoy/files/makefile-genproto | 212 +++++++- www/envoy/files/makefile-main | 539 ++++++++++++++++++--- .../files/patch-envoy_common_platform.h (new) | 20 + .../patch-source_common_common_logger.cc (gone) | 11 - ...atch-source_common_common_posix_thread__impl.cc | 2 +- ...atch-source_common_common_stack__array.h (gone) | 12 - ...atch-source_common_json_json__internal.cc (new) | 12 + ...ommon_network_io__socket__handle__impl.cc (new) | 20 + ...common_network_io__socket__handle__impl.h (new) | 11 + .../files/patch-source_common_protobuf_utility.h | 12 +- ...access__loggers_open__telemetry_config.cc (new) | 12 + 13 files changed, 849 insertions(+), 162 deletions(-)
(In reply to Ulas SAYGIN from comment #6) > first, change [the] build system from bazel to cmake or make We've been doing it since day one: on FreeBSD, the port is built with pure GNU make. I've feared this might not scale well against newer versions, but it's still quite manageable as of recent update to version 1.26.1. > we will also need openssl support. Yes, we certainly do, e.g. because BoringSSL prevents it from being packaged by default: one has to manually set DEFAULT_VERSIONS+=ssl=boringssl. > latest version seems there is support for openssl. I've poked around that OpenSSL fork when it appeared, but couldn't get it to work, patches welcome!