Ardour 3.0 build problem

[Henry W. Peters]

Hi,

Trying to build version 3.0... (just checked out at svn), I think I
figured out that the "Checking for header boost/shared_ptr.hpp    : not
found" & "Checking for header boost/weak_ptr.hpp      : not found"  was
related to boost 1.40.0 (latest version)... & once downloaded,
apparently no need to build anything (unless I misunderstand), but this
likely means you have to: 1.)  inform Ardour of the path location or 2.)
place the files in a correct path???? (a big & probably unjustified
guess on my part).

Also, could not find 'soundtouch-1.0' & when I do a search for (Checking
for) slv2 (>= 0.6.4) in Synaptic Package Manager, 'libnss31d v.3.12.3.1'
files show up, & are installed... so question is, how do I get the
proper slv2 file?

As you may be able to see, from the below report from terminal, I was
able to configure "successfully," but my other guess is, the missing
files (etc.), might & or would impede usefulness of Ardour (?).

Any help will be appreciated.

Henry


~/3.0$ ./waf configure
Writing svn revision info to libs/ardour/svn_revision.cc
Checking for program gcc                    : ok /usr/bin/gcc
Checking for program cpp                    : ok /usr/bin/cpp
Checking for program ar                     : ok /usr/bin/ar
Checking for program ranlib                 : ok /usr/bin/ranlib
Checking for gcc                            : ok  
Checking for program g++                    : ok /usr/bin/g++
Checking for g++                            : ok  
Checking for glib-2.0 >= 2.2                : ok
Checking for glibmm-2.4 >= 2.14.0           : ok
Checking for libxml-2.0                     : ok
Checking for sigc++-2.0 >= 2.0              : ok
Checking for uuid                           : ok
Checking for function getmntent             : ok
Checking for header execinfo.h              : ok
Checking for header boost/shared_ptr.hpp    : not found
Checking for header boost/weak_ptr.hpp      : not found
Checking for jack >= 0.109.0                : ok
Checking for cppunit >= 1.12.0              : ok
Checking for gthread-2.0 >= 2.14.0          : ok
Checking for fftw3                          : ok
Checking for fftw3f                         : ok
Checking for aubio                          : ok
Checking for liblo                          : ok
Checking for function usb_interrupt_write   : not found
Checking for header linux/input.h           : ok
Checking for function lo_server_new         : ok
Checking for program as                     : ok /usr/bin/as
Checking for lrdf >= 0.4.0                  : ok
Checking for samplerate >= 0.1.0            : ok
Checking for slv2 >= 0.6.4                  : fail
Checking for sndfile >= 1.0.18              : ok
Checking for soundtouch-1.0                 : not found
Checking for ogg >= 1.1.2                   : ok
Checking for flac >= 1.2.1                  : ok
Checking for header sys/vfs.h               : ok
Checking for header wordexp.h               : ok
Checking for FLAC support                   : True
Checking for Ogg/Vorbis support             : True
Checking for gtkmm-2.4 >= 2.8               : ok
Checking for gtk+-2.0 >= 2.12.1             : ok
Checking for alsa                           : ok
Checking for libgnomecanvas-2.0 >= 2.0      : ok
Checking for libgnomecanvasmm-2.6 >= 2.12.0 : ok

Global configuration
Install prefix                              : /usr/local
Debuggable build                            : False
Strict compiler flags                       : False
Build documentation                         : False

