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 error on x64-linux #43820

Open
Ninoh-FOX opened this issue Feb 13, 2025 · 2 comments
Open

[libusb] Build error on x64-linux #43820

Ninoh-FOX opened this issue Feb 13, 2025 · 2 comments
Assignees
Labels
category:question This issue is a question

Comments

@Ninoh-FOX
Copy link

Ninoh-FOX commented Feb 13, 2025

Copy issue body from /home/ninoh-fox/vcpkg/installed/vcpkg/issue_body.md

ninoh-fox@debian:~/vcpkg$ sudo apt list libusb* | grep instalado

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libusb-0.1-4/stable,now 2:0.1.12-32 amd64 [instalado, automático]
libusb-1.0-0-dev/stable,now 2:1.0.26-1 amd64 [instalado]
libusb-1.0-0-dev/stable,now 2:1.0.26-1 i386 [instalado]
libusb-1.0-0/stable,now 2:1.0.26-1 amd64 [instalado]
libusb-1.0-0/stable,now 2:1.0.26-1 i386 [instalado, automático]
libusb-1.0-doc/stable,stable,now 2:1.0.26-1 all [instalado, automático]
libusb-dev/stable,now 2:0.1.12-32 amd64 [instalado]
libusbmuxd6/stable,now 2.0.2-3 amd64 [instalado, automático]
libusbredirparser1/stable,now 0.13.0-2 amd64 [instalado, automático]

ninoh-fox@debian:~/vcpkg$ sudo apt list libudev* | grep instalado

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libudev-dev/stable,now 252.33-1~deb12u1 amd64 [instalado]
libudev-dev/stable,now 252.33-1~deb12u1 i386 [instalado]
libudev1/stable,now 252.33-1~deb12u1 amd64 [instalado]
libudev1/stable,now 252.33-1~deb12u1 i386 [instalado, automático]

ninoh-fox@debian:/$ sudo apt list *autoreconf*
Listando... Hecho
dh-autoreconf/stable,stable,now 20 all [instalado, automático]

ninoh-fox@debian:~/vcpkg$ ./vcpkg install libusb
Computing installation plan...
The following packages will be built and installed:
    libusb[core,udev]:[email protected]#2
Detecting compiler hash for triplet x64-linux...
Compiler found: /usr/bin/c++
Restored 0 package(s) from /home/ninoh-fox/.cache/vcpkg/archives in 3.48 us. Use --debug to see more details.
Installing 1/1 libusb[core,udev]:[email protected]#2...
Building libusb[core,udev]:[email protected]#2...
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/ninoh-fox/vcpkg/buildtrees/libusb/src/v1.0.27-b8650a8dbc.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/ninoh-fox/vcpkg/downloads/libusb-libusb-v1.0.27.tar.gz
-- Using source at /home/ninoh-fox/vcpkg/buildtrees/libusb/src/v1.0.27-b8650a8dbc.clean
-- Found external ninja('1.12.2').
-- 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: /home/ninoh-fox/vcpkg/buildtrees/libusb/src/v1.0.27-b8650a8dbc.clean/
    Error code: 1
    See logs for more information:
      /home/ninoh-fox/vcpkg/buildtrees/libusb/autoconf-x64-linux-err.log

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


error: building libusb:x64-linux failed with: BUILD_FAILED
See https://learn.microsoft.com/vcpkg/troubleshoot/build-failures?WT.mc_id=vcpkg_inproduct_cli for more information.
Elapsed time to handle libusb:x64-linux: 2.5 s
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
  https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+libusb
You can submit a new issue at:
  https://github.com/microsoft/vcpkg/issues/new?title=[libusb]+Build+error+on+x64-linux&body=Copy%20issue%20body%20from%20%2Fhome%2Fninoh-fox%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

ninoh-fox@debian:~/vcpkg$ cat /home/ninoh-fox/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
ninoh-fox@debian:~/vcpkg$ 

```
`
@JonLiu1993
Copy link
Member

Please try install the necessary tools and libraries and try again.

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

@JonLiu1993 JonLiu1993 added the category:question This issue is a question label Feb 14, 2025
@Ninoh-FOX
Copy link
Author

As you can see in my first message I show that the required packages are installed, but it still doesn't work.

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