|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
Stuck at 2.8.0 ??? (for now)I think if I had a newer distribution than Mandriva 2007.0 that I wouldn't be having these problems. Not being able to upgrade ardour would be yet one more reason to force me to upgrade. Maybe someone can tell me if I have another way out. I saw an email that says that 2.8.0 has a bug which can cause file losses related to cleaning up unused files, and that the trouble is fixed in later versions. I built 2.8.0 just fine. But, 2.8.1 and 2.8.2 compile OK but scons won't complete the install step because of bug ID 0002718, http://tracker.ardour.org/view.php?id=2718 like so mo_builder(["gtk2_ardour/nn_NO.mo"], ["gtk2_ardour/nn_NO.po"]) msgfmt: gtk2_ardour/nn_NO.po: some header fields still have the initial default value msgfmt: found 1 fatal error scons: *** [gtk2_ardour/nn_NO.mo] Error 1 I see this is fixed in 2.0-ongoing, and I grabbed today's SVN version 5756. I verified that I have all of the tools and libraries of the versions required of Ardour 2.0 here http://www.ardour.org/building Running scons told me that I needed to grab a newer libsndfile. I have 1.0.17 installed. It looks like 2.0-ongoing (and 2.8.3?) needs 1.0.18 or better. So, I grabbed 1.0.18 (also tried 1.0.19 and 1.0.20) and then I ran into this problem: Making all in GSM610 make[3]: Entering directory `/home/local/src/INCOMING/BUILD/libsndfile-1.0.18/src/GSM610' /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fomit-frame-pointer -march=i586 -mtune=pentiumpro -fasynchronous-unwind-tables -std=gnu99 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -funsigned-char -Wstrict-prototypes -Wmissing-prototypes -Waggregate-return -Wcast-align -Wcast-qual -Wnested-externs -Wshadow -Wbad-function-cast -Wwrite-strings -pipe -MT add.lo -MD -MP -MF .deps/add.Tpo -c -o add.lo add.c /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fomit-frame-pointer -march=i586 -mtune=pentiumpro -fasynchronous-unwind-tables -std=gnu99 -Wall -Wextra -Wdeclaration-after-statement -Wpointer-arith -funsigned-char -Wstrict-prototypes -Wmissing-prototypes -Waggregate-return -Wcast-align -Wcast-qual -Wnested-externs -Wshadow -Wbad-function-cast -Wwrite-strings -pipe -MT decode.lo -MD -MP -MF .deps/decode.Tpo -c -o decode.lo decode.c ../../libtool: line 780: X--tag=CC: command not found ../../libtool: line 780: X--tag=CC: command not found Which seems related to http://www.mail-archive.com/libtool@.../msg10239.html which is a pretty good discussion. Then I tried something probably stupid, but maybe it would work. I changed the sndfile requirement in SConstruct from 1.0.18 to 1.0.17 which caused the scons build to fail after completing more steps, at this point g++ -o libs/ardour/session_export.os -c -O3 -fomit-frame-pointer -ffast-math -fstrength-reduce -pipe -DARCH_X86 -mmmx -m3dnow -march=i686 -msse -mfpmath=sse -DUSE_XMMINTRIN -DBUILD_SSE_OPTIMIZATIONS -Wall -DHAVE_LIBLO -Ilibs -DENABLE_NLS -D_REENTRANT -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Ilibs -pthread -DUSE_RUBBERBAND -Woverloaded-virtual -DPACKAGE=\"libardour2\" -DLIBSIGC_DISABLE_DEPRECATED -DDATA_DIR=\"/usr/share\" -DMODULE_DIR=\"/usr/lib\" -DVAMP_DIR=\"/usr/lib/ardour2/vamp\" -DCONFIG_DIR=\"/etc\" -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_JACK_CLIENT_OPEN -DHAVE_JACK_RECOMPUTE_LATENCIES -DHAVE_JACK_VIDEO_SUPPORT -DHAVE_JACK_PORT_ENSURE_MONITOR -DHAVE_WORDEXP -DHAVE_SYS_VFS_H -fPIC -Ilibs/pbd -I/usr/include/glib-2.0 -Ilibs/surfaces/control_protocol -Ilibs/midi++2 -Ilibs/vamp-sdk -Ilibs/sigc++2 -Ilibs/glibmm2 -I/usr/lib/glib-2.0/include -Ilibs/ardour -Ilibs/rubberband -I/usr/include/libxml2 libs/ardour/session_export.cc libs/ardour/session_export.cc: In member function ?int ARDOUR::AudioExportSpecification::prepare(nframes_t, nframes_t)?: libs/ardour/session_export.cc:173: error: ?SF_FORMAT_OGG? was not declared in this scope scons: *** [libs/ardour/session_export.os] Error 1 scons: building terminated because of errors. At this point I think I have two choices: - Continue with 2.8.0 and avoid cleaning up my old files. - Upgrade to a modern distribution which has or can build the components required to build newer versions of ardour. Any comments? If you made it this far, thanks for reading! Cheerio.... -- Kevin _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Stuck at 2.8.0 ??? (for now)On Thu, Oct 8, 2009 at 1:56 PM, Kevin Cosgrove <kevinc@...> wrote:
> At this point I think I have two choices: > > - Continue with 2.8.0 and avoid cleaning up my old files. > - Upgrade to a modern distribution which has or can build the > components required to build newer versions of ardour. that is a correct summary. Using ardour with libsndfile 1.0.17 will cause real problems under some scenarios - 1.0.18 is the first sndfile release to include patches that i provided to erik. _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
|
|
Re: Stuck at 2.8.0 ??? (for now)On 8 October 2009 at 14:04, Paul Davis <paul@...> wrote: > On Thu, Oct 8, 2009 at 1:56 PM, Kevin Cosgrove <kevinc@...> wrote: > > At this point I think I have two choices: > > - Continue with 2.8.0 and avoid cleaning up my old files. > > - Upgrade to a modern distribution which has or can build the > > components required to build newer versions of ardour. > > that is a correct summary. I found a work around, which will give me just a little bit more time to do my distribution upgrade (I've already got a Fedora 10 install disc burned) at a comfortable pace. I just deleted the translation file that was causing me troubles with the build, e.g.: rm gtk2_ardour/po/*NO* My 2.8.2 build was successful with no other changes. Ardour also appears to run. But, I haven't exercised it enough to tell if I broke something. I imagine removing the NO translation might be reasonably benign, if that's not the language I need. > Using ardour with libsndfile 1.0.17 will cause real problems > under some scenarios - 1.0.18 is the first sndfile release to > include patches that i provided to erik. Then I'll use ardour only with the libsndfile version required by that version of ardour. Thanks for keeping me from going down a bad road. Cheerio.... -- Kevin _______________________________________________ Ardour-Users mailing list ardour-users@... http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org |
| Free embeddable forum powered by Nabble | Forum Help |