1 |
as some may have noticed, a lot of packages have suddenly started aborting |
2 |
with messages such as: |
3 |
* Patching ${S}/ltmain.sh ... |
4 |
* Portage patch failed to apply (ltmain.sh version 1.3.4)! |
5 |
!!! ERROR: category/package failed. |
6 |
!!! Function elibtoolize, Line 240, Exitcode 0 |
7 |
!!! Portage patch failed to apply! |
8 |
|
9 |
( http://bugs.gentoo.org/show_bug.cgi?id=92377 ) |
10 |
( http://bugs.gentoo.org/show_bug.cgi?id=92426 ) |
11 |
|
12 |
now, before you cry fowl [1] and start blaming base-system (keepers of |
13 |
libtool.eclass) for all your troubles, take a minute to ask yourself "do i |
14 |
actually know wtf elibtoolize does ? or did i just add it because everyone |
15 |
else was doing it and i'm merely a tool in the toolbox of life ?" |
16 |
|
17 |
the best way to verify whether your package should join in the lemming flow is |
18 |
like this: |
19 |
# sed -i -e '/die.*Portage/d' /usr/portage/eclass/libtool.eclass |
20 |
# emerge <your package> |
21 |
|
22 |
review the output. does libtool show *any* patches being applied |
23 |
successfully ? *did* you remember to turn off your oven last nite ? |
24 |
|
25 |
so if the emerge of your package displayed this: |
26 |
* Patching ${S}/ltmain.sh ... |
27 |
* Portage patch failed to apply (ltmain.sh version 1.3.5)! |
28 |
* Could not apply relink.patch! |
29 |
* Applying uClibc/libtool patches ... |
30 |
* Fixing ${S}/ltconfig ... [ ok ] |
31 |
|
32 |
then chances are *very* good you shouldnt be using the libtool eclass |
33 |
|
34 |
if you have any questions, or you think your package is special (everyone |
35 |
does), feel free to pipe up now and ask for a 2.5rd party review ... i dont |
36 |
mind telling you you're wrong, really, it's ok ... on the flip side, maybe |
37 |
libtool.eclass is wrongly aborting and in that case, i'd like to know so i |
38 |
can fix base-system's broken crap |
39 |
-mike |
40 |
|
41 |
[1] http://www.timsayers.com/silly/edited/00000004.jpg |
42 |
-- |
43 |
gentoo-dev@g.o mailing list |