Skip to content
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

Undefined symbols for architecture x86_64 when building FRUT on macos 11 #764

Closed
nperreau opened this issue Oct 6, 2023 · 1 comment · Fixed by #765
Closed

Undefined symbols for architecture x86_64 when building FRUT on macos 11 #764

nperreau opened this issue Oct 6, 2023 · 1 comment · Fixed by #765
Labels

Comments

@nperreau
Copy link

nperreau commented Oct 6, 2023

Hello, I am using FRUT with github actions to build a JUCE project when it is pushed.
However, when compiling Jucer2Cmake on a MacOS 11.7.10 runner with

cmake .. -DCMAKE_INSTALL_PREFIX="../prefix" -DJUCE_ROOT="/Users/runner/work//JUCE"
cmake --build . --target install --parallel

I get this linking error:

[ 65%] Linking CXX executable BinaryDataBuilder-0.3.1
Undefined symbols for architecture x86_64:
  "_SecCodeCopySelf", referenced from:
      juce::SystemStats::isAppSandboxEnabled()::$_23::operator()() const in libtools_juce_core.a(juce_core.mm.o)
  "_SecCodeCopySigningInformation", referenced from:
      juce::SystemStats::isAppSandboxEnabled()::$_23::operator()() const in libtools_juce_core.a(juce_core.mm.o)
  "_kSecCodeInfoEntitlementsDict", referenced from:
      juce::SystemStats::isAppSandboxEnabled()::$_23::operator()() const in libtools_juce_core.a(juce_core.mm.o)
ld: symbol(s) not found for architecture x86_64
Undefined symbols for architecture x86_64:
  "_SecCodeCopySelf", referenced from:
clang: error: linker command failed with exit code 1 (use -v to see invocation)
      juce::SystemStats::isAppSandboxEnabled()::$_23::operator()() const in libtools_juce_core.a(juce_core.mm.o)
  "_SecCodeCopySigningInformation", referenced from:
      juce::SystemStats::isAppSandboxEnabled()::$_23::operator()() const in libtools_juce_core.a(juce_core.mm.o)
make[2]: *** [cmake/tools/PListMerger/PListMerger-0.1.0] Error 1
make[1]: *** [cmake/tools/PListMerger/CMakeFiles/PListMerger.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
  "_kSecCodeInfoEntitlementsDict", referenced from:
      juce::SystemStats::isAppSandboxEnabled()::$_23::operator()() const in libtools_juce_core.a(juce_core.mm.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [cmake/tools/BinaryDataBuilder/BinaryDataBuilder-0.3.1] Error 1
make[1]: *** [cmake/tools/BinaryDataBuilder/CMakeFiles/BinaryDataBuilder.dir/all] Error 2
[ 68%] Linking CXX executable Jucer2CMake
Undefined symbols for architecture x86_64:
  "_SecCodeCopySelf", referenced from:
      juce::SystemStats::isAppSandboxEnabled()::$_23::operator()() const in libJucer2CMake_JUCE.a(juce_core.mm.o)
  "_SecCodeCopySigningInformation", referenced from:
      juce::SystemStats::isAppSandboxEnabled()::$_23::operator()() const in libJucer2CMake_JUCE.a(juce_core.mm.o)
  "_kSecCodeInfoEntitlementsDict", referenced from:
      juce::SystemStats::isAppSandboxEnabled()::$_23::operator()() const in libJucer2CMake_JUCE.a(juce_core.mm.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [Jucer2CMake/Jucer2CMake] Error 1
make[1]: *** [Jucer2CMake/CMakeFiles/Jucer2CMake.dir/all] Error 2

The C/C++ compiler is AppleClang 13.0.0.13000029, and the JUCE and FRUT repositories are cloned in the workflow.

@nperreau nperreau changed the title Undefined symbols for architecture x86_64 when builder FRUT on macos 11 Undefined symbols for architecture x86_64 when building FRUT on macos 11 Oct 6, 2023
@McMartin
Copy link
Owner

McMartin commented Oct 9, 2023

Hi @nperreau
Thank you very much for using FRUT and for opening this issue!
What you discovered is that FRUT doesn't build with JUCE 7.0.6 or newer. I'll working on fixing this as soon as possible, but in the meantime you can workaround this problem by using JUCE 7.0.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants