Le Sun, 31 Mar 2013 18:54:15 +0200, Karl Lindén <spray.su...@gmail.com> a écrit :
> This does not solve the problem for me. I still get a segfault. Me too. I have investigated the cflags and -j1, but without success. I will report it upstream. All it does for now is to select the correct python version allowing to install guitarix2 even when python 3 is set. It was the more urgent. When we finally get guitarix2 to install with this wrapper, we can add other functions if needed. > And > besides, why not use the new python[-single]-r1 eclass? We are > building a library so it could be good for reverse dependencies (even > though there are none at the moment) to know what python > implementation is used. I don't think that would be overkill, but what > do you think? I missed it, thanks. I will take a look at it. Dominique > > Karl > > 2013/3/31 <subvers...@tuxfamily.net>: > > Revision: 2626 > > Author: dominique > > Date: 2013-03-31 18:36:31 +0200 (Sun, 31 Mar 2013) > > Log Message: > > ----------- > > guitarix2: initial support for python eclass > > > > Modified Paths: > > -------------- > > trunk/overlays/proaudio/media-sound/guitarix2/ChangeLog > > trunk/overlays/proaudio/media-sound/guitarix2/Manifest > > trunk/overlays/proaudio/media-sound/guitarix2/guitarix2-0.25.2.ebuild > > trunk/overlays/proaudio/media-sound/guitarix2/guitarix2-9999.ebuild > > > > -- "We have the heroes we deserve."
