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

Build with GHC 9.4.2 on llvm-15 branch, and adapt to LLVM-15. #411

Merged
merged 1 commit into from
Mar 3, 2023

Conversation

sighingnow
Copy link

The "build with GHC 9.4.2" part is the same as #410.

See llvm/llvm-project@962a247 (which is included afterwords LLVM-14) for the jitlink::InProcessMemoryManager API changes.

Tested on windows with MSYS2.

Signed-off-by: Tao He <sighingnow@gmail.com>
@tmcdonell
Copy link
Member

Thanks!

How are you building/testing on windows? Would it be easy to add to the (new) CI? The version of llvm on the runner (via Chocolaty) doesn't include the llvm-config executable so we can't build using that, and I'm not sure where else to get packages on windows.

@tmcdonell
Copy link
Member

tmcdonell commented Mar 4, 2023

I made some progress building with msys2, but get undefined symbol errors linking the test executables. Have you encountered this problem before?

Edit: example

@sighingnow
Copy link
Author

but get undefined symbol errors linking the test executables. Have you encountered this problem before?

No such error. Actually, I'm working in a very non-standard environment where I remove the bundled MinGW in ghc and mklink /D the $MSYS/clang64 to the ghc/mingw location, and removed all explicit extra-libraries: c++ from my dependencies.

With bundled MinGW, I meet some other linker errors like ld.lld: error: -exclude-symbols:__clang_call_terminate is not allowed in .drectve so I have given up and turns to MSYS's clang64 environment at the very beginning.

@tmcdonell
Copy link
Member

Linking seems to work with the clang64 environment, although the tests fail with a (presumably) null pointer dereference. This could be the same reason the tests fail on macOS though, so I think it's actually working now. Thanks!

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

Successfully merging this pull request may close these issues.

None yet

2 participants