Skip to content

[compatibility] Linux: Selecting the correct libusb version #113

Closed

Description

@pthomas

This started as an issue, but the fix is easy so I figured I'd post it here because I don't know where it should go.

In Fedora there are 2 libusb versions, libusb and libusb1. stlink depends on libusb1 so Fedora users (and possibly other distros) just need to install that, 'yum install libusb1-devel', and then stlink should compile fine.

For all you googlers the error if you just have libusb is:
checking for USB... no
configure: error: *** Required libusb-1.0 >= 1.0.0 not installed ***

thanks,
Paul

Activity

  1. added this to the v1.6.1 milestone on Feb 25, 2020
  2. deleted a comment from xor-gate on Mar 22, 2020
  3. Nightwalker-87 commented on Mar 22, 2020

    @Nightwalker-87
    Member

    Related to #211 and #782.

  4. 2 remaining items

  5. changed the title [-]Fedora Linux: Selecting the correct libusb version[/-] [+]Linux: Selecting the correct libusb version[/+] on Mar 23, 2020
  6. Nightwalker-87 commented on Mar 23, 2020

    @Nightwalker-87
    Member

    As of today this also applies to several linux/unix distributions namely:

    • CentOS 6, 7, 8
    • Debian 8, 9, 10, sid
    • Fedora 30, 31, Rawhide
    • NetBSD 7.2, 8.1, 9.0
    • openSUSE Leap 15.1, Leap 15.2
    • Ubuntu 14.04 LTS, 16.04 LTS, 18.04 LTS, 19.10

    Other relevant distributions appear to have packages named libusb-compat-0.1 or alike to distinguish from libusb packages based on version 1.0.x.

  7. added a commit that references this issue on Mar 23, 2020
    10ae529
  8. Nightwalker-87 commented on Mar 23, 2020

    @Nightwalker-87
    Member

    Closed by 10ae529.

  9. linked a pull request that will close this issue[compatibility] update of libusb #895on Mar 26, 2020
  10. changed the title [-]Linux: Selecting the correct libusb version[/-] [+][compatibility] Linux: Selecting the correct libusb version[/+] on Mar 26, 2020
  11. added 2 commits that reference this issue on Mar 31, 2020
    566614a
    d211eff
  12. added a commit that references this issue on Apr 6, 2020
    aee2702
  13. locked as resolved and limited conversation to collaborators on Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions