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

Using meson instead of autoconf #40

Open
gonzoleeman opened this issue Sep 4, 2022 · 7 comments
Open

Using meson instead of autoconf #40

gonzoleeman opened this issue Sep 4, 2022 · 7 comments

Comments

@gonzoleeman
Copy link
Collaborator

See pull request #39

Migrating to meson from autoconf. Please speak up if you have any issues.

@gonzoleeman
Copy link
Collaborator Author

My plan is to tag a new version once this is in place.

I'm actually thinking about upping the version number to 1.1

@hilaolu
Copy link

hilaolu commented Sep 13, 2022

+1
I am trying to port open-isns to RISC-V architecture. However, config.ac seems to be too old to identify RISC-V as target.

This script, last modified 2005-05-27, has failed to recognize
the operating system you are using. It is advised that you
...
configure: error: cannot guess build type; you must specify one

Migrating to meson may help.

@gonzoleeman
Copy link
Collaborator Author

+1 I am trying to port open-isns to RISC-V architecture. However, config.ac seems to be too old to identify RISC-V as target.

This script, last modified 2005-05-27, has failed to recognize
the operating system you are using. It is advised that you
...
configure: error: cannot guess build type; you must specify one

Migrating to meson may help.

Interesting.

Have you tried it yet? I did find internet references for cross-compiling for risc-v using meson: link here. But nothing about just building on risc-v.

@eli-schwartz
Copy link

AFAIK Meson should work fine on risc-v, e.g.Debian builds a wide variety of Meson-based software on their risc-v port.

@hilaolu
Copy link

hilaolu commented Sep 21, 2022

+1 I am trying to port open-isns to RISC-V architecture. However, config.ac seems to be too old to identify RISC-V as target.

This script, last modified 2005-05-27, has failed to recognize
the operating system you are using. It is advised that you
...
configure: error: cannot guess build type; you must specify one

Migrating to meson may help.

Interesting.

Have you tried it yet? I did find internet references for cross-compiling for risc-v using meson: link here. But nothing about just building on risc-v.

It builds just by running autoreconf -fi on build host(riscv64gc) to update config.ac.

@hilaolu
Copy link

hilaolu commented Oct 3, 2022

It now builds painlessly with meson on RISC-V, thanks.

@gonzoleeman
Copy link
Collaborator Author

gonzoleeman commented Oct 3, 2022 via email

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