You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for providing the cross-compilation toolchain. I’ve successfully used it to compile and run an x86_64-linux version of my program. However, when I attempted to compile the arm-linux version and run it, the device displayed a "kernel too old" message. I suspect this is due to the newer versions of gcc, glibc, etc., in the cross-compilation toolchain you provided. Therefore, I plan to use crosstool-ng to build a new cross-compilation toolchain.
I’m attempting to build a cross-compilation toolchain using crosstool-ng on macOS, but I’ve encountered an error during the process. Specifically, the build fails at the step where it’s installing m4 for the build. The error message indicates an issue with the execution of make during the m4 installation step.
I’ve followed the official crosstool-ng documentation, ensuring all dependencies are installed and environment variables configured, but the error persists. Here’s the relevant part of the error log:
[CFG ] config.status: creating examples/Makefile
[CFG ] config.status: creating lib/config.h
[CFG ] config.status: linking /Volumes/WD_APFS_SENSE/ct-ng/arm-unknown-linux-gnueabi/.build/arm-unknown-linux-gnueabi/src/m4/GNUmakefile to GNUmakefile
[CFG ] config.status: executing depfiles commands
[CFG ] config.status: executing stamp-h commands
[DEBUG] ==> Return status 0
[EXTRA] Building m4
[DEBUG] ==> Executing: 'make'
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step 'Installing m4 for build'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@378]
[ERROR] >> called from: do_m4_backend[scripts/build/companion_tools/100-m4.sh@77]
[ERROR] >> called from: do_companion_tools_m4_for_build[scripts/build/companion_tools/100-m4.sh@18]
[ERROR] >> called from: do_companion_tools_for_build[scripts/build/companion_tools.sh@35]
[ERROR] >> called from: main[scripts/crosstool-NG.sh@712]
[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] >> 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: 1:30.00)
I’ve already consulted the known issues list at crosstool-ng known issues but couldn’t find a solution that applies to my case.
Has anyone experienced a similar issue or have any suggestions on how to resolve this? I would greatly appreciate any guidance on what might be causing this error and how I can overcome it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
First, thank you for providing the cross-compilation toolchain. I’ve successfully used it to compile and run an x86_64-linux version of my program. However, when I attempted to compile the arm-linux version and run it, the device displayed a "kernel too old" message. I suspect this is due to the newer versions of gcc, glibc, etc., in the cross-compilation toolchain you provided. Therefore, I plan to use crosstool-ng to build a new cross-compilation toolchain.
I’m attempting to build a cross-compilation toolchain using crosstool-ng on macOS, but I’ve encountered an error during the process. Specifically, the build fails at the step where it’s installing m4 for the build. The error message indicates an issue with the execution of make during the m4 installation step.
I’ve followed the official crosstool-ng documentation, ensuring all dependencies are installed and environment variables configured, but the error persists. Here’s the relevant part of the error log:
I’ve already consulted the known issues list at crosstool-ng known issues but couldn’t find a solution that applies to my case.
Has anyone experienced a similar issue or have any suggestions on how to resolve this? I would greatly appreciate any guidance on what might be causing this error and how I can overcome it.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions