From: Rod <Rod@Rods.id.au>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] ltmain.sh version 1.5.22
Date: Sat, 24 Jan 2009 21:11:41 +1100 [thread overview]
Message-ID: <497AE95D.8070909@Rods.id.au> (raw)
I'm getting the following error too much, many packages are no longer
insalling with this problem ;o(
>>> Emerging dev-libs/libmcrypt-2.5.8-r1
* libmcrypt-2.5.8.tar.gz RMD160 SHA1 SHA256 size ;-)
...
[ ok ]
* checking ebuild checksums ;-)
...
[ ok ]
* checking auxfile checksums ;-)
...
[ ok ]
* checking miscfile checksums ;-)
...
[ ok ]
>>> Unpacking source...
>>> Unpacking libmcrypt-2.5.8.tar.gz to
/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r1/work
* Applying libmcrypt-2.5.8-rotate-mask.patch
...
[ ok ]
* Running elibtoolize in: libmcrypt-2.5.8
* Applying install-sh-1.5.patch ...
* Portage patch failed to apply (ltmain.sh version 1.5.22)!
* Please bug azarah or vapier to add proper patch.
*
* ERROR: dev-libs/libmcrypt-2.5.8-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 2364: Called elibtoolize
* environment, line 943: Called die
* The specific snippet of code:
* die "Portage patch failed to apply!";
* The die message:
* Portage patch failed to apply!
*
* If you need support, post the topmost build error, and the call stack
if relevant.
* A complete build log is located at
'/var/log/portage/dev-libs:libmcrypt-2.5.8-r1:20081226-103235.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r1/temp/environment'.
*
Searching the Gentoo Forums, I get most posts about this from
2005... this is upgrading a currently working install.
next reply other threads:[~2009-01-25 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 10:11 Rod [this message]
2009-01-25 10:45 ` [gentoo-user] ltmain.sh version 1.5.22 Alan McKinnon
2009-01-26 21:23 ` Rod
2009-01-25 20:21 ` [gentoo-user] " ABCD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=497AE95D.8070909@Rods.id.au \
--to=rod@rods.id.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox