Re: [Audacity-devel] Error building (with python3 as /usr/bin/python)

[Gale (A. Team) <ga...@au...>]

"Campbell Barton" wrote:
> It would be nice to get this resolved since Audacity wont compile out
> of the box on Arch-Linux, Fedora is also moving to Python3:
> https://fedoraproject.org/wiki/Changes/Python_3_as_Default

To close this off, I assume Leland's fix:
https://code.google.com/p/audacity/source/detail?r=13096

solves this so supports any version of Python?


Gale


On Tue, Jan 21, 2014 at 7:13 PM, Lasse Steen Bohnstedt
<lassesteenbohnstedt@> wrote:
> I've just upgraded os x (to Lion) and downloaded audacity sources again
> via
> svn.
> ./configure couldn't complete because of a missing python2, it stopped in
> this section:
> === configuring in lib-src/lv2
>
> So I did this:
>   sudo ln -s /usr/bin/python /usr/bin/python2
> ... and it ran without further errors.
>
> Is that how it's supposed to be done for now?
>
> // Lasse
>
> On Wed, Dec 18, 2013 at 12:07 PM, Richard Ash <richard@>
> wrote:
>>
>> On Tue, 17 Dec 2013 11:46:10 +0000
>> Paul Livesey <paul-aud@> wrote:
>>
>> > On 16 Dec 2013, at 20:19, Benjamin Drung <bdrung@> wrote:
>> >
>> > > On Di, 2013-12-17 at 06:15 +1100, Campbell Barton wrote:
>> > >> Audacity fails to build since waf assumes python is python2
>> > >>
>> > >> http://www.pasteall.org/48067
>> > >>
>> > >> Im on arch-linux where running python will execute python3,
>> > >> probably waf should be explicitly called with python2.
>> > >
>> > > Sounds good. I went ahead and changed the "python" call into
>> > > "python2" in r12992.
>> >
>> > Unfortunately this fails to build on a Mac.
>> >
>> > ./configure: line 8: python2: command not found
>> > configure: error: ./configure failed for lib-src/lv2
>> >
>> > If you need any further details on this please ask.
>>
>> This doesn't surprise me, naming the binary "python2" is an artifact of
>> installing two copies of python on the same system because of lack of
>> backwards compatibility. For the same reason, most distributions have
>> not yet switched the default "python" to be python3, because it breaks
>> too many things!
>>
>> Ideally waf needs to be fixed upstream to work with python3, failing
>> that then configure needs to try various names for the python
>> interpreter to find the correct one on the build system - that is what
>> the configure script is for!
>>
>> Has anyone tried building without an installed copy of python to see
>> whether there is a sane error message? Fairly rare, but I suspect there
>> won't be!
>>
>> Richard





--
View this message in context: http://audacity.238276.n2.nabble.com/Error-building-with-python3-as-usr-bin-python-tp7560922p7561859.html
Sent from the audacity-devel mailing list archive at Nabble.com.