| 1 |
Hi all, |
| 2 |
|
| 3 |
|
| 4 |
> I'd do: |
| 5 |
> [*] emerge -vu portage |
| 6 |
> [*] emerge -vuDp world |
| 7 |
> [*] if everything went OK: emerge -vuD world |
| 8 |
> [*] revdep-rebuild --pretend |
| 9 |
> [*] revdep-rebuild |
| 10 |
|
| 11 |
so I did. Everything went fine, until it was libusb's turn. I still get: |
| 12 |
|
| 13 |
|
| 14 |
>>> Unpacking source... |
| 15 |
>>> Unpacking libusb-0.1.10a.tar.gz |
| 16 |
to /var/tmp/portage/libusb-0.1.10a/work |
| 17 |
* Applying 0.1.10a-fbsd.patch ... |
| 18 |
[ ok ] |
| 19 |
* Running eautoreconf in |
| 20 |
'/var/tmp/portage/libusb-0.1.10a/work/libusb-0.1.10a' ... |
| 21 |
* Running aclocal ... |
| 22 |
[ ok ] |
| 23 |
* Running libtoolize --copy --force --automake ... |
| 24 |
[ ok ] |
| 25 |
* Running aclocal ... |
| 26 |
[ ok ] |
| 27 |
* Running autoconf ... |
| 28 |
[ ok ] |
| 29 |
* Running autoheader ... |
| 30 |
[ ok ] |
| 31 |
* Running automake --add-missing --copy --foreign ... |
| 32 |
[ !! ] |
| 33 |
|
| 34 |
* Failed Running automake ! |
| 35 |
* |
| 36 |
* Include in your bugreport the contents of: |
| 37 |
* |
| 38 |
* /var/tmp/portage/libusb-0.1.10a/temp/automake-12138.out |
| 39 |
|
| 40 |
|
| 41 |
!!! ERROR: dev-libs/libusb-0.1.10a failed. |
| 42 |
!!! Function autotools_run_tool, Line 179, Exitcode 0 |
| 43 |
|
| 44 |
============= |
| 45 |
|
| 46 |
When I look into |
| 47 |
/var/tmp/portage/libusb-0.1.10a/temp/automake-12138.out |
| 48 |
it contains: |
| 49 |
|
| 50 |
***** automake ***** |
| 51 |
|
| 52 |
configure.in: installing `./mkinstalldirs' |
| 53 |
libusbpp_la_LDFLAGS: variable `QT_LDFLAGS' is used but `QT_LDFLAGS' is |
| 54 |
undefined |
| 55 |
|
| 56 |
============= |
| 57 |
|
| 58 |
|
| 59 |
A further issue I had before was that kdelibs didn't compile properly. |
| 60 |
It complained: |
| 61 |
|
| 62 |
grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such |
| 63 |
file or directory |
| 64 |
/bin/sed: can't |
| 65 |
read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such |
| 66 |
file or directory |
| 67 |
libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la' |
| 68 |
is not a valid libtool archive |
| 69 |
make[3]: *** [libkio.la] Fehler 1 |
| 70 |
make[3]: Leaving directory |
| 71 |
`/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3/kio' |
| 72 |
make[2]: *** [all-recursive] Fehler 1 |
| 73 |
make[2]: Leaving directory |
| 74 |
`/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3/kio' |
| 75 |
make[1]: *** [all-recursive] Fehler 1 |
| 76 |
make[1]: Leaving directory |
| 77 |
`/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3' |
| 78 |
make: *** [all] Fehler 2 |
| 79 |
|
| 80 |
!!! ERROR: kde-base/kdelibs-3.4.3 failed. |
| 81 |
!!! Function kde_src_compile, Line 173, Exitcode 2 |
| 82 |
!!! died running emake, kde_src_compile:make |
| 83 |
|
| 84 |
|
| 85 |
================= |
| 86 |
|
| 87 |
I did notice that there was |
| 88 |
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/ |
| 89 |
which pointed to |
| 90 |
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/ |
| 91 |
but 3.3.4 didn't exist. Instead there was |
| 92 |
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/ |
| 93 |
so I created a symlink to 3.3.6 called 3.3.4 |
| 94 |
|
| 95 |
I don't know if this also is related to the libusb error, but at least I |
| 96 |
wanted to annotate that. |
| 97 |
|
| 98 |
|
| 99 |
Any hint about the libusb error? |
| 100 |
|
| 101 |
|
| 102 |
Best regards |
| 103 |
|
| 104 |
|
| 105 |
ce |
| 106 |
|
| 107 |
-- |
| 108 |
gentoo-user@g.o mailing list |
Archives