Bugzilla Bug 145536

When using MAKEOPTS="-j3" the ebuild of libusb fails with the following error:
ld: cannot find -lusb

This looks like a concurrency issue to me, it doesn't fail without the -j3
option. I haven't looked into it, but I think it's an error in the makefile?
I've set this bug for 2006.0 and x86, because that's what I've found it on.
Maybe someone with another platform can check/confirm it's (not) just x86?

The last output form the ebuild is:

i686-pc-linux-gnu-g++ -shared -nostdlib
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../crti.o
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/crtbeginS.o  .libs/usbpp.o  -lusb
-L/usr/lib/gcc/i686-pc-linux-gnu/3.4.4
-L/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/lib
-L/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../..
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.so -L/usr/i686-pc-linux-gnu/bin
-L/usr/i686-pc-linux-gnu/lib -lm -lc -lgcc_s
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/crtendS.o
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../crtn.o  -march=i686 -Wl,-soname
-Wl,libusbpp-0.1.so.4 -o .libs/libusbpp-0.1.so.4.4.2
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/bin/ld:
cannot find -lusb
collect2: ld returned 1 exit status
make[2]: *** [libusbpp.la] Error 1
make[2]: *** Waiting for unfinished jobs....
 i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -O2 -march=i686 -pipe -Wall -MT
linux.lo -MD -MP -MF .deps/linux.Tpo -c linux.c  -fPIC -DPIC -o .libs/linux.o
 i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -O2 -march=i686 -pipe -Wall -MT
linux.lo -MD -MP -MF .deps/linux.Tpo -c linux.c -o linux.o >/dev/null 2>&1
make[2]: Leaving directory
`/var/tmp/portage/libusb-0.1.10a/work/libusb-0.1.10a'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/libusb-0.1.10a/work/libusb-0.1.10a'
make: *** [all] Error 2

!!! ERROR: dev-libs/libusb-0.1.10a failed.
Call stack:
  ebuild.sh, line 1539:   Called dyn_compile
  ebuild.sh, line 939:   Called src_compile
  libusb-0.1.10a.ebuild, line 37:   Called die

!!! emake failed
!!! If you need support, post the topmost build error, and the call stack if
relevant.

*** This bug has been marked as a duplicate of 137414 ***