-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac M1: dyld: could not load inserted library #109
Comments
Thanks for reporting this. The error message on Ubuntu ARM is expected. CodeQL only supports arm64 for OSX at the moment. We tried the 2.7.6 version of CodeQL on macOS 12 (Monterey) with a simple mvn build and things work fine. Perhaps the way we generate the universal binary somehow does not work on macOS: Big Sur (11.6) . To debug things further, could you:
|
% codeql version
CodeQL command-line toolchain release 2.7.6.
Copyright (C) 2019-2022 GitHub, Inc.
Unpacked in: /Users/admin/Documents/codeql-home/codeql
Analysis results depend critically on separately distributed query and
extractor modules. To list modules that are visible to the toolchain,
use 'codeql resolve qlpacks' and 'codeql resolve languages'.
% file /Users/admin/Documents/codeql-home/codeql/tools/osx64/libtrace.dylib
/Users/admin/Documents/codeql-home/codeql/tools/osx64/libtrace.dylib: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm64:Mach-O 64-bit dynamically linked shared library arm64]
/Users/admin/Documents/codeql-home/codeql/tools/osx64/libtrace.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
/Users/admin/Documents/codeql-home/codeql/tools/osx64/libtrace.dylib (for architecture arm64): Mach-O 64-bit dynamically linked shared library arm64
|
Many thanks for the detailed report. I'll pass this on to the team. |
@aibaars Is this problem solved? |
Hello,
When I use CodeQL to create database, I got following error:
Version:
I changed CodeQL to Ubuntu ARM64 virtual machine (Using UTM), then the error changed to:
java: Exec format error
And then I use an old macbook, finally success.
So I think the problem is M1. Can I do something to resolve this problem?
The text was updated successfully, but these errors were encountered: