| Message ID | 20220216232654.1868016-1-quaresma.jose@gmail.com |
|---|---|
| State | Accepted, archived |
| Commit | 25ea276a13a6ac2342c2b0945c8fafe878d56095 |
| Headers | show |
| Series | icecc.bbclass: enable networking in all tasks | expand |
diff --git a/meta/classes/icecc.bbclass b/meta/classes/icecc.bbclass index 3bbd2645af..68415b04c7 100644 --- a/meta/classes/icecc.bbclass +++ b/meta/classes/icecc.bbclass @@ -428,18 +428,22 @@ set_icecc_env() { bbnote "Using icecc tarball: $ICECC_VERSION" } +do_configure[network] = "1" do_configure:prepend() { set_icecc_env } +do_compile[network] = "1" do_compile:prepend() { set_icecc_env } +do_compile_kernelmodules[network] = "1" do_compile_kernelmodules:prepend() { set_icecc_env } +do_install[network] = "1" do_install:prepend() { set_icecc_env }
The icecc.bbclass needs network access to work properly. Currently I build with icecc inside a container with network isolation and my icecc daemon runs outside of the build container in my host. The only thing I need to do for using the icecc inside my build container is mounting the unix socket /var/run/icecc/iceccd.socket inside the container. I think we need something like this mount functionality to have access to some sockets connections inside the tasks that runs on the new namespace created with unshare system call. This patch is not a the real solution for the problem and is more like an hack so we can use the icecc.bbclass again. Signed-off-by: Jose Quaresma <quaresma.jose@gmail.com> --- meta/classes/icecc.bbclass | 4 ++++ 1 file changed, 4 insertions(+)