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

Figure out how to portably link our C dependencies statically #1415

Closed
emberian opened this issue Jan 9, 2019 · 3 comments
Closed

Figure out how to portably link our C dependencies statically #1415

emberian opened this issue Jan 9, 2019 · 3 comments
Assignees
Labels
status-in-progress someone is currently working on this

Comments

@emberian
Copy link
Member

emberian commented Jan 9, 2019

Right now our build has substantial problems building on macOS because our dependencies assume the linker is GNU ld. On macOS the linker is not GNU ld. We need to be using -force_load on macOS, so that dlsym will see all the symbols we expect at runtime. -force_load takes a full path to a static library. There's also no equivalent to -Bstatic to make the linker consider static libraries before dynamic ones when trying to satisfy an -lfoo request.

@emberian emberian added category-enhancement status-in-progress someone is currently working on this labels Jan 9, 2019
@emberian emberian self-assigned this Jan 9, 2019
@emberian
Copy link
Member Author

emberian commented Jan 9, 2019

We can use Configurator (or, really, anything) to generate a flags.sexp that we then use with (link_flags (:include flags.sexp))

@emberian
Copy link
Member Author

Done in #1443 and #1433

@emberian
Copy link
Member Author

emberian commented Aug 6, 2020

we finished this!

@emberian emberian closed this as completed Aug 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status-in-progress someone is currently working on this
Projects
None yet
Development

No branches or pull requests

2 participants