Re: [proaudio] Re: jack_mixer-9999 fails and deprecated ebuild warning

[Ede Wolf <listac@xxxxxxxxxxxxxxxx>]

I can confirm that after installing gconf jack_mixer builds fine.
However, a gconfless verion would be appreciated, if possible without
much extra work.



Am 23.01.2012 13:08, schrieb Gavin Pryke:
> On Saturday 21 January 2012 20:56:34 Nedko Arnaudov wrote:
>> Ede Wolf <listac@xxxxxxxxxxxxxxxx> writes:
>>> FYI: Just tried to install jack-mixer-9999:
>>>
>>> emerge -pv jack_mixer
>>>
>>> These are the packages that would be merged, in order:
>>>
>>> Calculating dependencies / *
>>>
>>>  *
>>>  "/usr/src/gentoo/layman/pro-audio/media-libs/pylash/pylash-3_pre.ebui
>>>  ld": * Deprecation Warning: Usage of distutils.eclass in packages not> 
>>> supporting installation
>>>
>>>  * for multiple Python ABIs in EAPI <=2 is deprecated and will be
>>>  banned
>>>
>>> on 2011-06-01.
>>>
>>>  * The ebuild needs to be fixed. Please report a bug, if it has not
>>>  been
>>>
>>> already reported.
>>>
>>>  *
>>>
>>> ... done!
>>> [ebuild  N     ] dev-python/pyxml-0.8.4-r2  USE="-doc -examples" 0 kB
>>> [0]
>>> [ebuild  N     ] dev-python/fpconst-0.7.3  0 kB [0]
>>> [ebuild  N    *] media-sound/jack_mixer-9999  USE="lash -debug -phat" 0
>>> kB [1]
>>>
>>>
>>>
>>> And the build itself fails:
>>> + autoconf
>>> configure.ac:66: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call
>>> detected in body
>>> ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
>>> ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded
>>> from... ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is
>>> expanded from... m4/jack.m4:4: AC_JACK_MIDI_NFRAMES_CHECK is expanded
>>> from...
>>> configure.ac:66: the top level
>>> configure.ac:91: error: possibly undefined macro: AM_GCONF_SOURCE_2
>>>
>>>       If this token and others are legitimate, please use
>>>       m4_pattern_allow. See the Autoconf documentation.
>>>  
>>>  * ERROR: media-sound/jack_mixer-9999 failed (prepare phase):
>>>  *   (no error message)
>>>  *
>>>  * Call stack:
>>>  *     ebuild.sh, line  75:  Called src_prepare
>>>  *   environment, line 3176:  Called die
>>>  * The specific snippet of code:
>>>  *       "${S}/autogen.sh" || die;
>>>  *
>>>  * If you need support, post the output of 'emerge --info
>>>
>>> =media-sound/jack_mixer-9999',
>>>
>>>  * the complete build log and the output of 'emerge -pqv
>>>
>>> =media-sound/jack_mixer-9999'.
>>>
>>>  * This ebuild is from an overlay named 'proaudio':
>>> '/usr/src/gentoo/layman/pro-audio/'
>>>
>>>  * The complete build log is located at
>>>
>>> '/var/log/portage/media-sound:jack_mixer-9999:20120116-144138.log'.
>>>
>>>  * The ebuild environment file is located at
>>>
>>> '/tmp/build/portage/media-sound/jack_mixer-9999/temp/environment'.
>>>
>>>  * S:
>>>  '/tmp/build/portage/media-sound/jack_mixer-9999/work/jack_mixer-9999'>  
>>>>>> Failed to emerge media-sound/jack_mixer-9999, Log file:
>>>>>>  '/var/log/portage/media-sound:jack_mixer-9999:20120116-144138.lo
>>>>>>  g'
>>>  
>>>  * GNU info directory index is up-to-date.
>>
>> The ebuild works on my machine. Do you have a patch that fixes the
>> ebuild for you?
> 
> Hi
> It looks like the autogen.sh script that is called in the 9999 ebuild is 
> calling autoreconf that in turn requires /usr/share/aclocal/gconf-2.m4 from 
> gnome-base/gconf.
> The jack_mixer-9 version compiles and installs fine here as does the 9999 but 
> I think if the gnome-base/gconf is not installed and jack_mixer-9999 is 
> emerged there will be this issue as the m4 macro doesn't exist on the system 
> yet.
> 
> Maybe a DEPEND on gnome-base/gconf, or one could add 
> /usr/share/aclocal/gconf-2.m4 as a file add patch to the jack_mixer 
> sources in a place like m4/gconf-2.m4 and do something like this in 
> src_prepare:
> AT_M4DIR="m4" eautoreconf
> 
> Either of those should work but not sure which for jack_mixer; I'm not 
> familiar with it.
> 
> I ran into a similar issue with alsa/esd macros being required for autoreconf 
> in media-sound/psindustrializer which I recently touched but that has 
> IUSE="alsa esd" so I chose to patch with the m4 files rather than add them as 
> a dependency as it's not sure which will be installed according to USE flags 
> set. jack_mixer looks different in that regard so maybe adding dependency 
> would be more suitable?
> 
> Cheers
> Gav
> 
>