Ardour Configuration
Build Target                                : []
Architecture flags                          : None
Aubio                                       : True
AudioUnits                                  : False
FPU Optimization                            : True
Freedesktop Files                           : False
Freesound                                   : False
GtkOSX                                      : False
LV2 Support                                 : False
Rubberband                                  : True
Samplerate                                  : True
Soundtouch                                  : False
Translation                                 : True
System Libraries                            : True
Tranzport                                   : False
Universal Binary                            : False
VST Support                                 : False
Wiimote Support                             : False
Windows Key                                 : Mod4><Super
system triple: i686-pc-linux-gnu
Checking for function posix_memalign        : ok
C Compiler flags                            : ['-DNDEBUG', '-fPIC',
'-DPIC', '-fshow-column', '-DWAF_BUILD', '-O3', '-fomit-frame-pointer',
'-ffast-math', '-fstrength-reduce', '-pipe', '-DARCH_X86', '-mmmx',
'-m3dnow', '-march=i686', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN',
'-DBUILD_SSE_OPTIMIZATIONS', '-Wall', '-D_LARGEFILE64_SOURCE',
'-D_LARGEFILE_SOURCE', '-DENABLE_NLS']
C++ Compiler flags                          : ['-DNDEBUG', '-fPIC',
'-DPIC', '-fshow-column', '-DWITH_JACK_MIDI', '-DHAVE_FFTW3',
'-DWAF_BUILD', '-O3', '-fomit-frame-pointer', '-ffast-math',
'-fstrength-reduce', '-pipe', '-DARCH_X86', '-mmmx', '-m3dnow',
'-march=i686', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN',
'-DBUILD_SSE_OPTIMIZATIONS', '-Wall', '-Woverloaded-virtual',
'-D_LARGEFILE64_SOURCE', '-D_LARGEFILE_SOURCE', '-DENABLE_NLS']
'configure' finished successfully (2.995s)

_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Henry W. Peters]

A small postscript... I also neglected to mention that I could not find
the file related to 'function usb_interrupt_write.'

Henry

Henry W. Peters wrote:

> Hi,
>
> Trying to build version 3.0... (just checked out at svn), I think I
> figured out that the "Checking for header boost/shared_ptr.hpp    :
> not found" & "Checking for header boost/weak_ptr.hpp      : not
> found"  was related to boost 1.40.0 (latest version)... & once
> downloaded, apparently no need to build anything (unless I
> misunderstand), but this likely means you have to: 1.)  inform Ardour
> of the path location or 2.) place the files in a correct path???? (a
> big & probably unjustified guess on my part).
>
> Also, could not find 'soundtouch-1.0' & when I do a search for
> (Checking for) slv2 (>= 0.6.4) in Synaptic Package Manager, 'libnss31d
> v.3.12.3.1' files show up, & are installed... so question is, how do I
> get the proper slv2 file?
>
> As you may be able to see, from the below report from terminal, I was
> able to configure "successfully," but my other guess is, the missing
> files (etc.), might & or would impede usefulness of Ardour (?).
>
> Any help will be appreciated.
>
> Henry
>
>
> ~/3.0$ ./waf configure
> Writing svn revision info to libs/ardour/svn_revision.cc
> Checking for program gcc                    : ok /usr/bin/gcc
> Checking for program cpp                    : ok /usr/bin/cpp
> Checking for program ar                     : ok /usr/bin/ar
> Checking for program ranlib                 : ok /usr/bin/ranlib
> Checking for gcc                            : ok  Checking for program
> g++                    : ok /usr/bin/g++
> Checking for g++                            : ok  Checking for
> glib-2.0 >= 2.2                : ok
> Checking for glibmm-2.4 >= 2.14.0           : ok
> Checking for libxml-2.0                     : ok
> Checking for sigc++-2.0 >= 2.0              : ok
> Checking for uuid                           : ok
> Checking for function getmntent             : ok
> Checking for header execinfo.h              : ok
> Checking for header boost/shared_ptr.hpp    : not found
> Checking for header boost/weak_ptr.hpp      : not found
> Checking for jack >= 0.109.0                : ok
> Checking for cppunit >= 1.12.0              : ok
> Checking for gthread-2.0 >= 2.14.0          : ok
> Checking for fftw3                          : ok
> Checking for fftw3f                         : ok
> Checking for aubio                          : ok
> Checking for liblo                          : ok
> Checking for function usb_interrupt_write   : not found
> Checking for header linux/input.h           : ok
> Checking for function lo_server_new         : ok
> Checking for program as                     : ok /usr/bin/as
> Checking for lrdf >= 0.4.0                  : ok
> Checking for samplerate >= 0.1.0            : ok
> Checking for slv2 >= 0.6.4                  : fail
> Checking for sndfile >= 1.0.18              : ok
> Checking for soundtouch-1.0                 : not found
> Checking for ogg >= 1.1.2                   : ok
> Checking for flac >= 1.2.1                  : ok
> Checking for header sys/vfs.h               : ok
> Checking for header wordexp.h               : ok
> Checking for FLAC support                   : True
> Checking for Ogg/Vorbis support             : True
> Checking for gtkmm-2.4 >= 2.8               : ok
> Checking for gtk+-2.0 >= 2.12.1             : ok
> Checking for alsa                           : ok
> Checking for libgnomecanvas-2.0 >= 2.0      : ok
> Checking for libgnomecanvasmm-2.6 >= 2.12.0 : ok
>
> Global configuration
> Install prefix                              : /usr/local
> Debuggable build                            : False
> Strict compiler flags                       : False
> Build documentation                         : False
>
> Ardour Configuration
> Build Target                                : []
> Architecture flags                          : None
> Aubio                                       : True
> AudioUnits                                  : False
> FPU Optimization                            : True
> Freedesktop Files                           : False
> Freesound                                   : False
> GtkOSX                                      : False
> LV2 Support                                 : False
> Rubberband                                  : True
> Samplerate                                  : True
> Soundtouch                                  : False
> Translation                                 : True
> System Libraries                            : True
> Tranzport                                   : False
> Universal Binary                            : False
> VST Support                                 : False
> Wiimote Support                             : False
> Windows Key                                 : Mod4><Super
> system triple: i686-pc-linux-gnu
> Checking for function posix_memalign        : ok
> C Compiler flags                            : ['-DNDEBUG', '-fPIC',
> '-DPIC', '-fshow-column', '-DWAF_BUILD', '-O3',
> '-fomit-frame-pointer', '-ffast-math', '-fstrength-reduce', '-pipe',
> '-DARCH_X86', '-mmmx', '-m3dnow', '-march=i686', '-msse',
> '-mfpmath=sse', '-DUSE_XMMINTRIN', '-DBUILD_SSE_OPTIMIZATIONS',
> '-Wall', '-D_LARGEFILE64_SOURCE', '-D_LARGEFILE_SOURCE', '-DENABLE_NLS']
> C++ Compiler flags                          : ['-DNDEBUG', '-fPIC',
> '-DPIC', '-fshow-column', '-DWITH_JACK_MIDI', '-DHAVE_FFTW3',
> '-DWAF_BUILD', '-O3', '-fomit-frame-pointer', '-ffast-math',
> '-fstrength-reduce', '-pipe', '-DARCH_X86', '-mmmx', '-m3dnow',
> '-march=i686', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN',
> '-DBUILD_SSE_OPTIMIZATIONS', '-Wall', '-Woverloaded-virtual',
> '-D_LARGEFILE64_SOURCE', '-D_LARGEFILE_SOURCE', '-DENABLE_NLS']
> 'configure' finished successfully (2.995s)
>
> _______________________________________________
> Ardour-Users mailing list
> ardour-users@...
> http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
>
>

_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Paul Davis]

On Thu, Oct 8, 2009 at 2:10 PM, Henry W. Peters <hwpeters@...> wrote:
> A small postscript... I also neglected to mention that I could not find the
> file related to 'function usb_interrupt_write.'

with the greatest respect, if  these issues are blocking problems for
you, then its not appropriate that you be attempting to build 3.0.

--p
_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Henry W. Peters]

Is this an "official" position... ?

Henry

Paul Davis wrote:

> On Thu, Oct 8, 2009 at 2:10 PM, Henry W. Peters <hwpeters@...> wrote:
>  
>> A small postscript... I also neglected to mention that I could not find the
>> file related to 'function usb_interrupt_write.'
>>    
>
> with the greatest respect, if  these issues are blocking problems for
> you, then its not appropriate that you be attempting to build 3.0.
>
> --p
>
>
>  

_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Patrick Shirkey]

On 10/09/2009 07:20 AM, Henry W. Peters wrote:
> Is this an "official" position... ?
>


Pretty much yes.

You will need to get the -dev or -devel versions of the deps that are
missing in order to compile.


Cheers.



Patrick Shirkey
Boost Hardware Ltd


_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Henry W. Peters]

But that is just it... I know this, & have seemed to get all the
appropriate dependencies up to THOSE ONES (maybe 8 of them)! I found not
even the non "-dev" versions of those I listed... (except the headers
for "header boost/weak_ptr.hpp" etc., which may be another kind of
problem (?)),  & basically, looked thru the wiki on installation... &
found no instructions on *those* items.

