| 1 |
Mike Frysinger wrote: |
| 2 |
|
| 3 |
>On Friday 15 April 2005 10:29 am, Francesco Riosa wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>Mike Frysinger wrote: |
| 7 |
>> |
| 8 |
>> |
| 9 |
>>>as a reminder, NEVER utilize USE=pic in your package unless you know |
| 10 |
>>>exactly |
| 11 |
>>> |
| 12 |
>>> |
| 13 |
>>[... snip of how much PIC is bad ] |
| 14 |
>> |
| 15 |
>> |
| 16 |
> |
| 17 |
>PIC isnt bad ... people misusing USE=pic is bad |
| 18 |
> |
| 19 |
> |
| 20 |
received. |
| 21 |
|
| 22 |
> |
| 23 |
> |
| 24 |
>>A clarification: It's ok to use it _only_ for _libraryes_ by default ? |
| 25 |
>> |
| 26 |
>> |
| 27 |
> |
| 28 |
>a good rule of thumb: |
| 29 |
>shared objects should always be built with PIC |
| 30 |
> |
| 31 |
> |
| 32 |
> |
| 33 |
>>i.e |
| 34 |
>>econf [...] --with-lib-ccflags="-fPIC" |
| 35 |
>> |
| 36 |
>> |
| 37 |
> |
| 38 |
>ive never seen/used --with-lib-ccflags configure option before, but i imagine |
| 39 |
>it'll affect static libraries too right ? you dont want that |
| 40 |
> |
| 41 |
>the large majority of autotooled package gets PIC handling right so you |
| 42 |
>shouldnt need this kind of crap ... |
| 43 |
>-mike |
| 44 |
> |
| 45 |
> |
| 46 |
fast grepping on "configure" show code for -fPIC utilization --> I must |
| 47 |
see how to change the ebuilds my worryes goes to amd64 ... will see |
| 48 |
|
| 49 |
-- |
| 50 |
gentoo-dev@g.o mailing list |
Archives