From nobody Sun Mar 20 11:46:53 2022 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9D82B1A33108 for ; Sun, 20 Mar 2022 11:46:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KLwvd2XWhz4S19 for ; Sun, 20 Mar 2022 11:46:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 37146267CC for ; Sun, 20 Mar 2022 11:46:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 22KBkrtT018391 for ; Sun, 20 Mar 2022 11:46:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 22KBkrAL018390 for ports-bugs@FreeBSD.org; Sun, 20 Mar 2022 11:46:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 262216] devel/bazel 5.0.0 does not work after successful installation on freebsd 13.0 Date: Sun, 20 Mar 2022 11:46:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ulassayginim@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1647776813; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VW7UB1pPpLtpjPNotxIqspyeT5jFbaFIhUvwfE9AIKQ=; b=ZLOaDkLna6MtQuPG2EWwcxHJmKY5x5J5WOjndI1HuvrBcqv2uD0V1edzVTPJ+GRnntFcEN agr24cJ8LuzFb68MNNNREP0EQCKCz6B/mNxK+DCMY10YwMTZmqWEJ/mRHJYPS0BLb1mt3r Yn0cJAyCEF3iCKt1ev2cLJ9KH+AaAIOjpYdfESE5NtOaNxJ62QGNOCkAy9K+JGOb0LcZqs CFddwBMgiHcZqFVFxpZh7BZVA3d61FTcMjoQ/4p5VapfLkRSVmtizFcFnSKdLqTFlOSfXN cv0X4aZJek52Wtp8Dc6E7xUz0B9iNHba7IXgrVW3Fba/qhZ5y6eyR26j4qmbhA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1647776813; a=rsa-sha256; cv=none; b=ENMANAwFTYZsfS7UBEJif/x216WbqRAL6pd1o9BOyA4/jTocJQNQoaptH4qAE69p/U+nJ7 Hr8ufIee+8w4f3JWxNQEUUUKhIn6QKVIEOQaQ/YDvO4trQ+lTaLBmGzqB1HAts5ydYYNPP ODvIxDyhqwFfLIurc1ixIsAyOVy/X1w8jD+YJUMPeKOi7t7X/vb/mCPNUqkdCzuj+VMExW CnKS0vJBDBhOcgybrwnND/C6fjXFbjr3ZybtKW/7husnnmRIKCWg41/NATuC9xVRJ9295F PXsVQHj99B87Y+tA/bpC75oQjdJzLIilv/oAQrm+ZQ3hKg6Nis023fcFiFxh4w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262216 --- Comment #20 from Ulas SAYGIN --- (In reply to Klaus Aehlig from comment #19) Thank you for your help. what do you think about to make bazel compile envoyproxy?=20 i mean you said remotejdk_11 seems problem for compiling but you said it is= not only problem. what other problems you think? i read documentation but i really dont understand remotejdk magic. because bazel has jdk 11 support why people dont use it for envoyproxy? what is the problem. in this case, envoyproxy developers seem to me they do= nt want to use all options as they said to compatible with all cpu architectur= es. because , their strong argument about to use bazel is cmake didnt provide e= nvoy to compile for some cpu archectures. if they really care about it, compiling for freebsd shouldnt be problem :) i also find converters from bazel to cmake but none of them seems working completely :( i tried to change bazel.rc file by editing local_jdk but no luck. i think envoy bazel settings are not complete. i dont know how to overcome this, because i am not familiar with bazel and = its documentation does not seem well to me. there are a lot of things changed and discussed in github issues and people give some command prompt args but i am not able to correct envoy bazel with them. lastly, i just want 2 things from you. can we have port for bazel 4.2 version? seperately to test bazel? because now i am not able to compile example java projects of bazel :) i thougt that this bazel should have at least 4.2 version as stable and wor= king without problem. i think this version seems ok but i know it may not have latest config changes or it may have i am not sure how bazel developers thi= nk about compability old versions of bazel. can we have port for bazel4.2? whi= ch is major version, if i am not wrong. /usr/ports/devel/bazel42 could be nice= , if it is possible. or if you can provide patch for this, i can try. second thing is ,can you able compile example java projects of bazel which gives on documentation? did you try it? if not,can you try it to be sure ab= out java tool chain is not working? or working as expected. i think we are not = sure about that, or at least i am for other peoples system. thanks a lot for you help. i would like to have envoyprxy for freebsd if i can achieve the bazel works without problem:) and many more other ports. --=20 You are receiving this mail because: You are the assignee for the bug.=