I have built (say) Ardour 2.xx quite a few times... struggling with
installation of the dependencies, etc., with some differing versions of
my distro (Ubuntu), got the program to run, but had digital audio input  
problems (probably sound card, etc., compatibility?) with it... so
Ardour as a *functioning* program (I have been doing digital audio for
maybe 15 years, much of which was with Pro Tools, when I ran Mac OS, pre
version 9.0), as is (the so-called "stable" version), is strictly a
hypothetical, for me; point is, to reiterate, & emphasize, version 2.xx
is not a useable program for me... I was hoping to see if there were
issues that might have been resolved, so that I could reconsider
utilizing Ardour.

So if you are saying, even if you know better (re installation) & have
problems where documentation is not (at the least) apparently
available... too bad... or what?   & are you really saying you (who ever
"you" is) are not interested in some one actually trying to learn? That
would be just too sad.

Henry

Patrick Shirkey wrote:

>
> On 10/09/2009 07:20 AM, Henry W. Peters wrote:
>> Is this an "official" position... ?
>>
>
>
> Pretty much yes.
>
> You will need to get the -dev or -devel versions of the deps that are
> missing in order to compile.
>
>
> Cheers.
>
>
>
> Patrick Shirkey
> Boost Hardware Ltd
>
>
>
>

_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Patrick Shirkey]

On 10/09/2009 10:52 AM, Henry W. Peters wrote:

> But that is just it... I know this, & have seemed to get all the
> appropriate dependencies up to THOSE ONES (maybe 8 of them)! I found
> not even the non "-dev" versions of those I listed... (except the
> headers for "header boost/weak_ptr.hpp" etc., which may be another
> kind of problem (?)), & basically, looked thru the wiki on
> installation... & found no instructions on *those* items.
>
> I have built (say) Ardour 2.xx quite a few times... struggling with
> installation of the dependencies, etc., with some differing versions
> of my distro (Ubuntu), got the program to run, but had digital audio
> input  problems (probably sound card, etc., compatibility?) with it...
> so Ardour as a *functioning* program (I have been doing digital audio
> for maybe 15 years, much of which was with Pro Tools, when I ran Mac
> OS, pre version 9.0), as is (the so-called "stable" version), is
> strictly a hypothetical, for me; point is, to reiterate, & emphasize,
> version 2.xx is not a useable program for me... I was hoping to see if
> there were issues that might have been resolved, so that I could
> reconsider utilizing Ardour.
>
> So if you are saying, even if you know better (re installation) & have
> problems where documentation is not (at the least) apparently
> available... too bad... or what? & are you really saying you (who ever
> "you" is) are not interested in some one actually trying to learn?
> That would be just too sad.
>

I just recently upgraded to f11 and installed the -devel packages and
ardour-3.0 compiled for me yesterday with no problems.

Maybe it's your base system that is too far out of date and you need to
upgrade that first before you can get ardour-3.0 to build smoothly.



Cheers.



Patrick Shirkey
Boost Hardware Ltd

> Henry
>
> Patrick Shirkey wrote:
>>
>> On 10/09/2009 07:20 AM, Henry W. Peters wrote:
>>> Is this an "official" position... ?
>>>
>>
>>
>> Pretty much yes.
>>
>> You will need to get the -dev or -devel versions of the deps that are
>> missing in order to compile.
>>
>>
>> Cheers.
>>
>>
>>
>> Patrick Shirkey
>> Boost Hardware Ltd
>>
>>
>>
>>

_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Lamar Owen]

On Thursday 08 October 2009 07:52:59 pm Henry W. Peters wrote:
> So if you are saying, even if you know better (re installation) & have
> problems where documentation is not (at the least) apparently
> available... too bad... or what?   & are you really saying you (who ever
> "you" is) are not interested in some one actually trying to learn? That
> would be just too sad.

I think the point you might be missing is that Ardour 3 is very much pre-alpha
and under heavy development.  My take on it was that only developers of Ardour
should be attempting to build Ardour 3 at the moment.  When a beta release is
available there will be an announcement, I would expect.

The developers are trying their hardest to get the development work done for
Ardour 3.0; honestly, handholding a fresh user/developer into the process
would distract from the work being done in the development.  And it's not a
'too bad, so sad' situation; it's simply that Ardour 3.0 is not suitable at
the moment for anyone but someone who is an Ardour developer.

And, FWIW, I am not an Ardour developer, but one who would love to be using
Ardour 3 myself.  Which is one reason I'm not distracting any Ardour
developers by asking questions about building Ardour 3.0 myself for normal use
(and it's not ready for normal use, at least that's what I keep seeing).

Currently 2.8.2 is the latest non-SVN release, and 2.0-ongoing is the stable
SVN.  The 3.0 SVN isn't stable (or even alpha, much less beta) yet.
_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Paul Davis]

On Thu, Oct 8, 2009 at 7:52 PM, Henry W. Peters <hwpeters@...> wrote:
  [ ... ]

Ardour 3.0 has not been declared ready for testing by anyone except
our inner core at this point. We are not interested in hand-holding
compilation issues. The problems you have with boost are probably
because your system installs a versioned include dir for boost, in
contravention of all boost policy.

What is it about 2.X that makes it usable for you?

> So if you are saying, even if you know better (re installation) & have
> problems where documentation is not (at the least) apparently available...
> too bad... or what?   & are you really saying you (who ever "you" is) are
> not interested in some one actually trying to learn? That would be just too
> sad.

What I am saying is that if your linux development skills are not up
to solving this sort of problem for yourself, then no, you are not
part of the current intended audience for 3.0, which has not even
entered alpha testing yet.

--p
_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Paul Davis]

On Thu, Oct 8, 2009 at 8:14 PM, Lamar Owen <lowen@...> wrote:

> On Thursday 08 October 2009 07:52:59 pm Henry W. Peters wrote:
>> So if you are saying, even if you know better (re installation) & have
>> problems where documentation is not (at the least) apparently
>> available... too bad... or what?   & are you really saying you (who ever
>> "you" is) are not interested in some one actually trying to learn? That
>> would be just too sad.
>
> I think the point you might be missing is that Ardour 3 is very much pre-alpha
> and under heavy development.  My take on it was that only developers of Ardour
> should be attempting to build Ardour 3 at the moment.  When a beta release is
> available there will be an announcement, I would expect.

all true. but even beyond that, we are not ever going to "fix"
ardour's build process to accomodate distributions that install
/usr/include/boost-1.0.31  and not /usr/include/boost (for example)
....
_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[sh0099]

Henry W. Peters schrieb:
>
> I have built (say) Ardour 2.xx quite a few times... struggling with
> installation of the dependencies, etc., with some differing versions
> of my distro (Ubuntu), got the program to run, but had digital audio
> input  problems (probably sound card, etc., compatibility?) with it...
i personaly (unoffical) would not expect that input problems get solfed
with ardour3. this sounds more like a jack thing... can you describe
your problem you had with ardour2... in more detail.
(i hope i am right when i say that ardour3 has no new audio
input/output/recording/playback-engine ... )

greetings from the unofficial olaf

p.s.: paul, it seams that you (work to much and) care to much about
things you don't want to care about, be healthy and do only(!) what you
want.
_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Jörn Nettingsmeier-5]

hi henry!

Henry W. Peters wrote:

> I have built (say) Ardour 2.xx quite a few times... struggling with
> installation of the dependencies, etc., with some differing versions of
> my distro (Ubuntu), got the program to run, but had digital audio input
> problems (probably sound card, etc., compatibility?) with it... so
> Ardour as a *functioning* program (I have been doing digital audio for
> maybe 15 years, much of which was with Pro Tools, when I ran Mac OS, pre
> version 9.0), as is (the so-called "stable" version), is strictly a
> hypothetical, for me; point is, to reiterate, & emphasize, version 2.xx
> is not a useable program for me...

that is unfortunate. but you are following the wrong lead.

if your sound hardware does not work, then it's a JACK or ALSA problem.
if you cared to elaborate on what hardware you use and the problems you
are having, this might be fixable.

