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

Update config.guess to support riscv64 platform #715

Closed
A1ca7raz opened this issue Apr 10, 2023 · 5 comments
Closed

Update config.guess to support riscv64 platform #715

A1ca7raz opened this issue Apr 10, 2023 · 5 comments

Comments

@A1ca7raz
Copy link

A1ca7raz commented Apr 10, 2023

I am packaging this project for Arch Linux RISC-V and I noticed that config.guess script this projec use is too old to recognize riscv64 arch. This script should be updated to support riscv64 arch.
To update this script manually while packaging, I ran this command before run configure script:
autoreconf -fi && autoupdate -f
then this problem should be fixed.

Describe the bug

Config.guess cannot recognize riscv64 architecture.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • Application: [e.g. Steam, SDL, pulseaudio]
  • OS: [e.g. macOS, linux, windows] Arch Linux
  • Version [e.g. 3.1.12] 3.1.12

Additional context

@revmischa
Copy link
Collaborator

It would be very cool to have it running on RISC-V! Please submit a PR if you know what needs to be fixed. I think you are maybe not using the latest version with CMake though? Please try building 4.0.0+ or master with CMake.

@A1ca7raz
Copy link
Author

I found that the config.guess in the released 3.1.12 tarball is too old to recognize riscv32&riscv64 arch. Is it possible to repack v3.1.12?

@revmischa
Copy link
Collaborator

I found that the config.guess in the released 3.1.12 tarball is too old to recognize riscv32&riscv64 arch. Is it possible to repack v3.1.12?

There should be some way to do it with a local copy of a recent autoconf. But I would really suggest using cmake and the latest 4.x version instead.

@kblaschke
Copy link
Member

kblaschke commented Apr 12, 2023

I second Mischa's recommendation. Update packages to use the new 4.0 version and only provide these for previously unsupported architectures. Since projectM probably never worked there before, it might not break any existing applications, and since we've fixed tons of bugs, I don't see a good reason to ride a dead horse any further.

We'll also provide support to downstream developers as needed to update their integrations, and we expect 4.0 and newer versions of libprojectM to replace any 3.x version soon.

@kblaschke
Copy link
Member

Closing the issue, as we're not going to re-release the old version. With CMake, please use a proper toolchain file if needed, otherwise I'd expect it to work without any additional changes.

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

3 participants