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

[libusb] Build failure on x64-linux #38648

Open
eugeniowalters opened this issue May 9, 2024 · 1 comment
Open

[libusb] Build failure on x64-linux #38648

eugeniowalters opened this issue May 9, 2024 · 1 comment
Assignees
Labels
category:question This issue is a question

Comments

@eugeniowalters
Copy link

Package: libusb[core,udev]:x64-linux@1.0.27#1

Host Environment

  • Host: x64-linux
  • Compiler: GNU 11.4.0
  • vcpkg-tool version: 2024-04-23-d6945642ee5c3076addd1a42c331bbf4cfc97457
    vcpkg-scripts version: 77b0517 2024-05-08 (2 hours ago)

To Reproduce

vcpkg install realsense2

Failure logs

libusb currently requires the following tools and libraries from the system package manager:
    autoreconf
    libudev

These can be installed on Ubuntu systems via apt-get install autoconf libudev-dev
-- Using cached libusb-libusb-v1.0.27.tar.gz.
-- Cleaning sources at /home/devbox/Documents/librealsense/vcpkg/buildtrees/libusb/src/v1.0.27-b8650a8dbc.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/devbox/Documents/librealsense/vcpkg/downloads/libusb-libusb-v1.0.27.tar.gz
-- Using source at /home/devbox/Documents/librealsense/vcpkg/buildtrees/libusb/src/v1.0.27-b8650a8dbc.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:112 (message):
    Command failed: /usr/bin/autoreconf -vfi
    Working Directory: /home/devbox/Documents/librealsense/vcpkg/buildtrees/libusb/src/v1.0.27-b8650a8dbc.clean/
    Error code: 1
    See logs for more information:
      /home/devbox/Documents/librealsense/vcpkg/buildtrees/libusb/autoconf-x64-linux-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:728 (vcpkg_execute_required_process)
  ports/libusb/portfile.cmake:54 (vcpkg_configure_make)
  scripts/ports.cmake:175 (include)



/home/devbox/Documents/librealsense/vcpkg/buildtrees/libusb/autoconf-x64-linux-err.log
autoreconf: export WARNINGS=
autoreconf: Entering directory '.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
aclocal: warning: couldn't open directory 'm4': No such file or directory
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: configure.ac: not using Intltool
autoreconf: configure.ac: not using Gtkdoc
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:23: installing './compile'
configure.ac:26: installing './install-sh'
configure.ac:26: installing './missing'
Makefile.am: installing './INSTALL'
examples/Makefile.am: installing './depcomp'
libusb/Makefile.am:6: error: Libtool library used but 'LIBTOOL' is undefined
libusb/Makefile.am:6:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
libusb/Makefile.am:6:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
libusb/Makefile.am:6:   If 'LT_INIT' is in 'configure.ac', make sure
libusb/Makefile.am:6:   its definition is in aclocal's search path.
parallel-tests: installing './test-driver'
autoreconf: error: automake failed with exit status: 1
@WangWeiLin-MV WangWeiLin-MV added the category:question This issue is a question label May 9, 2024
@WangWeiLin-MV
Copy link
Contributor

libusb currently requires the following tools and libraries from the system package manager:
autoreconf
libudev

These can be installed on Ubuntu systems via apt-get install autoconf libudev-dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:question This issue is a question
Projects
None yet
Development

No branches or pull requests

2 participants