Re: [gentoo-user] libusb build error
OH God !!! Haven't updated Gentoo in a year ?? Wow... I think first thing you should do is to update portage. Bye, Rafael Fernández López. Hi, me again :) . I'm trying to update my machine. I have never done so since I installed Gentoo last year, so I'm a bit unexperienced and ignorant about portage and emerge usage. I have updated most of the packages manually to avoid a broken system, and most are done (only 98 left :) . Some packages don't install properly, this time it is libusb. I have installed libusb-0.1.8 and try to install libusb-0.1.10a, but I get the error message attached. Anyone a clue where I can start searching for a solution? Wrong automake version? A missing variable? Thx best regards ce emerge libusb Calculating dependencies ...done! emerge (1 of 1) dev-libs/libusb-0.1.10a to / md5 files ;-) libusb-0.1.7-r1.ebuild md5 files ;-) libusb-0.1.8.ebuild md5 files ;-) libusb-0.1.10a.ebuild md5 files ;-) files/digest-libusb-0.1.7-r1 md5 files ;-) files/0.1.10a-fbsd.patch md5 files ;-) files/digest-libusb-0.1.8 md5 files ;-) files/libusb-0.1.8-amd64-fPIC.patch md5 files ;-) files/digest-libusb-0.1.10a md5 src_uri ;-) libusb-0.1.10a.tar.gz Unpacking source... Unpacking libusb-0.1.10a.tar.gz to /var/tmp/portage/libusb-0.1.10a/work * Applying 0.1.10a-fbsd.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/libusb-0.1.10a/work/libusb-0.1.10a' ... * Running aclocal... [ ok ] * Running libtoolize --copy --force --automake... [ ok ] * Running aclocal... [ ok ] * Running autoconf... [ ok ] * Running autoheader... [ ok ] * Running automake --add-missing --copy --foreign... [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/libusb-0.1.10a/temp/automake-5879.out !!! ERROR: dev-libs/libusb-0.1.10a failed. !!! Function autotools_run_tool, Line 179, Exitcode 0 !!! Failed Running automake ! !!! If you need support, post the topmost build error, NOT this status message. -- gentoo-user@gentoo.org mailing list -- A la vista de suficientes ojos todos los errores resultan evidentes - Linus Torvalds -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] libusb build error
OH God !!! :) ? Haven't updated Gentoo in a year ?? Wow... I think first thing you should do is to update portage. Portage is updated, I even synced the local tree. I didn't say I didn't update anything during this year, but I only updated the packages I was interested in (mainly packages for audio work). It was a year without struggling with updated config files or any other unconvenient issues :-) . Anyway, most packages are up to date now. I still have installed kde 3.3, and I plan to update it to 3.5 as soon as it is marked as stable. Unfortunately, kdebase depends on libusb, and even CUPS has been updated and I cannot use my USB printer because CUPS complains about Unable to open USB device usb://hp/deskjet%205550: No such device though I don't know if this is a problem of updating CUPS or with libusb. Best regards ce -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] libusb build error
Hi all, I'd do: [*] emerge -vu portage [*] emerge -vuDp world [*] if everything went OK: emerge -vuD world [*] revdep-rebuild --pretend [*] revdep-rebuild so I did. Everything went fine, until it was libusb's turn. I still get: Unpacking source... Unpacking libusb-0.1.10a.tar.gz to /var/tmp/portage/libusb-0.1.10a/work * Applying 0.1.10a-fbsd.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/libusb-0.1.10a/work/libusb-0.1.10a' ... * Running aclocal ... [ ok ] * Running libtoolize --copy --force --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign ... [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/libusb-0.1.10a/temp/automake-12138.out !!! ERROR: dev-libs/libusb-0.1.10a failed. !!! Function autotools_run_tool, Line 179, Exitcode 0 = When I look into /var/tmp/portage/libusb-0.1.10a/temp/automake-12138.out it contains: * automake * configure.in: installing `./mkinstalldirs' libusbpp_la_LDFLAGS: variable `QT_LDFLAGS' is used but `QT_LDFLAGS' is undefined = A further issue I had before was that kdelibs didn't compile properly. It complained: grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la' is not a valid libtool archive make[3]: *** [libkio.la] Fehler 1 make[3]: Leaving directory `/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3/kio' make[2]: *** [all-recursive] Fehler 1 make[2]: Leaving directory `/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3/kio' make[1]: *** [all-recursive] Fehler 1 make[1]: Leaving directory `/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3' make: *** [all] Fehler 2 !!! ERROR: kde-base/kdelibs-3.4.3 failed. !!! Function kde_src_compile, Line 173, Exitcode 2 !!! died running emake, kde_src_compile:make = I did notice that there was /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/ which pointed to /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/ but 3.3.4 didn't exist. Instead there was /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/ so I created a symlink to 3.3.6 called 3.3.4 I don't know if this also is related to the libusb error, but at least I wanted to annotate that. Any hint about the libusb error? Best regards ce -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] libusb build error
On Sun, 11 Dec 2005 14:26:26 +0100 (CET), Rafael Fernández López wrote: If you do one by one, then you'll may have packages broken, because you don't know dependency tree by heart, so you should portage work for you. You'll also bork your world file if you don't use --oneshot when emerging individual packages. -- Neil Bothwick Orcs aren't all that bad... if you have plenty of ketchup. signature.asc Description: PGP signature
