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

[bug] unresolved external symbols in *-mingw32 .a #81

Open
xanimo opened this issue Oct 4, 2022 · 1 comment
Open

[bug] unresolved external symbols in *-mingw32 .a #81

xanimo opened this issue Oct 4, 2022 · 1 comment

Comments

@xanimo
Copy link
Member

xanimo commented Oct 4, 2022

Bug Report

Current behavior:
When building the python wrapper manually and only when targeting native windows I've had to use a work around that combines the missing linked libs to address the following error:

https://gist.github.com/xanimo/e5c306da8b83a6ee1caa9da8b2110012

Expected behavior
Not have unresolved external symbols in libdogecoin.a.

Steps to reproduce:
Will post a script that will automate the failure shortly. Note this is to be performed on Windows with VS build tools and Windows SDK installed.

libdogecoin commit
Both 0.1.1-dev and 0.2.0-dev contain this bug.

@xanimo
Copy link
Member Author

xanimo commented Oct 4, 2022

Steps to repro are install VS build tools, Windows SDK on Windows and clone and checkout mingw32-failure branch from the following repo: https://github.com/xanimo/python-libdogecoin

Then run bin/init --arch=amd64 and you'll see that since the missing libs are not being linked to the corresponding libdogecoin.a for mingw32, the python wheel compilation will fail and show the unresolved external symbols as seen in the gist above.

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