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

🐛 Broken (dynamic) linking in CI builds #281

Closed
hacheigriega opened this issue Jun 12, 2024 · 1 comment
Closed

🐛 Broken (dynamic) linking in CI builds #281

hacheigriega opened this issue Jun 12, 2024 · 1 comment
Assignees
Labels
priority: critical Must be fixed immediately type: bug 🐛 Something isn't working

Comments

@hacheigriega
Copy link
Member

hacheigriega commented Jun 12, 2024

🐛 Bug Report

The introduction of the SEDA Tally VM is causing build failures in the CI. It is unclear why this is failing when this works fine in a local setting. It seems that the linker is not being directed to the correct location to search for the shared library file despite the CGO directive here.

# github.com/sedaprotocol/seda-chain/plugins/indexing
/home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.21.[10](https://github.com/sedaprotocol/seda-chain/actions/runs/9483366636/job/26130286122?pr=272#step:6:11).linux-amd64/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
/usr/bin/ld: cannot find -lseda_tally_vm: No such file or directory
collect2: error: ld returned 1 exit status

Note the shared libraries for linux do not exist yet in the Tally VM repo, so it is as expected that the linux builds are failing. The Darwin builds, however, should pass.

Debugging ld in linux environment gives (may not be helpful):

ld: mode aarch64linux
attempt to open /usr/aarch64-amazon-linux/lib64/libseda_tally_vm.so failed
attempt to open /usr/aarch64-amazon-linux/lib64/libseda_tally_vm.a failed
attempt to open /usr/lib64/libseda_tally_vm.so failed
attempt to open /usr/lib64/libseda_tally_vm.a failed
attempt to open /usr/local/lib64/libseda_tally_vm.so failed
attempt to open /usr/local/lib64/libseda_tally_vm.a failed
attempt to open /lib64/libseda_tally_vm.so failed
attempt to open /lib64/libseda_tally_vm.a failed
attempt to open /usr/aarch64-amazon-linux/lib/libseda_tally_vm.so failed
attempt to open /usr/aarch64-amazon-linux/lib/libseda_tally_vm.a failed
attempt to open /usr/local/lib/libseda_tally_vm.so failed
attempt to open /usr/local/lib/libseda_tally_vm.a failed
attempt to open /lib/libseda_tally_vm.so failed
attempt to open /lib/libseda_tally_vm.a failed
attempt to open /usr/lib/libseda_tally_vm.so failed
attempt to open /usr/lib/libseda_tally_vm.a failed
ld: cannot find -lseda_tally_vm: No such file or directory
attempt to open /usr/aarch64-amazon-linux/lib64/libseda_tally_vm.so failed
attempt to open /usr/aarch64-amazon-linux/lib64/seda_tally_vm.a failed
attempt to open /usr/lib64/libseda_tally_vm.so failed
attempt to open /usr/lib64/seda_tally_vm.a failed
attempt to open /usr/local/lib64/libseda_tally_vm.so failed
attempt to open /usr/local/lib64/seda_tally_vm.a failed
attempt to open /lib64/libseda_tally_vm.so failed
attempt to open /lib64/seda_tally_vm.a failed
attempt to open /usr/aarch64-amazon-linux/lib/libseda_tally_vm.so failed
attempt to open /usr/aarch64-amazon-linux/lib/seda_tally_vm.a failed
attempt to open /usr/local/lib/libseda_tally_vm.so failed
attempt to open /usr/local/lib/seda_tally_vm.a failed
attempt to open /lib/libseda_tally_vm.so failed
attempt to open /lib/seda_tally_vm.a failed
attempt to open /usr/lib/libseda_tally_vm.so failed
attempt to open /usr/lib/seda_tally_vm.a failed
@hacheigriega hacheigriega added the type: bug 🐛 Something isn't working label Jun 12, 2024
@hacheigriega hacheigriega self-assigned this Jun 12, 2024
@mariocao mariocao added the priority: critical Must be fixed immediately label Jun 13, 2024
@hacheigriega
Copy link
Member Author

hacheigriega commented Jun 21, 2024

Fixed in #272
We included the shared libraries built for various operating systems and architectures in the seda-wasm-vm repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: critical Must be fixed immediately type: bug 🐛 Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants