| 1 |
Ciaran McCreesh wrote: |
| 2 |
> Fact: the underlying issue is a libtool bug. |
| 3 |
|
| 4 |
Wrong, it isn't just that, --as-needed and libtool are unrelated. |
| 5 |
|
| 6 |
> Fact: as-needed does not fix this bug. It attempts to work around it. |
| 7 |
|
| 8 |
Wrong, --as-needed does exactly what is supposed to do, precise bookkeeping. |
| 9 |
|
| 10 |
> Fact: as-needed breaks standard-compliant code. |
| 11 |
|
| 12 |
Wrong, --as-needed breaks disputable code that happens to be |
| 13 |
standard-compliant by a specific read of the standard. The fact the |
| 14 |
specific code is something wrong from the security/style/maintainability |
| 15 |
point makes it a bonus. |
| 16 |
|
| 17 |
> Fact: fixing the libtool bug would give all the benefits purportedly |
| 18 |
> given by using as-needed, without the drawbacks. |
| 19 |
|
| 20 |
Wrong, fixing libtool gives other benefits, so it's worth trying to fix |
| 21 |
it as well. The new autotools and proper usage of them makes life easier |
| 22 |
so it's worth improving on this side. |
| 23 |
|
| 24 |
> It's quite simple, |
| 25 |
|
| 26 |
Probably but is an empty sentence w/out supporting code. |
| 27 |
|
| 28 |
> and if there're any of the above that you didn't |
| 29 |
> already know then why are you wasting everyone else's time discussing |
| 30 |
> things in this thread without doing some basic research first? |
| 31 |
|
| 32 |
Basically most people is discussing with you since thinks, wrongly, that |
| 33 |
could be possible take something good from this discussion. The patch |
| 34 |
you pointed doesn't look complete nor acceptable to upstream as is, yet |
| 35 |
could help. |
| 36 |
|
| 37 |
lu |
| 38 |
|
| 39 |
-- |
| 40 |
|
| 41 |
Luca Barbato |
| 42 |
Gentoo Council Member |
| 43 |
Gentoo/linux Gentoo/PPC |
| 44 |
http://dev.gentoo.org/~lu_zero |
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-dev@l.g.o mailing list |
Archives