-
Notifications
You must be signed in to change notification settings - Fork 440
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
Building Magnum on Emscripten 2.0.17 to 2.0.24 fails with undefined symbol: malloc #507
Comments
Hi! Corrade was built and installed using the Magnum (and the toolchain both Corrade and Magnum use) then looks for |
Hi, thank you for the clues. I will try a fresh start and will report what kind of files I get. |
I got the .bc files. when running "sudo pacman -U emscripten-corrade-dev.wasm-1-any.pkg.tar.zst" i get some warnings: I will try to build magnum now |
Looks like some stale files from a manual install? :) To ensure you have a clean setup, I'd suggest manually removing the whole |
magnum finds corrade now -- Found Corrade: /usr/lib/emscripten/system/include found components: Containers rc Utility I think the problem was that I had some .so files in the emscripten/system folder. |
Yeah I was fighting hard :) |
I am getting another error [walde@localhost archlinux]$ makepkg --nocheck -fp PKGBUILD-emscripten-wasm |
Looks like some fancy new emscripten breakage (this happens all the time, unfortunately). What version are you on? Locally I'm on 2.0.10 and it works here -- can you try downgrading? Get a package from ArchLinux Archive, for example. I'll have to fix this of course, but a downgrade could be a temporary solution to unblock you. |
I am on 2.0.17. |
I was not able to get emscripten 2.0.10 running from arch aur. I will try to use emsdk to get to version 2.0.10. |
I was able to build magnum with emscripten 2.0.10 from emsdk. |
Keeping this open as a reminder to fix the build issue ;) FYI, here's older Emscripten versions (this is what I'm always doing, in case I upgrade and get a breakage and I have nothing in |
Even a year later I still don't have any better solution than just ignoring affected Emscripten versions -- after all, it's In my testing this started happening in 2.0.14 (probably due to emscripten-core/emscripten#13434), happened still in 2.0.24 and then mysteriously went away in 2.0.25. I went through the commit log between the two versions and found nothing even vaguely related, so I simply don't know. The only way to fix this on 2.0.14 to 2.0.24 is to supply |
Hi, when I compile magnum to wasm i get the error "Could NOT find Corrade (missing: Utility)".
I setup the toolchain file ("set(EMSCRIPTEN_PREFIX "/usr/lib/emscripten")")
and build corrade for wasm.
Then I execute
"makepkg -fp PKGBUILD-emscripten-wasm" in "/magnum/package/archlinux"
and get the output:
==> Making package: emscripten-magnum dev.wasm-1 (2021-05-26T00:44:21 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
==> Extracting sources...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
-- The CXX compiler identification is Clang 13.0.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/lib/emscripten/em++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at /usr/share/cmake-3.20/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find Corrade (missing: Utility)
Call Stack (most recent call first):
/usr/share/cmake-3.20/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
modules/FindCorrade.cmake:605 (find_package_handle_standard_args)
CMakeLists.txt:51 (find_package)
Configuring incomplete, errors occurred!
See also "/home/walde/aur/magnum/build-emscripten-wasm/CMakeFiles/CMakeOutput.log".
See also "/home/walde/aur/magnum/build-emscripten-wasm/CMakeFiles/CMakeError.log".
==> ERROR: A failure occurred in build().
Aborting...
/usr/lib/emscripten/system/lib" contains:
libCorradeInterconnect.so, libCorradePluginManager.so, libCorradeTestSuite.so, libCorradeUtility.so
The text was updated successfully, but these errors were encountered: