[Bug]: Building `termux-am` hangs indefinitely

[CloudControlPro]

Problem description

termux - building termux-am for arch aarch64...
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.5/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build 

> Task :app:compileReleaseJavaWithJavac
Note: /root/.termux-build/termux-am/src/app/src/main/java/com/termux/termuxam/IntentCmd.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

BUILD SUCCESSFUL in 31s
36 actionable tasks: 36 executed
<-------------> 0% WAITING
> IDLE
> IDLE

What steps will reproduce the bug?

./build-package.sh -a aarch64 php

What is the expected behavior?

No response

System information

termux - building termux-am for arch aarch64...
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.5/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build 

> Task :app:compileReleaseJavaWithJavac
Note: /root/.termux-build/termux-am/src/app/src/main/java/com/termux/termuxam/IntentCmd.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

BUILD SUCCESSFUL in 31s
36 actionable tasks: 36 executed
<-------------> 0% WAITING
> IDLE
> IDLE

[TomJo2000]

This isn't an issue with the php package, but with the termux-am package by the looks of it.

[TomJo2000]

Can't replicate the issue locally. Gradle can take a pretty long time sometimes. Please use a process monitor like htop or btop to check that it is actually stuck, and not still processing background tasks.

[Grimler91]

Seems like you are not building in our docker image, and you have not provided any information about your environment, so pretty hard for anyone to investigate.

Please do not build as root user, there should be no reason to do so.

[TomJo2000]

Not sure why I didn't catch that. But yeah, building as root is not recommended.

[rlukas210]

i'm also suffering from this issue, using docker image also i have tried building xfce4, fluxbox, and termux-am is build as a dep, gradle just hangs

[TomJo2000]

i'm also suffering from this issue, using docker image also i have tried building xfce4, fluxbox, and termux-am is build as a dep, gradle just hangs

Are you also building as root or not?

[rlukas210]

Are you also building as root or not?

no, using just docker

[CloudControlPro]

I built it as root

