Niels Sascha Reedijk

The vanilla code in clang/lib/Driver/Toolchains/Haiku.cpp is: ``` void Haiku::addLibStdCxxIncludePaths(const llvm::opt::ArgList &DriverArgs, llvm::opt::ArgStringList &CC1Args) const { addLibStdCXXIncludePaths(getDriver().SysRoot + "/system/develop/headers/c++", getTriple().str(), "", DriverArgs, CC1Args); } ``` Based on the original patch, this...

I like the idea, but I think there is one step missing, which is actually 'binding' to the native API. This either means automatically generate bindings to the C++ API...

I do not have any particular feedback on this tool or whether it should be included in `haikuporter`. It makes sense to me though, to help automate packaging software that...

Thank you for all the information. I hope it is possible to divide the recipe file up into two sections, one that we expect a recipe-writer to manually change, and...

> @nielx is that also true of the Application Kit part as well? Would it make sense to use bindgen for the other kits in a separate lib (like this...

+1 for the content, though I wonder if this happens/will happen often enough to get its own segment, or whether (for now) this particular announcement should just be a news...

Could it be that a static libgcc is linked in somewhere? The issue smells a bit like this issue and the comment about dwarf unwinding pitfalls: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105507#c5

@jackburton79 You are correct. And to be even more absolutist, libroot.so depends on libgcc_s.so, so nothing build and run on Haiku can ever include the static libgcc. @waddlesplash asked earlier...

Looks like bumping `tempfile` to 3.7.1 should work: https://github.com/Stebalien/tempfile/commit/bf8f7ea4362894f572935ea730a271378d7277f2