On Thu, 2012-06-28 at 15:09 -0400, Randy MacLeod wrote:
>
> autoconf and automake build as part of the "core" tools that get built
> before any target packages are built whereas python-native isn't in
> that set. When automake runs, it uses whatever python it finds.
> This will be the python-nati
On Thu, Jun 28, 2012 at 12:09 PM, Randy MacLeod
wrote:
>
> A solution might be to have autoconf and automake and python inherit a
> version of autotools that does not add a python-native dependency, say
> autotools-no-python, and then modify the "real" autotools class to
> add the python dependenc
autoconf and automake build as part of the "core" tools that get built
before any target packages are built whereas python-native isn't in
that set. When automake runs, it uses whatever python it finds.
This will be the python-native version if it has been built. When
doing parallel builds, it
