cmeng-git / atalk-android

xmpp/jabber client for android
Apache License 2.0
155 stars 56 forks source link

F-Droid build failed #202

Closed linsui closed 1 year ago

linsui commented 1 year ago

https://monitor.f-droid.org/builds/log/org.atalk.android/301040#site-footer

========== Updating x264 source: x264 (164) ==========
Cloning into 'x264'...
========== Completed sub modules update ==========
### Applying patches for x264-v164.3095 modules
**********************************************
### Use NDK=/opt/android-sdk/ndk/18.1.5063045
### Use ANDROID_API=21
### Install directory: PREFIX=/home/vagrant/build/org.atalk.android/aTalk/jni/static_library_built/ffmpeg-x264/../../ffmpeg/android/armeabi-v7a
**********************************************
~/build/org.atalk.android/aTalk/jni/static_library_built/ffmpeg-x264/x264 ~/build/org.atalk.android/aTalk/jni/static_library_built/ffmpeg-x264

** BUILD STARTED: x264-v164 for armeabi-v7a **
Makefile:3: config.mak: No such file or directory
cat: config.h: No such file or directory
./configure
No working C compiler found.
make: *** [config.mak] Error 1
platform:       ARM
byte order:     little-endian
system:         LINUX
cli:            no
libx264:        internal
shared:         no
static:         yes
bashcompletion: no
asm:            yes
interlaced:     yes
avs:            no
lavf:           no
ffms:           no
mp4:            no
gpl:            yes
thread:         no
opencl:         no
filters:        crop select_every
lto:            no
debug:          no
gprof:          no
strip:          yes
PIC:            yes
bit depth:      all
chroma format:  all

It seems it failed here. Could you please take a look? Thanks!

cmeng-git commented 1 year ago

I have checked, confirmed the missing 2 files are not the cause of the problem. The 2 files are generated during the build. Looking through the build log file, I see that there are only a few jni *.a libraries being generated. Not sure if this is because the build is prematurely terminated.

As the aTalk build is complex, I would advise you to do a manual build to confirm your build environment is properly set up. The jni libraries can be built using the shell scripts in the static_library_build directory. The shell script can be manually executed in a linux terminal window. This way you can isolate where the problem is.

From the build log, I am not able to figure out where the problem lies.

regards, CM Eng

On Mon, Feb 27, 2023 at 1:12 PM linsui @.***> wrote:

https://monitor.f-droid.org/builds/log/org.atalk.android/301040#site-footer

========== Updating x264 source: x264 (164) ========== Cloning into 'x264'... ========== Completed sub modules update ==========

Applying patches for x264-v164.3095 modules


Use NDK=/opt/android-sdk/ndk/18.1.5063045

Use ANDROID_API=21

Install directory: PREFIX=/home/vagrant/build/org.atalk.android/aTalk/jni/static_library_built/ffmpeg-x264/../../ffmpeg/android/armeabi-v7a


~/build/org.atalk.android/aTalk/jni/static_library_built/ffmpeg-x264/x264 ~/build/org.atalk.android/aTalk/jni/static_library_built/ffmpeg-x264

BUILD STARTED: x264-v164 for armeabi-v7a Makefile:3: config.mak: No such file or directory cat: config.h: No such file or directory ./configure No working C compiler found. make: *** [config.mak] Error 1 platform: ARM byte order: little-endian system: LINUX cli: no libx264: internal shared: no static: yes bashcompletion: no asm: yes interlaced: yes avs: no lavf: no ffms: no mp4: no gpl: yes thread: no opencl: no filters: crop select_every lto: no debug: no gprof: no strip: yes PIC: yes bit depth: all chroma format: all

It seems it failed here. Could you please take a look? Thanks!

— Reply to this email directly, view it on GitHub https://github.com/cmeng-git/atalk-android/issues/202, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4XINSEOW7JAONL3IYRBHTWZQZSXANCNFSM6AAAAAAVI54MMU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

licaon-kter commented 1 year ago

This can be closed, right?

/LE: deleted the other post, read the CI wrong, no issue there

cmeng-git commented 1 year ago

Issue resolved.