libyal/libewf

git clone and cd libewf

zdavatz opened this issue · 6 comments

zdavatz commented
  1. this works: git clone https://github.com/libyal/libewf.git
  2. this works: cd libewf/
  3. this does not work: ./synclibs.sh
  4. this does not work: ./autogen.sh
  5. latest-screenshot
joachimmetz commented

@zdavatz if you're not a developer this method of building the source is not for you. The scripts work fine, since they are run as part of the CI tests. Use the source distribution package as recommended on https://github.com/libyal/libewf/wiki/Building#read-first instead

This is an issue related to your build environment, marking as invalid

  • 👍1
zdavatz commented

this worked now: ./synclibs.sh

but it seems that my Orcale Linux has an old version of gettext:

autoreconf: autopoint failed with exit status: 1
[opc@free libewf]$ sudo yum install gettext
Failed to set locale, defaulting to C.UTF-8
Letzte Prüfung auf abgelaufene Metadaten: vor 3:59:18 am Thu Mar 16 04:53:15 2023.
Das Paket gettext-0.19.8.1-17.el8.x86_64 ist bereits installiert.
Abhängigkeiten sind aufgelöst.
Nichts zu tun.
Fertig.
joachimmetz commented

Stick with the source distribution package. If you're not directly developing libewf there is no reason to use git clone

  • ❤️1
zdavatz commented

In my view using git clone should be the easiest way to build any project including yours. It is how I build the Linux kernel. Why are you recommending not to use the libewf package via yum install? What is wrong with that?

joachimmetz commented

Why are you recommending not to use the libewf package via yum install?

you don't seem to understand the ecosystem, I have no control over what get's distributed via "yum", this also is distro dependent.

joachimmetz commented

In my view using git clone should be the easiest way to build any project including yours.

This project assumes that you have a fair bit of understanding of how to build from source to do so and are able to resolve basic issues in the build environment yourself.

Also HEAD is in-development, so you would need to be comfortable making code changes.