-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
32 bit build... #1340
Comments
Can you try to compile Bazel from source?
This will create a bazel binary in bazel-bin/src/bazel. |
I know how to compile... And I already tried. It just wouldn't. |
Can you show me the error you got when running ./compile.sh? |
No, I won't have my laptop back for a few days (probably at least a week, maybe two). I don't recall what they were either. |
Bazel only supports 64-bit platforms. Unfortunately we can't help with building it on 32-bit platforms. |
Because bazel will not build (at all) on 32 bit: bazelbuild/bazel#1340
If there is a 32bit compatible Remote Executor (https://docs.bazel.build/versions/2.0.0/remote-execution.html), it might be possible to build and test on 32 bit with bazel that way. |
As per this issue, Bazel project does not release binaries for i686 and as per #8652 the binaries are not expected to work on RHEL6x. And they indeed do not work:
Let me drop here notes about getting Bazel on RHEL6i. I tried first running the binaries under qemu-x86_64 and then I tried remote execution. Remote execution seems to work and solves my goal of performning RHEL6i builds with Bazel. I was not able to get the qemu-x86-64 solution to work. Remote executionhttps://docs.bazel.build/versions/master/remote-execution.html This looks to be the way. ScootThere is Go toolchain for i686, awesome! When I compiled the project, I hit a few issues, the last of which looked hard to fix, and I got Buildfarm working next, so I did not investigate.
Scoot does not work for me. BuildfarmThat worked fine. I built the _dist.jars on another machine, shipped them onto rhel6i machine, together with sample configs, and was able to start remote build of Buildfarm itself. I am still watching for issues.
Seems to be working fine so far. QemuCompile qemu, as per https://wiki.qemu.org/Hosts/Linux
Register qemu-x86_64 as the interpreter for 64bit binaries, from https://k3a.me/running-x86_64-amd64-executables-on-ppc64le-ibm-power-9-gentoo/
Copy 64bit libraries from Ubuntu Trusty docker image (docker --rm -it library/ubuntu:trusty) onto the rhel6i system. Taking libraries from a rhel6x does not help (glibc and libstdc++ are too old there) and with libraries from rhel7x I get a segfault. So Trusty it is.
I saw "cannot mmap brk" error from qemu, apparently caused by running out of RAM, since adding more memory to the rhel6i VM solved the problem. qemu 0.14.0, 1.5.1
qemu 2.3.1
And I stopped version climbing at qemu 3.0.1 because I don't have packaged dependemcies in repo for it any more
As a last resort, qemu 4.2.0, the latest version, also needs a custom kernel (due to qemu 4.2, linux/if_alg.h: No such file or directory; installed http://elrepo.org/tiki/kernel-lt) and updated glibc. I had two issues there
Never the less, after doing all this, I got a segfault this time
Qemu way did not work for me. |
My laptop is 32 bit and all of the releases are 64 bit.
So basically I'm requesting a 32 bit .deb build.
The text was updated successfully, but these errors were encountered: