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]: ARM64 compilation problems #32476

Closed
1 task done
alexanderguzhva opened this issue Apr 19, 2024 · 3 comments
Closed
1 task done

[Bug]: ARM64 compilation problems #32476

alexanderguzhva opened this issue Apr 19, 2024 · 3 comments
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@alexanderguzhva
Copy link
Contributor

alexanderguzhva commented Apr 19, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.4.0
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): Ubuntu
- CPU/Memory: 
- GPU: 
- Others: ARM

Current Behavior

  • scripts/install_deps.sh downloads cmake for x86 despite being run on ARM.

  • scripts/install_deps.sh does not install blas (libopenblas-dev is needed)

  • 'build/builder.sh make' fails with

ubuntu@ip-172-31-1-23:~/milvus$ build/builder.sh make
~/milvus ~/milvus
Pulling builder ... done
Creating milvus_builder_run ... done
exec /entrypoint.sh: exec format error

Expected Behavior

no compilation problems

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@alexanderguzhva alexanderguzhva added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 19, 2024
@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 22, 2024
@yanliang567
Copy link
Contributor

@alexanderguzhva are you going to make a pr for it?
/assign @alexanderguzhva

@alexanderguzhva
Copy link
Contributor Author

well, let me try, at least

@yanliang567 yanliang567 removed their assignment Apr 26, 2024
sre-ci-robot pushed a commit that referenced this issue May 22, 2024
…only (#32548)

issue #32476 

tested on x86_64 and aarch64. I'm not sure what needs to be done on some
exotic architectures.

Signed-off-by: Alexandr Guzhva <alexanderguzhva@gmail.com>
Copy link

stale bot commented May 27, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label May 27, 2024
sre-ci-robot pushed a commit that referenced this issue May 29, 2024
…atform, not x86_64 only (#33439)

issue #32476
pr: #32548
tested on x86_64 and aarch64. I'm not sure what needs to be done on some
exotic architectures.

Signed-off-by: Alexandr Guzhva <alexanderguzhva@gmail.com>
@stale stale bot closed this as completed Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants