[oe] [gcc 4.4.2] [libcap, vdr] relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC

[Frans Meulenbroeks]

2010/1/12 Paul Menzel <paulepanter at users.sourceforge.net>:
> Dear OE hackers,
>
>
> sorry for bothering you with this. I am trying to reproduce the errors
> Henning has seen with g++ 4.4.2 [1] and therefore added the following
> lines to my `local.conf` for Ångström with BeagleBoard [2].
>
> Am Montag, den 11.01.2010, 23:42 +0100 schrieb Paul Menzel:
>
> […]
>
>> Putting
>>
>>         PREFERRED_VERSION_binutils               = "2.20"
>>         PREFERRED_VERSION_binutils-cross         = "2.20"
>>         PREFERRED_VERSION_binutils-cross-sdk     = "2.20"
>>
>>         PREFERRED_VERSION_gcc                    = "4.4.2"
>>         PREFERRED_VERSION_gcc-cross              = "4.4.2"
>>         PREFERRED_VERSION_gcc-cross-sdk          = "4.4.2"
>>         PREFERRED_VERSION_gcc-cross-initial      = "4.4.2"
>>         PREFERRED_VERSION_gcc-cross-intermediate = "4.4.2"
>>
>> in my `local.conf` and running `bitbake vdr` gave me an error in
>> `do_compile` for `libcap_1.10.bb`.
>>
>>         arm-angstrom-linux-gnueabi-ld -soname libcap.so.1 -x -shared -o libcap.so.1.10 cap_alloc.o cap_proc.o cap_extint.o cap_flag.o cap_text.o cap_sys.o
>>         arm-angstrom-linux-gnueabi-ld: cap_text.o: relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC
>
> I do not get these errors if I use the standard versions defined for
> Ångström which is 4.1.1. Adding `-fPIC` to the flags as suggested in [3]
> solves the problem for me.
>
> Does anyone know if GCC’s behavior was changed somehow?

Did you start from scratch (with an empty tmp)? If not it might well
be that something has been changed and you are mixing objects from two
versions of gcc (which possibly their own set of options and
defaults).

Frans