Replies: 7 comments 28 replies
-
|
First attempt at build failed with: compiling src/remote-stub.c...
linking make...
done.
ninja: build stopped: subcommand failed.
mds@ravynosbuild:~/test_sdk/Developer/Platforms/ravynos-SDK_0.7.0.0$ |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Build vm is Ubuntu Server 25.10 Used these commands: |
Beta Was this translation helpful? Give feedback.
-
|
Oh. Try this: mkdir -p test_sdk/Developer/Platforms I think it's failing because you set the build root as the SDK. The SDK should be inside the build root. |
Beta Was this translation helpful? Give feedback.
-
|
I found that Developer/ravynOS.sdk/CMakeLists.txt had the "sh" instead of "bash" issue again. I fixed that and ran it again and it is still grinding away. I'm going to wait and see how it finishes. |
Beta Was this translation helpful? Give feedback.
-
|
Oops, did I revert your PR with one of my commits? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
My second build attempt took much longer as I simply fixed the bash thing and just ran the config/build thing again without cleaning. Then I implemented your recommendation and it was back to the quick fail at the same place. |
Beta Was this translation helpful? Give feedback.
-
|
Ah. Another stupid build ordering issue. Dependencies seem really complex to manage in CMake compared to bmake. Try this: ninja -C BootstrapTools It is trying to use tools to compile liblaunch before they're built. I'll add a dependency rule. |
Beta Was this translation helpful? Give feedback.
6 replies
-
|
BootstrapTools is a target, not a directory. You want to either cd to your build dir and run "ninja BootstrapTools" to build the target, or add "-C builddir" to that command if you don't change dir first. |
Beta Was this translation helpful? Give feedback.
-
|
LOL, I see where you got that bad command. Sorry :) I must have been typing something and got distracted. That should have read |
Beta Was this translation helpful? Give feedback.
-
|
Ok, it's grinding away now |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
that is the finish of the BootstrapTools target |
Beta Was this translation helpful? Give feedback.
-
|
Is your libtapi.so library somewhere in the output directory? Looks like it is missing. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
time ninja -C test_sdk BootstrapTools 2>&1 | tee BootstrapTools2nd.log` |
Beta Was this translation helpful? Give feedback.
-
|
Hmm... that's weird. The linker is complaining about unresolved tapi:: symbols, so there's something it does not like about libtapi or it can't be found. Make sure it's an ELF shared lib and not MachO. Make sure your SDKROOT env var is not set for a full OS build. |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
this would indicate missing parts of Apple's interfaces then, would it not? probably an ordering issue if those are expected. |
Beta Was this translation helpful? Give feedback.
-
|
time ninja -C test_sdk BootstrapTools 2>&1 | tee BootstrapTools2nd.log` |
Beta Was this translation helpful? Give feedback.
-
|
way past this old man's bedtime, nite |
Beta Was this translation helpful? Give feedback.
-
|
Same issue. |
Beta Was this translation helpful? Give feedback.
-
|
I just thought of something. Is your /usr/bin/ld the GNU linker or the LLVM one (ld.lld)? If it is GNU's, try the LLVM one. This build needs the clang toolchain. |
Beta Was this translation helpful? Give feedback.
-
|
BINGO! /usr/bin/ld was pointed to the GNU linker. I removed that symlink and created it's replacement to point to LLVM. And I changed the default shell while I was there. It certainly changes things, now it breaks somewhere else. I started with a clean slate; removed the test_sdk directory and started over. |
Beta Was this translation helpful? Give feedback.
9 replies
-
|
Logs from last build after resolving libdispatch issues. |
Beta Was this translation helpful? Give feedback.
-
It seems to be missing some symbols. No idea why. This is just Apple's LLVM branch, and it's part of clang that failed. You could try deleting the folder containing IndexStore.cpp.o (or whatever the filename is) and see if the clean build helps. |
Beta Was this translation helpful? Give feedback.
-
|
This was a clean build. I started by removing test_sdk directory and then extracting the sdk source into a newly created directory. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
side-note: take care with linking /usr/include on linux, as linux typically want's |
Beta Was this translation helpful? Give feedback.
-
From link above |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This package provides the headers, libraries, and frameworks needed to build ravynOS applications. It is the ravynOS equivalent to Apple's MacOSX.sdk and can be used from any host system that has a suitable
.xctoolchainbundle orclanginstall capable of cross-compiling to Darwin.This is not complete! While we do have a substantial part of libSystem, System.framework, IOKit, and DriverKit, parts of libSystem are still missing. Notably, libnotify, libinfo, corecrypto, and some others are missing. ObjC is here, along with XPC, liblaunch, dispatch (GCD) and others. No Frameworks yet other than System and Kernel. See the
ravynOS_SDK_0.7.0.0.manifestfile for full info.All code contained in these SDKs is fully open. No Apple proprietary tools or source was used to create them.
How to use the SDK
The SDK archive includes the
ravynOS.platformbundle as well, with the SDK inside it. There are two ways to use it./Library/Developer/Platformsand you should create a symlinkMacOSX.platformtoravynOS.platformfor best compatibility. However, you can put it wherever you prefer if you don't need to emulate a Mac build environment. Set the env varSDKROOT=<unpack_root>/ravynOS.platform/Developer/SDKs/ravynOS.sdkand build for the target<cpu>-apple-darwin.<build_root>/Developer/Platforms. Unset theSDKROOTenv var if set. Now build the system, which will produce an updated SDK in place.How to use the KDK
The KDK provides you with a prebuilt x86-64
xnukernel image and debugging symbols, kernel header exports, lists of supported KPIs,libkmod, and kernel extension (.kext) bundles to be linked into the kernelcache. You can use this KDK to play with the booter, build kernel extensions. and debug.Unpack it anywhere you like, verify the SHA256 sum, and have fun.
This one was manually assembled; the final KDK is subject to change 😄
This discussion was created from the release ravynOS SDK and KDK v0.7.0.0 (x86_64).
Beta Was this translation helpful? Give feedback.
All reactions