Re: Ardour3-3.1 does not build on FreeBSD i386 10.0
Paul Davis <[email protected]>
| Newsgroups | gmane.comp.audio.ardour.devel |
|---|---|
| Message-ID | <CAFa_cKmED4C8JgKix4JpGgWZ4WS0ObuMqWjQ77YORBsO-f8YJg@mail.gmail.com> |
the bug you referenced was related to boost and their deprecation/handling of certain things in boost::system. we certainly encountered this issue with a3 on OS X and linux, and it was solved by ensuring that -DBOOST_NO_SYSTEM_DEPRECATED was correctly defined, which it is (hard-coded) in the top level wscript file. perhaps you are talking about some other problem. On Thu, Jun 20, 2013 at 10:27 PM, outro pessoa <[email protected]>wrote: > The wrapper/Makefile is something that I can deal with. The current > problem is, "How do I eliminate the constant reference to a non existing > set of library files?" > I sent the Makefile so that you and the rest of the developers would see > the direction I was going in compiling the old beta release. Each of the > flags and arguments show a positive result in the building of the > application. > > I need to remember the file that has the {apple}{freebsd} arguments. The > build was customized somewhat. > > If need be, the beta can be rebuilt with -vvv. Once the beta builds > properly, the move can go to the current release. > > > > > > On Thu, Jun 20, 2013 at 10:07 PM, Paul Davis <[email protected]>wrote: > >> sorry, but wrappers around our wscript files are not something i'm going >> to spend any time on at all. >> >> >> On Thu, Jun 20, 2013 at 9:23 PM, outro pessoa <[email protected]>wrote: >> >>> I'm sending the Makefile. It contains the C and CXX flags. Included are >>> two files: opop.txt.bz2 and op22.txt.bz2. The former is before the C/CXX >>> flags and the latter is after. >>> >>> >>> On Thu, Jun 20, 2013 at 8:55 PM, Paul Davis <[email protected]>wrote: >>> >>>> this should already be fixed by the use of >>>> '-DBOOST_SYSTEM_NO_DEPRECATED' for CFLAGS and CXXFLAGS. >>>> >>>> >>>> On Thu, Jun 20, 2013 at 6:31 PM, outro pessoa <[email protected]>wrote: >>>> >>>>> I ran into a problem similar to this one: >>>>> https://bugs.gentoo.org/show_bug.cgi?id=425578 with the same type of >>>>> results. Can this be approached from a configuration directory such as >>>>> $PORTS_PATH/ardour-betaX or will it need to be done within the top level >>>>> wscript file? I am aware that the old Scons build system was used and is >>>>> referenced; but, I am looking for a solution similar to the problem I am >>>>> encountering. >>>>> >>>>> Thanks and all for the help and advice so far. >>>>> >>>>> >>>>> On Tue, Jun 18, 2013 at 7:38 PM, Paul Davis < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Jun 18, 2013 at 6:46 PM, outro pessoa <[email protected] >>>>>> > wrote: >>>>>> >>>>>>> I set clang, clang++, and clang-cpp with the full paths in the >>>>>>> $PORT/Makefile. >>>>>>> Another question... >>>>>>> "$ ./ardev >>>>>>> .: cannot open ./../build/gtk2_ardour/ardev_common_waf.sh: No such >>>>>>> file or directory >>>>>>> $ " >>>>>>> >>>>>>> >>>>>>> http://pkgsubmit.mageia.org/autobuild/cauldron/x86_64/core/log/ardour3-3.0-0.13700.2.mga3.src.rpm/build.0.20130209132846.log >>>>>>> had the exact same thing. The page is gone though. >>>>>>> >>>>>>> Does this require a link to a top level directory? >>>>>>> >>>>>> >>>>>> no, it means that your build didn't work. >>>>>> ../build/gtk2_ardour/ardev_common_waf.sh is a build target. >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >> > _______________________________________________ ardour-dev mailing list [email protected] http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org