------------------ 原始邮件 ------------------ 发件人: "termux/termux-packages" @.>; 发送时间: 2024年7月1日(星期一) 凌晨4:41 @.>; @.@.>; 主题: Re: [termux/termux-packages] [Bug]: Building termux-am hangs indefinitely (Issue #20651)

Are you also building as root or not?

no, using just docker

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[CloudControlPro]

Can you implement building python-pip?

------------------ 原始邮件 ------------------ 发件人: "termux/termux-packages" @.>; 发送时间: 2024年7月1日(星期一) 凌晨4:37 @.>; @.@.>; 主题: Re: [termux/termux-packages] [Bug]: Building termux-am hangs indefinitely (Issue #20651)

i'm also suffering from this issue, using docker image also i have tried building xfce4, fluxbox, and termux-am is build as a dep, gradle just hangs

Are you also building as root or not?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[TomJo2000]

I built it as root

As mentioned above already, we do not recommend or officially support that. Please build packages as a regular user, either in a properly configured environment, or using the supplied termux-package-builder docker container.

Can you implement building python-pip?

If you want to build python-pip, this would be the command to do it.

./scripts/run-docker.sh ./build-package.sh -I -f -a all python-pip

• ./scripts/run-docker.sh Run inside the package build container. (Optional if your enviroment is properly setup, though the container is the recommended method.)
• ./build-package.sh We're building a package.
• -I Download dependencies from the Termux repositories. This speeds up builds significantly. But is not available if your fork uses a different $PREFIX.
• -f Force rebuilds if the target package(s) are already built. Useful for testing build script changes.
• -a all Which architectures to build. If not specified it will default to aarch64. The options are: all, aarch64, arm, x86_64 and i686.
• python-pip The package(s) you want to build. This can be a list of one or more packages. The build system will figure out a build-order for you if some packages in the list depend on others. If that isn't the case they will just be built in the order specified.

[CloudControlPro]

 ./build-package.sh -I -f -a all python-pip  Can be compiled successfully

But I made modifications nano scripts/properties.sh   TERMUX_APP_PACKAGE="com.Cloudcontrol.script" Then compile  build-package.sh  -a aarch64  python-pip report errors

Installing /home/builder/.termux-build/glib/host-build/glib/gtester-report to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/bin Installing /home/builder/.termux-build/glib/src/glib/glib_gdb.py to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/glib-2.0/gdb Installing /home/builder/.termux-build/glib/host-build/glib/libglib-2.0.so.0.8000.3-gdb.py to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/gdb/auto-load/.//data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu Installing /home/builder/.termux-build/glib/host-build/gobject/glib-genmarshal to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/bin Installing /home/builder/.termux-build/glib/host-build/gobject/glib-mkenums to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/bin Installing /home/builder/.termux-build/glib/host-build/meson-private/gobject-2.0.pc to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu/pkgconfig Installing /home/builder/.termux-build/glib/src/gobject/gobject_gdb.py to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/glib-2.0/gdb Installing /home/builder/.termux-build/glib/host-build/gobject/libgobject-2.0.so.0.8000.3-gdb.py to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/gdb/auto-load/.//data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu Installing /home/builder/.termux-build/glib/host-build/meson-private/gthread-2.0.pc to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu/pkgconfig Installing /home/builder/.termux-build/glib/host-build/meson-private/gmodule-no-export-2.0.pc to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu/pkgconfig Installing /home/builder/.termux-build/glib/host-build/meson-private/gmodule-export-2.0.pc to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu/pkgconfig Installing /home/builder/.termux-build/glib/host-build/meson-private/gmodule-2.0.pc to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu/pkgconfig Installing /home/builder/.termux-build/glib/host-build/gio/gnetworking.h to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/include/glib-2.0/gio Installing /home/builder/.termux-build/glib/host-build/gio/gdbus-2.0/codegen/gdbus-codegen to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/bin Installing /home/builder/.termux-build/glib/host-build/gio/gdbus-2.0/codegen/config.py to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/glib-2.0/codegen Installing /home/builder/.termux-build/glib/src/gio/completion/gapplication to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/bash-completion/completions Installing /home/builder/.termux-build/glib/src/gio/completion/gdbus to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/bash-completion/completions Installing /home/builder/.termux-build/glib/src/gio/completion/gio to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/bash-completion/completions Installing /home/builder/.termux-build/glib/src/gio/completion/gsettings to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/bash-completion/completions Installing /home/builder/.termux-build/glib/src/gio/completion/gresource to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/bash-completion/completions Installing /home/builder/.termux-build/glib/host-build/meson-private/gio-2.0.pc to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu/pkgconfig Installing /home/builder/.termux-build/glib/host-build/meson-private/gio-unix-2.0.pc to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu/pkgconfig Installing /home/builder/.termux-build/glib/src/gio/gresource.dtd to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/glib-2.0/dtds Installing /home/builder/.termux-build/glib/src/gio/gschema.dtd to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/glib-2.0/schemas Installing /home/builder/.termux-build/glib/src/gio/gschema.loc to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/gettext/its Installing /home/builder/.termux-build/glib/src/gio/gschema.its to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/gettext/its Installing /home/builder/.termux-build/glib/host-build/meson-private/girepository-2.0.pc to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/lib/x86_64-linux-gnu/pkgconfig Installing /home/builder/.termux-build/glib/src/po/Makefile.in.in to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/glib-2.0/gettext/po Installing /home/builder/.termux-build/glib/src/m4macros/glib-2.0.m4 to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/aclocal Installing /home/builder/.termux-build/glib/src/m4macros/glib-gettext.m4 to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/aclocal Installing /home/builder/.termux-build/glib/src/m4macros/gsettings.m4 to /data/data/com.Cloudcontrol.script/files/usr/opt/glib/cross/share/aclocal Applying patch: gio-gdbusprivate.c.patch Applying patch: gio-gkeyfilesettingsbackend.c.patch Applying patch: gio-gnetworking.h.in.patch Applying patch: gio-gunixmounts.c.patch Applying patch: gio-xdgmime-xdgmime.c.patch Applying patch: glib-gcharset.c.patch Applying patch: glib-gspawn.c.patch Applying patch: glib-gthread-posix.c.patch Applying patch: glib-gthreadprivate.h.patch Applying patch: glib-gtimezone.patch Applying patch: glib-gtypes.h.patch Applying patch: glib-gutils.c.patch Applying patch: glib-tests-meson.build.patch Applying patch: meson.build.patch sed: can't read /data/data/com.Cloudcontrol.script/files/usr/lib/pkgconfig/gobject-introspection-1.0.pc: No such file or directory

May I ask how to specifically resolve the error sed: can't read /data/data/com.Cloudcontrol.script/files/usr/lib/pkgconfig/gobject-introspection-1.0.pc: No such file or directory

------------------ 原始邮件 ------------------ 发件人: "termux/termux-packages" @.>; 发送时间: 2024年7月1日(星期一) 上午10:09 @.>; @.@.>; 主题: Re: [termux/termux-packages] [Bug]: Building termux-am hangs indefinitely (Issue #20651)

I built it as root

As mentioned above already, we do not recommend or officially support that. Please build packages as a regular user, either in a properly configured environment, or using the supplied termux-package-builder docker container.

Can you implement building python-pip?

If you want to build python-pip, this would be the command to do it. ./scripts/run-docker.sh ./build-package.sh -I -f -a all python-pip

./scripts/run-docker.sh Run inside the package build container. (Optional if your enviroment is properly setup, though the container is the recommended method.)

./build-package.sh We're building a package.

-I Download dependencies from the Termux repositories. This speeds up builds significantly. But is not available if your fork uses a different $PREFIX.

-f Force rebuilds if the target package(s) are already built. Useful for testing build script changes.

-a all Which architectures to build. If not specified it will default to aarch64. The options are: all, aarch64, arm, x86_64 and i686.

python-pip The package(s) you want to build. This can be a list of one or more packages. The build system will figure out a build-order for you if some packages in the list depend on others. If that isn't the case they will just be built in the order specified.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>