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

Could it be made that a dune utop works with this project? #20

Open
hannesm opened this issue Apr 5, 2022 · 1 comment
Open

Could it be made that a dune utop works with this project? #20

hannesm opened this issue Apr 5, 2022 · 1 comment

Comments

@hannesm
Copy link

hannesm commented Apr 5, 2022

Currently, a dune utop results in:

File "_build/default", line 1, characters 0-0:
ld: error: undefined symbol: caml_startup__code_begin
>>> referenced by owee_stubs.c:47
>>>               owee_stubs.o:(ml_owee_code_pointer) in archive src/libowee_stubs.a

ld: error: undefined symbol: caml_startup__code_end
>>> referenced by owee_stubs.c:47
>>>               owee_stubs.o:(ml_owee_code_pointer) in archive src/libowee_stubs.a
cc: error: linker command failed with exit code 1 (use -v to see invocation)
File "_none_", line 1:
Error: Error while building custom runtime system

Even for projects that depend on owee. It would be great to support bytecode targets, even if understandably owee woudn't work as expected. In the meantime we had to comment out the packages using owee to get an interactive session up and running.

@let-def
Copy link
Owner

let-def commented Apr 11, 2022

Thank you for reporting this issue. I had not thought of using Owee in bytecode before.
I see two steps to solve this problem properly:

  • splitting the core owee library (DWARF/ELF/manipulation), from the higher-level OCaml runtime introspection API.
  • implementing a bytecode code path for Owee_locate (as an alternative to Dynamically get code symbols #22)

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

No branches or pull requests

2 participants