| 1 |
Thomas Naujokas wrote: |
| 2 |
|
| 3 |
>Last night I did an: |
| 4 |
> |
| 5 |
> emerge --update --deep world |
| 6 |
> |
| 7 |
>Reviewing logs this morning I find in 3125-glibc-2.3.5-r1.log the |
| 8 |
>following: |
| 9 |
> |
| 10 |
> QA Notice: /usr/lib/misc/glibc/pt_chown is setXid, dynamically |
| 11 |
> linked and using lazy bindings. |
| 12 |
> This combination is generally discouraged. Try: |
| 13 |
> CFLAGS='-Wl,-z,now' emerge glibc |
| 14 |
> |
| 15 |
>I can see a couple of problems with this: |
| 16 |
> |
| 17 |
>1.) Wouldn't that compile glibc without any optimization settings? So |
| 18 |
> what I would rather do is merge the suggestion with my default |
| 19 |
> CFLAGS. Resulting in: |
| 20 |
> |
| 21 |
> CFLAGS='-O3 -march=athlon-xp -Wl,-z,now' emerge glibc |
| 22 |
> |
| 23 |
> Does this seem reasonable? |
| 24 |
> |
| 25 |
>2.) My impression of how portage works is that the next time glibc is |
| 26 |
> updated it will compile with the default again. Is there some place |
| 27 |
> to set this on a permanent basis? |
| 28 |
> |
| 29 |
>Tom Naujokas |
| 30 |
> |
| 31 |
> |
| 32 |
> |
| 33 |
Hi, |
| 34 |
First thing IMHO QA-notices are for devs, rarely for users so ignore it |
| 35 |
if no error so far. |
| 36 |
The CFLAGS you *may* put on the command-line are added to those in |
| 37 |
/etc/make.conf, so no need to repeat all. |
| 38 |
Think the using "-03" in your USE-flags isn't a good idea (use -02 |
| 39 |
instead) remember that with -03 any reports to Bugzilla are like INVALID |
| 40 |
(devs will suggest you use a more sane flags first). |
| 41 |
HTH. Rumen |
Archives