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

gthr object files and runtime loading #158

Open
3246251196 opened this issue Mar 12, 2024 · 0 comments
Open

gthr object files and runtime loading #158

3246251196 opened this issue Mar 12, 2024 · 0 comments

Comments

@3246251196
Copy link
Contributor

3246251196 commented Mar 12, 2024

Hi, @sba1

So, the reason for creating gthr_amigaos_(native|single|pthread).o is so that at link time the user can choose which threading implementation to use via the -athread option. This is my first assertion. I am aware of: #128 , #115 and probably more.

I am finding the following issue with a port: During runtime a shared object is loaded via dlopen. This shared object, itself, relies on other shared objects - as is often the case. Eventually, the elf.library tries to resolve one of the symbols that are marked as UND (undefined, in the readelf -s output of libstdc++.so) which belong to gthr_amigaos_native.o and fails to do so.

Does this mean that I should also create a shared object version of gthr_amigaos_native.o (having compiled with -fPIC) and load that so that it can be resolved. Or, should I somehow read in gthr_amigaos_native.o, instead, so that I can load the function?

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

1 participant