<div dir="ltr"><div>Since you and others had to build waf with certain flags, what was the script? It may work better if waf is first built on FreeBSD as you had done with Linux and OSX. That would help a small bit.<br></div>
I've sent in a ticket to the googlecode/waf about the build incident.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 3, 2013 at 12:17 AM, outro pessoa <span dir="ltr"><<a href="mailto:outro.pessoa@gmail.com" target="_blank">outro.pessoa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Separating by commas does not work. The header dlfcn.h is located in /usr/include. If I add the switch of --also-include=/usr/local/include/ to ./waf configure, the --boost-include=$PATH is not needed. Since I don't see the variables in wscript, I assume that they exist in the .waf*/*/ path.<br>
<br></div>In wscript conf.check_cc does not look in the previously mentioned locations. FreeBSD uses clang as the default compiler for the system. <br><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">
On Sun, Jun 2, 2013 at 11:42 PM, outro pessoa <span dir="ltr"><<a href="mailto:outro.pessoa@gmail.com" target="_blank">outro.pessoa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>I've noticed that dlopen.c is part of libtool. This is located in /usr/local/share and not in the standard library locations. The other functions are located in the /usr/include directory.<br></div>
I'm going to test an idea.<br></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jun 2, 2013 at 5:22 AM, Paul Davis <span dir="ltr"><<a href="mailto:paul@linuxaudiosystems.com" target="_blank">paul@linuxaudiosystems.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">those messages suggest to me that some other head file is required. ardour does not require a platform to provide IPMIDI - ardour has the code for it as part of its own source. but it does need to be able to use all the macros and symbols that a typical multicast app would require.</div>
<div><div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jun 2, 2013 at 12:49 AM, outro pessoa <span dir="ltr"><<a href="mailto:outro.pessoa@gmail.com" target="_blank">outro.pessoa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><h3>Okay</h3><p>1. <a href="http://www.nerds.de" target="_blank">www.nerds.de</a> This site has an application called ipmidi. That is why I had stated that ipmidi was not available for FreeBSD.</p>
<p>2. I have searched the code and can not find anything to match the error in the attached file.<br>
</p></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, May 26, 2013 at 4:08 PM, outro pessoa <span dir="ltr"><<a href="mailto:outro.pessoa@gmail.com" target="_blank">outro.pessoa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Okay ipmidi is not available for FreeBSD. I had to look up the information.<br></div>About how many hidden flags are in the wscript file? It looks like I'll need to remove the ones that cannot be built on this OS architecture.<br>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, May 26, 2013 at 3:57 PM, outro pessoa <span dir="ltr"><<a href="mailto:outro.pessoa@gmail.com" target="_blank">outro.pessoa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Configure was redone without static libraries.<br></div></div><div>Error seems to be in libmidi preprocessor pp/++ files.<br>
</div><br><br></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sun, May 26, 2013 at 1:54 PM, Paul Davis <span dir="ltr"><<a href="mailto:paul@linuxaudiosystems.com" target="_blank">paul@linuxaudiosystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">--internal-static-libs is experimental and will almost certainly not work. It is a work in progress that is expected to be months away from being completed, and was intended to be used only when building Ardour for binary distribution. There is a lot of code in ardour that is known to be completely, 100% broken when this option is used - it will compile but the program will crash either at startup or during execution.<div>
<br></div><div>put more simply: you cannot use this option to build a working version of ardour.</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, May 26, 2013 at 1:37 PM, outro pessoa <span dir="ltr"><<a href="mailto:outro.pessoa@gmail.com" target="_blank">outro.pessoa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Add this to FreeBSD install:<br></div>Compile without lv2 until I can see what the problem is with the search method.<br>
</div>Ardour3-3.1 compiles with "./waf configure --boost-includes=/usr/local/include/boost/ --also-includes=/usr/local/include/ --internal-static-libs --also-libdir=/usr/local/lib/ --freebie --no-lv2"<br>
<br></div>Now, Ardour3-3.1 will build but it does not install.<br><br></div>Build failed <br></div> -> task in 'libmidipp' failed (exit status 1):<br></div> {task 689150380: cxx ipmidi_port.cc -> ipmidi_port.cc.1.o}<br>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, May 25, 2013 at 3:28 PM, outro pessoa <span dir="ltr"><<a href="mailto:outro.pessoa@gmail.com" target="_blank">outro.pessoa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Took care of that.<br></div>Eliminated the dlopen from the wscript.<br></div>Really not too sure about the GMP and MPFR selection. At what point would the sound card crap out? <br>
</div>Here looking at using an i386 for wine and having NFS export the necessary directories, libraries, etc to a powerpc machine. <br>
<br><br></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 24, 2013 at 1:22 PM, Paul Davis <span dir="ltr"><<a href="mailto:paul@linuxaudiosystems.com" target="_blank">paul@linuxaudiosystems.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">boost does not provide pkg-config info. it is really pathetic.<div><br></div><div>you need to use system-level stuff to make boost discoverable (e.g. symlinks) etc. etc.</div>
</div><div class="gmail_extra"><br>
<br><div class="gmail_quote"><div>On Thu, May 23, 2013 at 4:38 AM, outro pessoa <span dir="ltr"><<a href="mailto:outro.pessoa@gmail.com" target="_blank">outro.pessoa@gmail.com</a>></span> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<div dir="ltr"><div>Boost 1.52 and subsequent boost based applications & libraries- also 1.52- are installed yet "./waf configure " will not recognize even with boost and other include flags enabled.<br><br>
</div>
The wscript file does not contain enough information to change the variable and search path with vi.<br><br><br></div>
<br></div>_______________________________________________<br>
ardour-dev mailing list<br>
<a href="mailto:ardour-dev@lists.ardour.org" target="_blank">ardour-dev@lists.ardour.org</a><br>
<a href="http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org" target="_blank">http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
ardour-dev mailing list<br>
<a href="mailto:ardour-dev@lists.ardour.org" target="_blank">ardour-dev@lists.ardour.org</a><br>
<a href="http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org" target="_blank">http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
ardour-dev mailing list<br>
<a href="mailto:ardour-dev@lists.ardour.org" target="_blank">ardour-dev@lists.ardour.org</a><br>
<a href="http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org" target="_blank">http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>