Container build script fails to compile GCC #39
Comments
|
Can you supply the error contents of the build.log file that the output mentions? The command line that failed, and the error output that followed, will be super helpful! 😀 |
|
Pinging @cam-rod (see #38). I forgot about it, but I believe we landed on reverting and not supporting that. I'd still expect it to work though, given that nothing changed since. |
|
@matthargett I did look for it but I couldn't find it inside the container, do you happen to know the directory and whether or not to look in the container or the host? Unless I'm blind, it didn't say where to look. @Frenzie thanks for linking that PR again, I did scan it briefly but last time I missed the mention of https://github.com/koreader/virdevenv, that may make this issue redundant for me :) May I suggest linking to there from https://github.com/koreader/koxtoolchain?tab=readme-ov-file#container-image ? I was under the impression that koreader/koxtoolchain only supported podman, not docker images. I can submit a PR for that change, if desired. |
Not quite unfortunately, the images there have been optimized in the meantime since it's built here anyway, which strikes me as a bit of a Catch 22 but in any case you can just quickly run |
|
Yeah I was wondering about that, I may end up making my own docker image... For context, I'm attempting to compile the Erlang/Elixir VM for my Kobo 😄 So the virdevenv images might contain either too much or not enough, so a bespoke image might not be a bad idea... Anyway, figured it was better to start with letting you folks know about the podman image first 🙂 Since this is not going to be supported with #40, I'll go ahead and close this issue. |
|
Generally speaking wouldn't it be easier to simply download and use https://github.com/koreader/koxtoolchain/releases/tag/2021.12? |
|
Generally speaking probably, but I'd prefer to have a container that has the toolchain installed so I can keep my environment isolated. I generally prefer to not add stuff that's only required for one project to my |
|
Note that's what |
|
Hmm you're right, the first time I skimmed through that file I think I missed the early return inside the |
|
I can confirm the problem anyway. I might look into why some other day. |
Hello! When running
./buildah-koxtoolchain.sh kobo, it fails at the step[INFO ] Installing C librarywith the following error logs:After this, the container is built and can be ran with the command
podman run --rm -it -v .:/home/kox/build koxtoolchain:kobo-latest, however gcc and some of the other tools are missing. The contents of the/home/kox/x-tools/directory is as follows:I am building on Arch Linux, with
buildah version 1.35.3 (image-spec 1.1.0, runtime-spec 1.1.0)andpodman version 5.0.1. I installed the dependencies listed in the readme even though this is building inside a container, not sure if it makes a difference or not.The text was updated successfully, but these errors were encountered: