nilfs-dev / nilfs-utils

NILFS utilities
https://nilfs.sourceforge.io/
Other
46 stars 6 forks source link

nilfs-utils' autoconf files are outdated #20

Closed moodyhunter closed 7 months ago

moodyhunter commented 2 years ago

Hello from the Arch Linux RISC-V Team, thanks for the great project.

When running ./configure on a RISC-V machine, it complains that:

This script, last modified 2013-06-10, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from

  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
and
  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD

If the version you run (./config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.

config.guess timestamp = 2013-06-10

uname -m = riscv64
uname -r = 5.18.6-arch1-1
uname -s = Linux
uname -v = #1 SMP PREEMPT_DYNAMIC Wed, 22 Jun 2022 18:10:56 +0000

/usr/bin/uname -p = unknown
/bin/uname -X     = 

hostinfo               = 
/bin/universe          = 
/usr/bin/arch -k       = 
/bin/arch              = 
/usr/bin/oslevel       = 
/usr/convex/getsysinfo = 

UNAME_MACHINE = riscv64
UNAME_RELEASE = 5.18.6-arch1-1
UNAME_SYSTEM  = Linux
UNAME_VERSION = #1 SMP PREEMPT_DYNAMIC Wed, 22 Jun 2022 18:10:56 +0000

Our current solution is to run autoreconf -fiv in our packaging script to get those files regenerated, but it's absolutely helpful if you can do this instead in the next release :)

konis commented 2 years ago

Thank you for your feedback!

The cause of the issue is that the machine environment used to create the nilfs-utils tarball is old and, as you reported, its autoconf is older than the one that supports RISC-V. I will update the packaging environment and fix this issue from the next release.

moodyhunter commented 2 years ago

Thanks!