
1116066858: === (1 of 82) Cleaning (media-libs/lcms-1.13::/usr/portage/media-libs/lcms/lcms-1.13.ebuild)slycordinator wrote:Which ebuild was it that it failed on? Once you tell me that I can easily tell you where to put it after examining that ebuild.
And I know you said it was when doing "emerge kde" but there are a lot of dependencies for kde.
slycordinator wrote:Which ebuild was it that it failed on? Once you tell me that I can easily tell you where to put it after examining that ebuild.
And I know you said it was when doing "emerge kde" but there are a lot of dependencies for kde.
Code: Select all
# cd /usr/portage/lib-media/lcms/
# ebuild lcms-1.13.ebuild digest
# emerge lcms

That's weird. I saw nothing in the ebuild manpage that would indicate that a patch could be applied to an ebuild like that.stillman wrote:just had the same issue, tried to apply the patch and finally found out how it works:
copy the patch to /usr/portage/lib-media/lcms/don't know how portage does it but there must be some kind of magic trick involved...Code: Select all
# cd /usr/portage/lib-media/lcms/ # ebuild lcms-1.13.ebuild digest # emerge lcms
Code: Select all
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.5) ***
Please run:
libtoolize --copy --force
if appropriate, please contact the maintainer of this
package (or your distribution) for help.
!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/lcms-1.13/work/lcms-1.13/config.log
!!! ERROR: media-libs/lcms-1.13 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.
well, it included the patch in the md5-check so i guess it must have used it, i didn't do anything else with success. in german we say:"probieren geht über studieren"("trying is better than studying" - reg. dict.leo.org:"The proof of the pudding is in the eating.")slycordinator wrote: That's weird. I saw nothing in the ebuild manpage that would indicate that a patch could be applied to an ebuild like that.
Code: Select all
checking for i686-pc-linux-gnu-strip... (cached) i686-pc-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.5) ***
Please run:
libtoolize --copy --force
if appropriate, please contact the maintainer of this
package (or your distribution) for help.
!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/lcms-1.13/work/lcms-1.13/config.log
!!! ERROR: media-libs/lcms-1.13 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.SAngeli wrote:[SOLVED]
I solved this issue this way:
1) emerge sync
2) emerge lcms (which compliled lcms-1.13-r1 as being the latest version in portage)
Code: Select all
checking for strip... 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.5a) ***
Please run:
libtoolize --copy --force
if appropriate, please contact the maintainer of this
package (or your distribution) for help.
*** Exited with status: 1 ***
That "solution" (syncing to a new portage tree) only fixes the lcms problem. Essentially, someone patched the ebuild for lcms.shi^Yo wrote:SAngeli wrote:[SOLVED]
I solved this issue this way:
1) emerge sync
2) emerge lcms (which compliled lcms-1.13-r1 as being the latest version in portage)
still not working here, even with the solution. Still geting the following error msg from kdevelop:
Code: Select all
checking for strip... 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.5a) *** Please run: libtoolize --copy --force if appropriate, please contact the maintainer of this package (or your distribution) for help. *** Exited with status: 1 ***
looks like i ve chosen a bad time to transmit fro java to c++
Code: Select all
So other ebuilds that are written incorrectly WILL STILL SHOW THE SAME PROBLEM.
I'm well aware of this.nixnut wrote:So? File bug reports if you find such ebuilds, so developers can fix them.Code: Select all
So other ebuilds that are written incorrectly WILL STILL SHOW THE SAME PROBLEM.