search

microsoft / vcpkg

C++ Library Manager for Windows, Linux, and MacOS
MIT License
23.15k stars 6.38k forks source link

[libmount] Build error on x64-linux #40370

Open SenthilDurai opened 2 months ago

SenthilDurai commented 2 months ago

Package: libmount:x64-linux@2.40

Host Environment

To Reproduce

vcpkg install opencv

Failure logs

-- Downloading https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/v2.40/util-linux-2.40.tar.xz -> util-linux-2.40.tar.xz...
-- Extracting source /mnt/d/Linux/vcpkg/downloads/util-linux-2.40.tar.xz
-- Applying patch hide-private-symbols.diff
-- Using source at /mnt/d/Linux/vcpkg/buildtrees/libmount/src/2.40-b5c733b07e.clean
-- Getting CMake variables for x64-linux-dbg
-- Getting CMake variables for x64-linux-rel
CMake Error at scripts/cmake/vcpkg_configure_make.cmake:721 (message):
  libmount requires autoconf from the system package manager (example: "sudo
  apt-get install autoconf")
Call Stack (most recent call first):
  ports/libmount/portfile.cmake:25 (vcpkg_configure_make)
  scripts/ports.cmake:192 (include)
FrankXie05 commented 2 months ago

@SenthilDurai Thanks for posting this issue, please run command sudo apt-get install autoconf and try again.

SenthilDurai commented 2 months ago

Thanks @FrankXie05 for your advise but still getting the error: The issue log as follows:

Package: libmount:x64-linux@2.40

Host Environment

To Reproduce

vcpkg install opencv

Failure logs

-- Using cached util-linux-2.40.tar.xz.
-- Cleaning sources at /mnt/d/Linux/vcpkg/buildtrees/libmount/src/2.40-b5c733b07e.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /mnt/d/Linux/vcpkg/downloads/util-linux-2.40.tar.xz
-- Applying patch hide-private-symbols.diff
-- Using source at /mnt/d/Linux/vcpkg/buildtrees/libmount/src/2.40-b5c733b07e.clean
-- Getting CMake variables for x64-linux-dbg
-- Getting CMake variables for x64-linux-rel
-- Generating configure for x64-linux
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
    Command failed: /usr/bin/autoreconf -vfi
    Working Directory: /mnt/d/Linux/vcpkg/buildtrees/libmount/src/2.40-b5c733b07e.clean/
    Error code: 1
    See logs for more information:
      /mnt/d/Linux/vcpkg/buildtrees/libmount/autoconf-x64-linux-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:731 (vcpkg_execute_required_process)
  ports/libmount/portfile.cmake:25 (vcpkg_configure_make)
  scripts/ports.cmake:192 (include)
/mnt/d/Linux/vcpkg/buildtrees/libmount/autoconf-x64-linux-err.log ``` autoreconf: Entering directory `.' autoreconf: running: true --force autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy --force Can't exec "libtoolize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 345, line 6. autoreconf: failed to run libtoolize: No such file or directory autoreconf: libtoolize is needed because this package uses Libtool ```
greenozon commented 2 months ago

The error message indicates that the libtoolize command is missing from your system. This is required because the package you're working with uses Libtool. To resolve this issue, you need to install the libtool package. You can do this by running the following command:

sudo apt-get install libtool

After installing libtool, try running the autoreconf command again. This should resolve the issue and allow the process to continue.

greenozon commented 2 months ago

Basically marjority Linux based libs needs these tools, just FYI:

sudo apt-get install autoconf automake libtool
foobra commented 2 months ago

Basically marjority Linux based libs needs these tools, just FYI:

sudo apt-get install autoconf automake libtool

I got same error after install these:

/usr/bin/ar: .libs/libblkid.lax/lt1-la-minix.o: No such file or directory make[2]: *** [Makefile:7956: libblkid.la] Error 1 make[1]: *** [Makefile:16921: all-recursive] Error 1 make: *** [Makefile:7280: all] Error 2

greenozon commented 2 months ago

@foobra could you provide more context please

foobra commented 2 months ago

@foobra could you provide more context please

  • what is the step you are running
  • what is your Linux distro
  • full error logs

cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS"

`./vcpkg install sdl2 Computing installation plan... The following packages will be built and installed:

`CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message): Command failed: /usr/bin/make V=1 -j 17 -f Makefile all Working Directory: /Users/jtang/Documents/Projects/Migu/MGYX/vcpkg-linux/buildtrees/libmount/x64-linux-dbg/ See logs for more information: /Users/jtang/Documents/Projects/Migu/MGYX/vcpkg-linux/buildtrees/libmount/build-x64-linux-dbg-out.log /Users/jtang/Documents/Projects/Migu/MGYX/vcpkg-linux/buildtrees/libmount/build-x64-linux-dbg-err.log

Call Stack (most recent call first): scripts/cmake/vcpkg_build_make.cmake:136 (vcpkg_execute_build_process) scripts/cmake/vcpkg_install_make.cmake:2 (vcpkg_build_make) ports/libmount/portfile.cmake:38 (vcpkg_install_make) scripts/ports.cmake:192 (include)`

build-x64-linux-dbg-out.log

error log /usr/bin/ar: .libs/libblkid.lax/lt1-la-minix.o: No such file or directory make[2]: *** [Makefile:7956: libblkid.la] Error 1 make[1]: *** [Makefile:16921: all-recursive] Error 1 make: *** [Makefile:7280: all] Error 2

btw, my linux distro is headless

dg0yt commented 2 months ago

error log /usr/bin/ar: .libs/libblkid.lax/lt1-la-minix.o: No such file or directory make[2]: *** [Makefile:7956: libblkid.la] Error 1 make[1]: *** [Makefile:16921: all-recursive] Error 1 make: *** [Makefile:7280: all] Error 2

The output log shows an attempt to create the file:

libtool: link: ln libblkid/src/superblocks/la-minix.o .libs/libblkid.lax/lt1-la-minix.o || cp libblkid/src/superblocks/la-minix.o .libs/libblkid.lax/lt1-la-minix.o

/mnt/d/

Maybe a WSL quirk? (Why run Ubuntu 20.04 in WSL - what else is outdated here?)

github-actions[bot] commented 1 month ago

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.