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

README build instructions omit details #80

Open
ChuckCottrill opened this issue May 1, 2023 · 4 comments
Open

README build instructions omit details #80

ChuckCottrill opened this issue May 1, 2023 · 4 comments

Comments

@ChuckCottrill
Copy link

The README build instructions specify using ./configure, but the repo does not contain the ./configure file.
I have tried

  • autoconf
    error: configure.ac:36: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.

  • autoreconf -i
    again, error: configure.ac:337: warning: macro 'AM_PATH_LIBGCRYPT' not found in library configure.ac:199: error: possibly undefined macro: AC_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:246: error: possibly undefined macro: AC_MSG_ERROR configure.ac:337: error: possibly undefined macro: AM_PATH_LIBGCRYPT configure.ac:342: error: possibly undefined macro: AC_MSG_WARN autoreconf: /usr/bin/autoconf failed with exit status: 1

@ChuckCottrill ChuckCottrill changed the title README build instructions not README build instructions omit details May 1, 2023
@ChuckCottrill
Copy link
Author

There is another issue closed in Nov 2022 that cited the same problem.
have tried autoconf, autoreconf, and now autogen.sh

  • autogen.sh
    configure.ac:199: error: possibly undefined macro: AC_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /usr/bin/autoconf failed with exit status: 1

error: possibly undefined macro: AC_PROG_LIBTOOL

@ChuckCottrill
Copy link
Author

It would be nice to have a list of packages that this depends upon, so that one can ensure all dependencies are installed prior to build.

@unsound
Copy link
Member

unsound commented Jun 18, 2023

To regenerate the build system you need autoconf, automake, libtool, pkg-config (or pkgconf) and libfuse / libgcrypt development files (e.g. libfuse-dev / libgcrypt-dev packages on Debian/Ubuntu).

@ShonkaiDJ
Copy link

ShonkaiDJ commented Dec 18, 2023

To 'make' (compile) and install the files offered as source files through the repository, firstly make sure you have the right environment to compile and create from source.

(On Ubuntu)
sudo apt install autoconf automake libtool pkgconf libgcrypt-dev libfuse-dev
sudo apt install libgcrypt20-doc

Run script:
./autogen.sh

Now ./configure and ./configure --help work as meant in the README file.

To fit my needs I added some options:
./configure --enable-extras --enable-posix-acls --enable-xattr-mappings

Next:
make

And finally:
sudo make install

will overwrite any pre-installed ntfs-3g modules. DO consider if you need the tools. The Windows tool 'ntfsusermap.exe' was not found to have been compiled through this extensive change!

NOTE: Trying to use the 'quick-install' instruction sent me on a 4,5 hour discovery tour though Linux universe. I ran into many interesting names, solutions and problems I will likely never need in my profession. I expect companions on this seemingly never ending trip to nowhere, to stumble upon this message in a bottle. I will express the hope for the future our information on Linux systems will improve as it did for a while since around 2017. "I will walk the fine line between time left in my projects and time wasted in the multiverse of Linux non-information, to add usefull, time-saving data". Sorry for the unintended column I ended up making here and in my recent issue in this thread.

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