Re: [proaudio] Jack 1.9.7 doesn't compile

[Gavin Pryke <gavinlee303@xxxxxxxxx>]

On Sunday 30 October 2011 16:32:28 Dubphil wrote:
> Hello,
> 
> Just wanted to update my gentoo, but Jack doesn't want to compile, so I
> 
> have done --skip-first and at the end retry to emerge it :
> >>> Emerging (1 of 2) media-sound/jack-audio-connection-kit-1.9.7 from
> >>> proaudio
> 
>   * jack-1.9.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...
>                                                         [ ok ]
>   * QA Notice: The 'hasq' function is deprecated (replaced by 'has')
>   * QA Notice: The 'hasq' function is deprecated (replaced by 'has')
> 
> >>> Unpacking source...
> >>> Unpacking jack-1.9.7.tar.bz2 to
> >>> /var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/work
> >>> Source unpacked in
> >>> /var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/work
> >>> Compiling source in
> >>> /var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/work/jack-
> >>> 1.9.7 ...
> 
>   * Running "./waf configure --prefix=/usr
> --destdir=/var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/imag
> e/ --alsa --classic" ...
>    File "./waf", line 49
>      print '\033[91mError: %s\033[0m' % m
>                                     ^
> SyntaxError: invalid syntax
>   * ERROR: media-sound/jack-audio-connection-kit-1.9.7 failed (compile
> phase):
>   *   waf configure failed
>   *
>   * Call stack:
>   *     ebuild.sh, line  56:  Called src_compile
>   *   environment, line 739:  Called die
>   * The specific snippet of code:
>   *       ./waf configure ${myconf} || die "waf configure failed";
>   *
>   * If you need support, post the output of 'emerge --info
> =media-sound/jack-audio-connection-kit-1.9.7',
>   * the complete build log and the output of 'emerge -pqv
> =media-sound/jack-audio-connection-kit-1.9.7'.
>   * This ebuild is from an overlay named 'proaudio':
> '/var/lib/layman/pro-audio/'
>   * The complete build log is located at
> '/var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/temp/build.lo
> g'. * The ebuild environment file is located at
> '/var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/temp/environm
> ent'. * S:
> '/var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/work/jack-1.9
> .7'
> 
> >>> Failed to emerge media-sound/jack-audio-connection-kit-1.9.7, Log
> >>> file:
> >>> 
> >>> 
> >>> '/var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/temp/buil
> >>> d.log'
> 
>   * Messages for package media-sound/jack-audio-connection-kit-1.9.7:
> 
>   * ERROR: media-sound/jack-audio-connection-kit-1.9.7 failed (compile
> phase):
>   *   waf configure failed
>   *
>   * Call stack:
>   *     ebuild.sh, line  56:  Called src_compile
>   *   environment, line 739:  Called die
>   * The specific snippet of code:
>   *       ./waf configure ${myconf} || die "waf configure failed";
>   *
>   * If you need support, post the output of 'emerge --info
> =media-sound/jack-audio-connection-kit-1.9.7',
>   * the complete build log and the output of 'emerge -pqv
> =media-sound/jack-audio-connection-kit-1.9.7'.
>   * This ebuild is from an overlay named 'proaudio':
> '/var/lib/layman/pro-audio/'
>   * The complete build log is located at
> '/var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/temp/build.lo
> g'. * The ebuild environment file is located at
> '/var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/temp/environm
> ent'. * S:
> '/var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.7/work/jack-1.9
> .7'
> 
> What can I do instead of upgrading to Jack2 ? (on my setup ecasound is
> not working with jack2)
> 
> Best regards
> 
> Philippe


If your default python interpreter is set as 3.x that could be the problem.
From looking at the print statement it seems like it, in python-3.x print is a 
function. Maybe the ebuild needs changing to make sure waf gets executed with 
python2.
Not much time to look at anything lately, sorry :(

Cheers
Gav