you should not have any hopes for ardour3 to give you a usable system at
this point. it's not even alpha. what paul was hinting at was: a3 will
be so scary to actually use that those build problems are just a
friendly way of saying: if you can't solve this, you should not be
wasting time with a3 at this point.

> I was hoping to see if there were
> issues that might have been resolved, so that I could reconsider
> utilizing Ardour.

please do, but note that hardware problems are usually orthogonal to ardour.

> So if you are saying, even if you know better (re installation) & have
> problems where documentation is not (at the least) apparently
> available... too bad... or what?   & are you really saying you (who ever
> "you" is) are not interested in some one actually trying to learn? That
> would be just too sad.

no, it's not. ardour3 is not ready for end users yet, and it's so much
in flux that it would be a waste of time to even address (let alone fix)
the issues you were having.
it's not a finished product. it's a scary contraption of wires, glass
tubes, green bubbly liquids and lightning discharge, the odd brain
floating in a formaldehyde jar, in an illegal basement facility in outer
transsilvania with maniacs in ragged grey lab coats dancing around by
the light of a sizzling carbide lamp.
that said, you may see why it's a bad idea to call igor to the door to
ask for the customer relationship manager :-D

please don't take offense, and do reconsider ardour2 for productive work.


best,

jörn




--
Jörn Nettingsmeier

Meister für Veranstaltungstechnik

Audio and event engineer
Ambisonic surround recordings

http://stackingdwarves.net
[phone]


_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org

[Jörn Nettingsmeier-5]

Henry W. Peters wrote:

> P.s., I do get sound from my MiaMidi (Echo Corp.) sound card via its'
> driver & alsa... /just not in Ardour/ (i.e., I use Audacity (which has
> some _other_ problems), & RealAudio (Helix project), & the tests work in
> the sound control panel, in Ubunto 9.04, & it works fine in Windows
> XP... though I know that is not relevant to the Linux needs).

well, it does establish that the hardware is ok.
so you a functional ALSA support. the question is: does it run in with
jack? i believe you said it does elsewhere. did you ever get it to play
sound using a jack application?

> P.p.s., if you do not have the time (for what ever reason), etc., let me
> know, I can put this question to the list.

i took the liberty of moving this discussion back on the list, so that
others can participate and the result eventually hits the archives.

> In file included from /usr/include/boost/dynamic_bitset.hpp:15,
>                  from libs/ardour/ardour/session.h:32,
>                  from libs/ardour/ardour/audio_diskstream.h:39,
>                  from libs/ardour/audio_diskstream.cc:44:
> /usr/include/boost/dynamic_bitset/dynamic_bitset.hpp: In member function
> ‘size_t boost::dynamic_bitset<Block, Allocator>::count() const’:
> /usr/include/boost/dynamic_bitset/dynamic_bitset.hpp:1021: error: ‘mode’
> cannot appear in a constant-expression
> /usr/include/boost/dynamic_bitset/dynamic_bitset.hpp:1021: error:
> template argument 1 is invalid
> /usr/include/boost/dynamic_bitset/dynamic_bitset.hpp:1021: error:
> expected `>' before ‘*’ token
> /usr/include/boost/dynamic_bitset/dynamic_bitset.hpp:1021: error:
> expected `(' before ‘*’ token
> /usr/include/boost/dynamic_bitset/dynamic_bitset.hpp:1021: error:
> expected primary-expression before ‘>’ token
> scons: *** [libs/ardour/audio_diskstream.os] Error 1
> scons: building terminated because of errors.
> henry@henry-heron:~/ardour-2.8.3$

this looks like a c++ compiler incompatibility to me. recent gcc
releases need some explicit include declarations that used to be
implicit in older versions. try and get an updated version of boost, or
try to google one of those error messages - often, you will find that
the appropriate fixes are being discussed somewhere.
this problem is not ardour-related.

if you can't solve this, try and find an ardour package for your distro,
to see if it suits your needs. once you know it's what you're after, you
can invest more time to get a full build environment going and try to
compile the very latest release.

best,

jörn




--
Jörn Nettingsmeier

Meister für Veranstaltungstechnik

Audio and event engineer
Ambisonic surround recordings

http://stackingdwarves.net
[phone]

_______________________________________________
Ardour-Users mailing list
ardour-users@...
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org