Hi Gal,
On Mon, 12 Sept 2022 at 05:14, Gal Aviel <galav...@gmail.com> wrote:Greetings!I'm trying to build under SUSE Linux Enterprise Server 12 (x86_64).I don't have root access.I must say that the build process is very complicated and frustrating. 10 years ago it was as simple as configure; make; make install however nowadays you must spend 1/2 a day installing bazel...
Yeah sorry, I feel you. Advantage of Bazel is, that it allows to describe dependencies hermetically, but disadvantage is, that it is a complicated, java-based system that is currently not very mainstream.
Anyway I think I managed to compile bazel from source, I have a 'bazel-devel' binary.
I have not recently used SUSE; but it seems like there are pre-installable binaries (I just found https://docs.bazel.build/versions/4.2.2/install-suse.html )You need bazel version 4.For the self-compilation, you probably need to do a lot of additional configuring, for instance what you local tooolchain is (gcc and such), at least that is what the error message w.r.t platform constraints and toolchain indicates below as a potential problem. Is it possible for you to test the pre-installable version of bazel ?
In the meantime, I will also check if the platform constraints can be formulated a bit differently (for context: these are essentially used for platform independent compilation rules, something like 'on windows, don't add this warning flag').We should maybe also consider adding OpenSUSE-compatible pre-compiled binaries in the releases (https://github.com/chipsalliance/verible/releases)
Hope this helps to get this sorted out.Henner.
When I try to run"bazel-dev build -c opt --repository_cache /tmp/<user>/bazel_repo_cache/ //verilog/tools/syntax:verible-verilog-syntax"I'm getting the below error message.Any help is greatly appreciated!thanks, Gal.---WARNING: Output base '/nfs/site/disks/home80/<user>/.cache/bazel/_bazel_<user>/5391d109076636e51abc1524bed7e4a3' is on NFS. This may lead to surprising failures and undetermined behavior.
Loading:
Loading: 0 packages loaded
Analyzing: target //verilog/tools/syntax:verible-verilog-syntax (0 packages loaded, 0 targets configured)
ERROR: /nfs/site/disks/home80/<user>/.cache/bazel/_bazel_<user>/5391d109076636e51abc1524bed7e4a3/external/bazel_tools/platforms/BUILD:89:6: in alias rule @bazel_tools//platforms:windows: Constraints from @bazel_tools//platforms have been removed. Please use constraints from @platforms repository embedded in Bazel, or preferably declare dependency on https://github.com/bazelbuild/platforms. See https://github.com/bazelbuild/bazel/issues/8622 for details.
ERROR: /nfs/site/disks/home80/<user>/.cache/bazel/_bazel_<user>/5391d109076636e51abc1524bed7e4a3/external/bazel_tools/platforms/BUILD:89:6: Analysis of target '@bazel_tools//platforms:windows' failed
ERROR: /tmp/<user>/verible/verilog/tools/syntax/BUILD:7:10: While resolving toolchains for target //verilog/tools/syntax:verible-verilog-syntax: invalid registered toolchain '@bazel_skylib//toolchains/unittest:cmd_toolchain':
ERROR: Analysis of target '//verilog/tools/syntax:verible-verilog-syntax' failed; build aborted:
INFO: Elapsed time: 0.094s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 0 targets configured)
FAILED: Build did NOT complete successfully (0 packages loaded, 0 targets configured)
--
You received this message because you are subscribed to the Google Groups "Verible Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to verible-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/verible-users/674e8755-7f61-43dc-8a39-cd0bc22b0f06n%40googlegroups.com.
1. OpenSuse binaries: can't use zypper - since I don't have root access. I work in a big corporation and don't have root. Tried work-arounds such as https://unix.stackexchange.com/questions/171568/zypper-how-to-install-a-package-in-local-bin-directory however still doesn't work - zypper won't let me even download the binaries without root access. Even if I could - would openSuse binaries work on Suse enterprise 12?
2. bazel-dev --version : since building 'verible' failed, I thought the issue might be with 'bazel' so I've cloned latest (git clone https://github.com/bazelbuild/bazel) and build it (bazel build //src:bazel-dev --repository_cache /tmp/<user>/bazel_repo_cache). Thinking perhaps the stable release of bazel isn't up to date for verible.Again, not trivial and I'm not sure I got it right - you need to boot-strap by downloading the stable release 5.3).
Also note I'm running on /tmp since bazel keeps complaining that running on NFS is bad...Anyway, bazel-dev --version returns:[FATAL 10:02:47.134 src/main/cpp/archive_utils.cc:67] Failed to find member 'build-label.txt' in zip file '/tmp/<user>/.cache/bazel/_bazel_<user>/08e1fc2229922b3ac823cfaf4c7d918f/execroot/io_bazel/bazel-out/k8-fastbuild/bin/src/bazel-dev'So again I'm not sure what's going on.
3. Consider that many of verible's potential users might work in big corporations, where distro's such as Enterprise Suse and/or RHEL are very common, whereas they might be less common in the open source world. So you would potentially miss out of those users.
4.Is there a possibility to provide a *statically-linked* binary for linux X64? Even if such a binary would be much bigger, for me this is a doable option.
5. Just an observation, again working with bazel is non trivial. It seems 'bazel' doesn't like NFS (NFS or other networked file systems are a must for corporate users...) and it also keeps using my home directory's .cache - again corroborate users have very limited space there.. so it's quite problematic.
To view this discussion on the web visit https://groups.google.com/d/msgid/verible-users/ea00bc6b-199c-413f-97d7-24befa0a98ccn%40googlegroups.com.
by mistake the last run was on Suse 11.4 and not 12 as I thought (Ran on our VNC hosting machine not the strong workstations..)
Anyway the Ubuntu-16 binary seems run happily under Suse Enterprise 12:>ldd ../../../downloads/verible-v0.0-2297-gd7d32592/bin/verible-verilog-syntax
linux-vdso.so.1 (0x00007ffff7ffa000)
libm.so.6 => /lib64/libm.so.6 (0x00007ffff7ade000)
libpthread.so.0 => /lib64/noelision/libpthread.so.0 (0x00007ffff78c1000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007ffff76a9000)
libc.so.6 => /lib64/libc.so.6 (0x00007ffff7304000)
/lib64/ld-linux-x86-64.so.2 (0x00007ffff7ddb000)Indeed very few dependancies ...Thanks allot !!! I'm a happy campter :)Ok now that I have it running - I can now batch run it on all our standard modules !