Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 94944 - libungif-4.1.0 needs libtoolize --copy --force (or a repatch)
Summary: libungif-4.1.0 needs libtoolize --copy --force (or a repatch)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: PPC Linux
: High normal (vote)
Assignee: PPC Porters
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-03 12:43 UTC by Armando Di Cianno (RETIRED)
Modified: 2005-06-04 07:53 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Armando Di Cianno (RETIRED) gentoo-dev 2005-06-03 12:43:41 UTC
Libungif is getting called in as a dependency for something I am trying to
emerge.  The build outputs, first:

 * Applying libungif-CVS.patch ...                                        [ ok ]
 * Applying libungif-4.1.0-stdarg.patch ...                               [ ok ]
>>> Source unpacked.
 * Patching ${S}/ltmain.sh ...
 *   Applying portage-1.3.3.patch ...
 *   Could not apply relink.patch!              <-- here
 * Applying uClibc/libtool patches ...
 *  Fixing ${S}/ltconfig... 

... and then, the final error is:

checking for powerpc-unknown-linux-gnu-ar... powerpc-unknown-linux-gnu-ar
checking for powerpc-unknown-linux-gnu-ranlib... powerpc-unknown-linux-gnu-ranlib
checking for powerpc-unknown-linux-gnu-strip... powerpc-unknown-linux-gnu-strip
checking for correct ltmain.sh version... no

*** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.16, ltmain.sh = 1.3.3) ***

Please run:

  libtoolize --copy --force

if appropriate, please contact the maintainer of this
package (or your distribution) for help.

make: *** [config.status] Error 1


Reproducible: Always
Steps to Reproduce:
1. emerge libungif
2.
3.

Actual Results:  
included above

Expected Results:  
libungif successfully installed

Likely the failed patch is causing this, but if not, remember to run something
along the lines of `autoreconf --install --force` after patching config/libtool
etc files.

Also, the ChangLog entries for libungif point that this may be solved for
>=4.1.3, if so, this needs to be stabilized soon.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2005-06-03 23:42:56 UTC
Can you mark 4.1.3 stable on ppc until libungif goes to /dev/null (Bug 85720)? 

This package has no metadata.xml.
Comment 2 Tobias Scherbaum (RETIRED) gentoo-dev 2005-06-04 07:53:36 UTC
4.1.3 marked ppc.