When compiling freebirth the compile fails with this : ./fusebirth > ./fused_loop.c 2>/dev/null make: *** [fused_loop.c] Error 139 this is related to the following line in Makefile fused_loop.c: fusebirth ./fusebirth > ./fused_loop.c 2>/dev/null when I remove the dev/null redirect I get: ./fusebirth > ./fused_loop.c Couldn't open sample: raw/kick.raw Couldn't open sample: raw/snare.raw Couldn't open sample: raw/cl_hat.raw Couldn't open sample: raw/op_hat.raw Couldn't open sample: raw/samp_1.raw make: *** [fused_loop.c] Error 139 this seems to be related to the sandbox tho I'm not sure. I'm playing with options to fix .. Reproducible: Always Steps to Reproduce: 1. emerge freebirth 2. 3.
I found a workaround. using ebuild ebuild.ebuild compile when it fails goto /var/tmp/portage/freebirth-0.3.2/work/freebirth-0.3.2 ./fusebirth > fused_loop.c ebuild compile again then install and merge. when it fails is creates the file fused_loop.c. but it's empty which might be why make fails ... but I added another command after the ./fusebirth > fused_loop.c command in the Makefile which doesn't run .. so I doubt it. still can get it compiled on one machine, but will play around and see if I can find out whats going on, on the other machine.
playing some more... I did an strace of the command "./fusebirth > ./fused_loop.c 2>/dev/null" to see if Ic an work out why the build is failing. and looking at the strace log the command segfaults. I'll attach the log.
Created attachment 21749 [details] ebuild failure strace of command strace of ./fusebirth > fused_loop.c command in freebirth Makefile
hmm... are you still seeing this? It emerged fine for me just now... maybe something in the new portage (0.50-r1 is what I have) has fixed it.
Yeah .. works fine now ... thanks :) bain
fixed with new portage...
