Summary: | media-video/acidrip-0.14-r1 test for MPlayer: sh: line 1: 3664 Segmentation fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Don Bishop <dbishop> |
Component: | New packages | Assignee: | Gentoo Media-video project <media-video> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | beandog, dbishop, peter |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
elog output from most recend build attempt
new ebuild based on acidrip-0.14-r2.ebuild with this bug solution |
Description
Don Bishop
2010-01-01 03:18:33 UTC
Created attachment 214816 [details]
elog output from most recend build attempt
The same problem with acidrip-0.14-r2 rebuild after update tu mplayer-1.0_rc4_p20100213. This test doesn't set any variable so it is obsolete when media-video/mplayer is set in dependences. Created attachment 219831 [details]
new ebuild based on acidrip-0.14-r2.ebuild with this bug solution
As I said, tesing presence of mplayer, is obsolete when mplayer is in dependences. Solution is to delete test lines from makefile, by comand:
sed -i '58,62d' ${S}/Makefile.PL
For those that have this problem, this can be a very frustrating bug. I have several gentoo machines, and the mainstream ebuild works fine on all of them except the one I want it to work on! It's the same machine I reported on above. I have gone to extraordinary measures to figure out what is different between these various machines, but I cannot find the issue: deleted all directories and files associated with acidrip, elogs, temp directories, you name it. I have changed use flags, done emerge -e world more times than you can count, and I can even get a successful return from the Makefile.PL script that performs the test -- it only fails when run from the ebuild environment. ANYWAY...The sed patch proposed by Hack_leberry Finn works perfectly. I was hoping that the maintainer would fix the ebuild officially, but so far, no joy. Until then, anyone wanting to work around this may choose to do what I finally did: Create a portage overlay, and put your own acidrip-0.14-r3.ebuild in there. It's pretty easy: 1. Edit your /etc/make.conf file and uncomment this line: PORTDIR_OVERLAY=/usr/local/portage 2. mkdir -p /usr/local/portage/media-video/acidrip/files 3. cd /usr/portage/media-video/acidrip 4. cp /usr/portage/media-video/acidrip/files/acidrip-mplayer.patch files/ 5. cp /usr/portage/media-video/acidrip/acidrip-0.14-r2.ebuild ./acidrip-0.14-r3.ebuild 6. edit the acidrip-0.14-r3.ebuild: Change EAPI="2" to EAPI=3 and add the line sed -i '58,62d' ${S}/Makefile.PL just after the epatch "${FILESDIR}/${PN}-mplayer.patch" line (this is essentially Hack_leberry Finn's fix) 7. ebuild acidrip-0.14-r3.ebuild digest 8. emerge -uvDN acidrip You will likely get a message from portage mentioning that it will use [1] /usr/local/portage -- which is what you want It should emerge just fine. [red face] Don't change EAPI to "3" in my step 6 above (comment #4). While it should work okay, it's not correct, so better to leave it as EAPI="2". Sorry for the misstep. Removed the dependency checks from the Makefile completely. Thanks for the bug report, and patch! Fixed in CVS. |