HAL emerge problem.

[bluezone]

Everytime I try to emerge hal, I've been getting the following errors:

/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../lib/libcap.a(cap_text.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../lib/libcap.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[3]: *** [hald] Error 1
make[3]: Leaving directory `/var/tmp/portage/hal-0.4.2/work/hal-0.4.2/hald'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/hal-0.4.2/work/hal-0.4.2/hald'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/hal-0.4.2/work/hal-0.4.2'
make: *** [all] Error 2

!!! ERROR: sys-apps/hal-0.4.2 failed.
!!! Function src_compile, Line 56, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.


Does anyone else have this problem or know of a possible solution?

[garlicbread]

I've not tried HAL myself yet
but as a temporary work around you could try adding this to the top of the ebuild
CFLAGS="${CFLAGS} -fPIC"

from looking here
https://forums.gentoo.org/viewtopic.php?t=166294&highlight=fpic
it looks as if some packages need to be updated so that they use the -fPIC option in the right place while building on amd64 systems for certain libs
(In other words I think the ideal solution is for one of the package's Makefiles to be updated to use -fPIC in the right place)
I think adding -fPIC to your general use Flags in make.conf is probably a bad idea but the above will limit it to that particular ebuild at least