Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 16
Like Tree1Likes
Hi, all. I have a problem with a program that uses libusb-0.1.so.4. Use Suse 12.1 64bit. ./usburn: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jul 2012
    Posts
    8

    Question libusb-0.1 problem


    Hi, all.

    I have a problem with a program that uses libusb-0.1.so.4.
    Use Suse 12.1 64bit.
    ./usburn: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory

  2. #2
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,346
    Hi and welcome,

    Behind the obvious (file not found) it means you try to run a program, that was not installed via the native package manager.
    So it would help, if you would give more context: What program are you trying to run, where did you get it and how did you install it?
    You must always face the curtain with a bow.

  3. #3
    Just Joined!
    Join Date
    Jul 2012
    Posts
    8

    Re

    Quote Originally Posted by Irithori View Post
    Hi and welcome,

    Behind the obvious (file not found) it means you try to run a program, that was not installed via the native package manager.
    So it would help, if you would give more context: What program are you trying to run, where did you get it and how did you install it?
    when I go to install libusb tells me that everything was installed successfully:
    Reading installed packages...
    'libusb' not found in package names. Trying capabilities.
    'libusb-0_1-4' providing 'libusb' is already installed.
    Resolving package dependencies...

    Nothing to do
    I try to run a programmer for microcontrollers: sprut.de/electronic/pic/projekte/brenner8/

  4. #4
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,346
    The executeable in that tar is made for an older distribution (debian 5).

    But the dependency requirements to compile a new one are rather low.
    On my fedora 17 I installed two addtional packages: "gcc-c++" and "libusb-devel".
    This was enough to build a new usburn executeable with "make" inside the usburn directory.

    I dont use suse, but the packages should be named similar there.
    You must always face the curtain with a bow.

  5. #5
    Just Joined!
    Join Date
    Jul 2012
    Posts
    8
    I install the required packages, but after run "make", get errors.

    g++ usburn.c programmer_usb.c database.c hexfile.c calibration.c firmware.c test.c -m32 -I/usr/local/include -L. -lnsl -lm -lc -L/usr/local/lib -lusb -o usburn
    In file included from /usr/include/features.h:382:0,
    from /usr/include/stdio.h:28,
    from usburn.c:33:
    /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
    compilation terminated.
    In file included from /usr/include/features.h:382:0,
    from /usr/include/stdio.h:28,
    from programmer_usb.c:34:
    /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
    compilation terminated.
    In file included from /usr/include/features.h:382:0,
    from /usr/include/stdio.h:28,
    from database.c:43:
    /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
    compilation terminated.
    In file included from /usr/include/features.h:382:0,
    from /usr/include/stdio.h:28,
    from hexfile.c:39:
    /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
    compilation terminated.
    In file included from /usr/include/features.h:382:0,
    from /usr/include/stdio.h:28,
    from calibration.c:30:
    /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
    compilation terminated.
    In file included from /usr/include/features.h:382:0,
    from /usr/include/stdio.h:28,
    from firmware.c:39:
    /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
    compilation terminated.
    In file included from /usr/include/features.h:382:0,
    from /usr/include/stdio.h:28,
    from test.c:36:
    /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
    compilation terminated.
    make: *** [all] Error 1

  6. #6
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,346
    gnu/stubs-32.h is part of the package "glibc-devel"
    Install it and try the compilation again.
    You must always face the curtain with a bow.

  7. #7
    Just Joined!
    Join Date
    Jul 2012
    Posts
    8
    'glibc-devel' is already installed.
    'glibc-devel' is already installed.
    No update candidate for 'glibc-devel-2.14.1-14.27.1.x86_64'. The highest available version is already installed.

  8. #8
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,346
    Then find out where this stubs-32.h is on your system and adjust the include path of usburnīs makefile accordingly.

    One time: "updatedb" to get an up to date index of your system files
    Then "locate stubs-32.h"

    On fedora, it is here:
    Code:
    locate stubs-32.h
    /usr/include/gnu/stubs-32.h
    And this file belongs to glibc-devel
    Code:
    rpm -qf /usr/include/gnu/stubs-32.h
    glibc-devel-2.15-37.fc17.i686
    But this might be different on suse.
    You must always face the curtain with a bow.

  9. #9
    Just Joined!
    Join Date
    Jul 2012
    Posts
    8
    How can I include "stubs-32.h" in the makefile. What is the exact syntax? sorry for stupid question.

  10. #10
    Just Joined!
    Join Date
    Jul 2012
    Posts
    8
    I can not find "stubs-32.h", but find "stubs-64.h". Could something to do with it?

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •