Skip to content

Conversation

@benoit-pierre
Copy link
Member

@benoit-pierre benoit-pierre commented Apr 21, 2025

This change is Reviewable

@benoit-pierre
Copy link
Member Author

I don't know why the remarkable-aarch64 build is failing:

[INFO ]    Building for multilib 1/1: ''
[EXTRA]      Configuring C library
[ERROR]      configure: error: *** The available kernel headers are older than the requested
[ERROR]  
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Building for multilib 1/1: '''
[ERROR]  >>        called in step 'Installing C library'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@378]
[ERROR]  >>        called from: glibc_backend_once[scripts/build/libc/glibc.sh@296]
[ERROR]  >>        called from: CT_IterateMultilibs[scripts/functions@1610]
[ERROR]  >>        called from: glibc_main[scripts/build/libc/glibc.sh@87]
[ERROR]  >>        called from: do_libc_main[scripts/build/libc.sh@33]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@710]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      https://crosstool-ng.github.io/docs/known-issues/
[ERROR]  >>
[ERROR]  >> NOTE: Your configuration includes features marked EXPERIMENTAL.
[ERROR]  >> Before submitting a bug report, try to reproduce it without enabling
[ERROR]  >> any experimental features. Otherwise, you'll need to debug it
[ERROR]  >> and present an explanation why it is a bug in crosstool-NG - or
[ERROR]  >> preferably, a fix.
[ERROR]  >>
[ERROR]  >>  If you feel this is a bug in crosstool-NG, report it at:
[ERROR]  >>      https://github.com/crosstool-ng/crosstool-ng/issues/
[ERROR]  >>
[ERROR]  >>  Make sure your report includes all the information pertinent to this issue.
[ERROR]  >>  Read the bug reporting guidelines here:
[ERROR]  >>      http://crosstool-ng.github.io/support/
[ERROR]  
[ERROR]  (elapsed: 16:26.18)

@NoaHimesaka1873
Copy link
Contributor

Might be some mismatch? It does build fine on 22.04 GH Actions and my personal Arch Linux installation. Try downgrading to 22.04.

@benoit-pierre
Copy link
Member Author

But we're building in docker now, which should isolate us from the runner image version.

@benoit-pierre
Copy link
Member Author

Looking at the diff between the 2 remarkable configs, I noticed that we're not using CT_STRIP_TARGET_TOOLCHAIN_EXECUTABLES=y:

--- /proc/self/fd/13	2025-04-22 04:30:11.623395735 +0200
+++ /proc/self/fd/15	2025-04-22 04:30:11.624395752 +0200
@@ -1,25 +1,18 @@
 CT_CONFIG_VERSION="4"
-CT_OBSOLETE=y
 CT_EXPERIMENTAL=y
-CT_STRIP_TARGET_TOOLCHAIN_EXECUTABLES=y
 CT_ARCH_ARM=y
-CT_ARCH_CPU="cortex-a9"
-CT_ARCH_ARM_MODE_THUMB=y
-CT_ARCH_FPU="neon"
-CT_ARCH_FLOAT_HW=y
-CT_TOOLCHAIN_PKGVERSION="NiLuJe"
+CT_ARCH_64=y
+CT_ARCH_CPU="cortex-a53"
+CT_TOOLCHAIN_PKGVERSION="Noa Himesaka"
 CT_TARGET_VENDOR="remarkable"
 CT_KERNEL_LINUX=y
-CT_LINUX_V_4_9=y
+CT_LINUX_V_6_1=y
 CT_BINUTILS_LINKER_LD_GOLD=y
 CT_BINUTILS_GOLD_THREADS=y
 CT_BINUTILS_LD_WRAPPER=y
 CT_BINUTILS_PLUGINS=y
-CT_GLIBC_V_2_27=y
+CT_GLIBC_V_2_35=y
 CT_GLIBC_KERNEL_VERSION_CHOSEN=y
-CT_GLIBC_MIN_KERNEL_VERSION="4.1.28"
-# CT_CC_GCC_STATIC_LIBSTDCXX is not set
-# CT_CC_GCC_USE_GRAPHITE is not set
-# CT_CC_GCC_ENABLE_TARGET_OPTSPACE is not set
+CT_GLIBC_MIN_KERNEL_VERSION="6.1.55"
 CT_CC_GCC_LNK_HASH_STYLE_GNU=y
 CT_CC_LANG_CXX=y

Might be why the resulting artifact is ~48 MB bigger for remarkable-aarch64 than remarkable? (Cf. https://github.com/koreader/koxtoolchain/actions/runs/14551016601)

@NoaHimesaka1873
Copy link
Contributor

Yeah I missed that one. Though it shouldn't affect compiling.

@NoaHimesaka1873
Copy link
Contributor

I think we should merge the bare 22.04 one and work on this kobase one later, since it would work the same way for now.

@NoaHimesaka1873
Copy link
Contributor

NoaHimesaka1873 commented Apr 22, 2025

Can repro this weird behavior on my local machine running same container to build. It fetches Linux version 5.2 when it should try to fetch 6.1. Also happens on vanilla ubuntu:22.04 container.

@NoaHimesaka1873
Copy link
Contributor

I dug a bit further, but still can't figure out why it's downgrading itself to 5.2. I think it's better to build remarkable-aarch64 on bare GH Actions 22.04.

@benoit-pierre benoit-pierre force-pushed the pr/use_our_docker_kobase_image_for_ga branch from 82636cb to f55106a Compare April 22, 2025 20:21
@benoit-pierre
Copy link
Member Author

Linux >=5.3 requires rsync…

@benoit-pierre benoit-pierre force-pushed the pr/use_our_docker_kobase_image_for_ga branch from f55106a to a319a15 Compare April 22, 2025 22:32
@benoit-pierre benoit-pierre marked this pull request as ready for review April 22, 2025 22:32
@benoit-pierre
Copy link
Member Author

git.savannah.gnu.org being flaky…

@NoaHimesaka1873
Copy link
Contributor

Linux >=5.3 requires rsync…

Oh shoot, how could I miss that lol

@benoit-pierre
Copy link
Member Author

@NiLuJe: ping!

@NiLuJe
Copy link
Member

NiLuJe commented May 8, 2025

Oh, sorry, didn't notice this was in this repo, lol ;).

@NiLuJe NiLuJe merged commit 887079d into koreader:master May 8, 2025
13 of 26 checks passed
@benoit-pierre benoit-pierre deleted the pr/use_our_docker_kobase_image_for_ga branch May 9, 2025 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants