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

Support aarch64-unknown-linux-gnu target #63

Closed
waynexia opened this issue Jun 24, 2022 · 5 comments
Closed

Support aarch64-unknown-linux-gnu target #63

waynexia opened this issue Jun 24, 2022 · 5 comments
Labels
feature New feature or request

Comments

@waynexia
Copy link
Member

Description

Add support for aarch64-unknown-linux-gnu

Proposal

Support build on aarch64-unknown-linux-gnu first. Probably add a new CI job to cover this.

Running on this arch is planned but with a lower priority.

Additional context

@waynexia waynexia added the feature New feature or request label Jun 24, 2022
@zwpaper
Copy link
Contributor

zwpaper commented Jul 27, 2022

how can we confirm that a target is supported?

I have an aarch64 mac, I can build and run the CeresDB locally, and it seems that most of the functions work as expected besides an SST error log occurred.

I run the CRUD example on README, and get all the correct responses.

@ShiKaiWi
Copy link
Member

ShiKaiWi commented Jul 27, 2022

Maybe there are some issues caused by cross compiling to address if we choose to build CeresDB by github actions, e.g. apache/horaedb-client-py#20.

@waynexia
Copy link
Member Author

waynexia commented Jul 27, 2022

how can we confirm that a target is supported?

We need to ensure chip, runtime os and dev toolchain are supported. To list a target as "supported" I think there are two steps:

  • Have CI to prevent untested regression.
  • Have the capacity and willingness to solve problems on that target quickly.

But sadly we don't have these two conditions 😣 So the target is "maybe support", or in other words, is Tire-2 priority compared to amd64-linux

@zwpaper
Copy link
Contributor

zwpaper commented Jul 27, 2022

haha, of course, CeresDB should focus on the rapid development currently

@jiacai2050
Copy link
Contributor

Closing since this issue has been quiet for a while, free free to reopen if others have requirements depending on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants