Bugzilla Bug 155847

trying to emerge adesklets-0.6.1-r1, it wouldn#t install because of the
following error

test -d /var/tmp/portage/x11-misc/adesklets-0.6.1-r1/image//usr/share/info ||
/bin/sh /bin/sh
/var/tmp/portage/x11-misc/adesklets-0.6.1-r1/work/adesklets-0.6.1/install-sh -d
 /var/tmp/portage/x11-misc/adesklets-0.6.1-r1/image//usr/share/info
/bin/sh: /bin/sh cannot execute binary file

I stored the following patch as
"/usr/portage/x11-misc/files/adesklets-0.6.1-doc-makefile.patch"

----------------snip-------------------
--- doc/Makefile.in     2006-11-21 12:20:34.000000000 +0100
+++ doc/Makefile.in.fixed       2006-11-21 12:20:57.000000000 +0100
@@ -5,8 +5,8 @@
 # Makefile.am when creating a distribution of the package.
 #

-install = @SHELL@ @install_sh@ -c -m 644
-install_dir = @SHELL@ @install_sh@ -d
+install = @install_sh@ -c -m 644
+install_dir = @install_sh@ -d
 prefix  = @prefix@
 infodir = @infodir@
 man1dir = @mandir@/man1
----------------snip-------------------


and added the following line in src_unpack:

----------------snip-------------------
*** adesklets-0.6.1-r1.ebuild   2006-11-21 12:32:21.000000000 +0100
--- adesklets-0.6.1-r2.ebuild   2006-11-21 12:32:15.000000000 +0100
***************
*** 45,50 ****
--- 45,52 ----
        #Fix for bug #131813: linker flags ordering
        epatch ${FILESDIR}/${P}-fix-as-needed.patch

+       epatch ${FILESDIR}/adesklets-0.6.1-doc-makefile.patch
+
        #Fix for bug #148988: fontconfig >= 2.4 support
        use fontconfig &&
        {
----------------snip-------------------


an

 ebuild adesklets-0.6.1-r1.ebuild digest

and 

emerge adesklets

later, I had a working compile and install

Created an attachment (id=102461) [details]
the mentioned patch as attachment

works for me. Also this revision fixes that bug with fontconfig.

This patch worked for me also.

works for me too (on amd64 & x86).
It's almost 2 months since was marked as NEW, maybe someone can commit patch to
portage tree and close this bug ?

This bug is the same as bug #157002, which I just fixed :-)
Thanks for the submission anyway ;-)

*** This bug has been marked as a duplicate of bug 157002 ***