[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Denemo-devel] The overnight builds
From: |
Richard Shann |
Subject: |
Re: [Denemo-devel] The overnight builds |
Date: |
Wed, 08 Jun 2016 16:02:19 +0100 |
On Wed, 2016-06-08 at 09:33 -0500, Jeremiah Benham wrote:
>
>
> On Wed, Jun 8, 2016 at 6:09 AM, Richard Shann
> <address@hidden> wrote:
> On Mon, 2016-06-06 at 10:01 -0500, Jeremiah Benham wrote:
> > It appears that gub has been building against aubio 3 not
> aubio 4. I
> > did not realize this before. I was confused because I have
> to build
> > files libaubio.py and aubio.py. The problem is that gub uses
> python
> > 2.4 and and waf (this is used to build aubio4) does not
> support python
> > 2.4. I am trying to see if I can upgrade python to get this
> to build.
> > I had to downgrade python from 2.6 at one point because it
> was not
> > building lilypond. I am looking into upgrading python back
> to 2.6.
> >
> With the latest commits I get the default build failing with
> this:
>
> audio/pitchrecog.o: In function `aubio_finish':
>
> /home/rshann/git-denemo/localbuild/src/../../denemo/src/audio/pitchrecog.c:115:
> undefined reference to `del_fvec'
> ...
>
> By configuring with --enable-aubio it built ok
>
>
> I have a patch to enable aubio by default. --disable-aubio will turn
> it off support. Configure will abort if aubio is not present? Should I
> have configure disable support and finish while printing printing
> LIBAUBIO......NO?
I'm not quite sure I understand - are you asking if configure should
switch to disabling aubio if it is configuring with aubio enabled and
fails to find aubio? That would be unusual I think.
Richard