| Summary: | sys-apps/usbutils-0.82: emerge fails; configure script can't find libusb via pkg-config | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andrew Evans <gentoo> |
| Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | andre, cnyegle, marduk, nelchael |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build log
See text virtual/libusb dependencies |
||
|
Description
Andrew Evans
2009-05-15 18:31:14 UTC
Created attachment 191408 [details]
build log
same problem here, but appplies also to media-libs/libgphoto2-2.4.4 emerge --sync and then "emerge virtual/libusb:0 virtual/libusb:1" There was a typo in the virtual/libusb-1 ebuild. Simply emerge --sync'ing and re-running revdep-rebuild (after rm'ing cache) fixed it. That did emerge --oneshot sys-apps/usbutils, which pulled in new =dev-libs/libusb-0.1.12-r5 and =virtual/libusb-0. So now I've got both libusb-0.1.12-r5 (again) and libusb-1.0.1. Thanks for the quick fix! revdep-rebuild is not required. You should have libusb-compat and libusb-1, which together are mutually exclusive with libusb-0. Portage should NOT have let you install dev-libs/libusb-0* and libusb-compat at the same time. I simply ran revdep-rebuild as that was how I discovered this in the first place. It was just a means to remerge usbutils. I still don't have libusb-compat: $ ls -ld /var/db/pkg/*/*usb* drwxr-xr-x 2 root root 808 2009-05-15 15:44 /var/db/pkg/dev-libs/libusb-0.1.12-r5 drwxr-xr-x 2 root root 728 2009-05-14 22:56 /var/db/pkg/dev-libs/libusb-1.0.1 drwxr-xr-x 2 root root 752 2009-05-15 15:44 /var/db/pkg/sys-apps/usbutils-0.82 drwxr-xr-x 2 root root 616 2009-05-15 15:44 /var/db/pkg/virtual/libusb-0 Is that a problem? Andrew Evans: Can you please show me the output of: 1. emerge -pv virtual/libusb:0 2. emerge -epv virtual/libusb:0 As it stands with that output, the dependencies of virtual/libusb-0 are not fulfilled at all. My situation is similar but not the same. I also discovered this bug by emerge --sync emerge --depclean revdep-rebuild A few hours later, after another emerge --sync virtual/libusb was pulled in, but this does not solve the problem. As mentioned before media-libs/libgphoto2 is also affected. the problem remains with me since I only have dev-libs/libusb-1.0.1 installed and not dev-libs/libusb-0.1.12-r5 like Andrew Evans. I have not yet opened a bug for libgphoto2 but will do so now. I'll also submit some more information shortly. I do have the libusb-1 but not libusb-compat: ZeusGentoo2 ~ # emerge -pv libusb These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-libs/libusb-1.0.1 USE="doc -debug" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB ZeusGentoo2 ~ # emerge -pv libusb-compat These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-libs/libusb-compat-0.1.0 USE="-debug" 244 kB Total: 1 package (1 new), Size of downloads: 244 kB ZeusGentoo2 ~ # The output of the commands in comment #7 will be attached. Created attachment 191443 [details]
See text
André Terpstra: 1. I'm not sure what that html attachment was. 2. Which slots of virtual/libusb do you have? There's lots of packages that need to flip to the virtual/libusb dep still. Created attachment 191449 [details]
virtual/libusb dependencies
(In reply to comment #11) > André Terpstra: > 1. I'm not sure what that html attachment was. > 2. Which slots of virtual/libusb do you have? > > There's lots of packages that need to flip to the virtual/libusb dep still. > I only have slot 1: ZeusGentoo2 ~ # emerge -pv virtual/libusb These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] virtual/libusb-1 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB Perhaps I should add the specific error message in my case: "... checking for x86_64-pc-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LIBUSB... configure: error: Package requirements (libusb >= 0.1.12) were not met: No package 'libusb' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables LIBUSB_CFLAGS and LIBUSB_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-apps/usbutils-0.82/work/usbutils-0.82/config.log * * ERROR: sys-apps/usbutils-0.82 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 191: Called econf '--datadir=/usr/share/misc' '--disable-zlib' * ebuild.sh, line 534: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/sys-apps:usbutils-0.82:20090516-073707.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/usbutils-0.82/temp/environment'. * >>> Failed to emerge sys-apps/usbutils-0.82, Log file: >>> '/var/log/portage/sys-apps:usbutils-0.82:20090516-073707.log' " André: # emerge -1v libusb-compat && emerge -1v =virtual/libusb-0 =virtual/libusb-1 You picked up the upgrade for a moment when the SLOT in virtual/libusb-1 had a typo. I already thought so. Since I already have slot 1 installed I did not re-emerge that one. I fail to understand why I have to manually emerge these packages, though. In my view everything should be controlled by the combination world file, profile and USE flags. Anyway, revdep-rebuild no longer complains no (no rebuilds necessary). No, you must remerge the virtual/libusb-1 ebuild, that's where the typo was (specifically, it accidentally declared SLOT=0 instead of SLOT=1). The other question however, is what on your system caused dev-libs/libusb-0* to be removed? An overzealous depclean maybe? Yes, like Andrew I did an emerge --depclean (as I do regularly as part of a system cleanup) after an ordinary emerge --sync. guess there doesnt need anything to be changed here |
