dev-libs/libsigc++-1.0.4-r2 emerge failed

[bodhiard]

Simple emerge of libsigc++ (as a dependency), simple error. Any insights?

[yinkoshaumer]

I am having the same issue. Have you found a solution?

[bodhiard]

No, I haven't found any solution yet. I have had bigger problems with the xorg update killing nvidia and kernel update killing dmraid. I guess I shouldn't be running ~arch, but I'm still a bit dissappointed in gentoo at the moment. Even fedora is working better than gentoo on my amd64 with nvidia software raid. Good luck. I'll be sure to post if I figure out what the issue was.

[nastasa_andrey]

The problem is that i have several packages that have the same problem (packages from system, xorg, kde and many others)
Post the output from:

[butters]

I'm had this problem too. The problem is related to the Makefile in the sigc++ and sigc++/config directories. Although the maintainer uses autotools, he felt the need to edit this Makefile by hand instead of correcting the corresponding Makefile.am input file, "commenting out" some target rules in a way that GNU Make does not support. You can see that this rule is the only rule specified in the Makefile.am, and yet there it sits, uncommented.

The sad part is that even though the offending rule causes the the build to break, it does so _after_ it accomplishes what it needs to do, which is to remove your existing libsigc++ library directory. Therefore, there's a relatively easy way to fix this.

Here's the really ugly hack to get libsigc++ to merge without waiting for upstream to fix it:

After your emerge fails, cd into /var/tmp/portage/libsigc++-1.0.4-r2/work/libsigc++-1.0.4/sigc++

There you will find two files of interest: Makefile and Makefile.am. Open both of these in an editor. In each file, search for the string "install-data-hook." In Makefile.am you will find the rule defined. Just delete that entire rule, from install-data-hook: label on down to where the "win32" comments are. In the Makefile itself, you will find something that looks a lot like this, except that it looks like it's commented out. It isn't... so delete that rule in the same way. In that file you will also find another instance of "install-data-hook" where it is appended on its own to a variable containing all the "normal" rules. Remove that, and make sure to save both files.

Now cd into the config directory below. Repeat the process above for deleting the install-data-hook rule in both Makefile and Makefile.am.

Now you get to rerun the rest of the emerge procedure, bypassing the features that normally protect you from people tampering with the source tree Here's how to do that:

cd /usr/portage/dev-libs/libsigc++
ebuild libsigc++-1.0.4-r2.ebuild install qmerge

This will hook into the emerge process after the compile phase (which has already completed successfully) and run the install phase with our changes. If your experience is like mine, then it will proceed successfully.

Before I wish you good luck, I want to emphasize that this is _not_ a supported way to fix the problem. Although there's almost zero chance of this affecting any other packages on your system, if it does break things, you're on your own.

Good luck!!
_________________
If tugboats were bigger, they'd be the ones getting tugged.

[hielvc]

butters is there a bug filed on this ? If There isnt could you sence you already solved it?
_________________
An A-Z Index of the Linux BASH command line

[kottlettstanze]

Hi,

this problem seems to be fixed in -r3, which is already in portage, but marked ~x86!

Perhaps the ~x86 flag should be removed.

Cheers
Kevin

[nixnut]