[Ardour-Dev] Ardour3-3.1 does not build on FreeBSD i386 10.0

[outro pessoa]

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.

In wscript conf.check_cc does not look in the previously mentioned
locations. FreeBSD uses clang as the default compiler for the system.



On Sun, Jun 2, 2013 at 11:42 PM, outro pessoa <outro.pessoa at gmail.com>wrote:

> 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.
> I'm going to test an idea.
>
>
> On Sun, Jun 2, 2013 at 5:22 AM, Paul Davis <paul at linuxaudiosystems.com>wrote:
>
>> 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.
>>
>>
>> On Sun, Jun 2, 2013 at 12:49 AM, outro pessoa <outro.pessoa at gmail.com>wrote:
>>
>>> Okay
>>>
>>> 1. www.nerds.de This site has an application called ipmidi. That is why
>>> I had stated  that ipmidi was not available for FreeBSD.
>>>
>>> 2. I have searched the code and can not find anything to match the error
>>> in the attached file.
>>>
>>>
>>> On Sun, May 26, 2013 at 4:08 PM, outro pessoa <outro.pessoa at gmail.com>wrote:
>>>
>>>> Okay ipmidi is not available for FreeBSD. I had to look up the
>>>> information.
>>>> 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.
>>>>
>>>>
>>>> On Sun, May 26, 2013 at 3:57 PM, outro pessoa <outro.pessoa at gmail.com>wrote:
>>>>
>>>>> Configure was redone without static libraries.
>>>>> Error seems to be in libmidi preprocessor pp/++ files.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, May 26, 2013 at 1:54 PM, Paul Davis <
>>>>> paul at linuxaudiosystems.com> wrote:
>>>>>
>>>>>> --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.
>>>>>>
>>>>>> put more simply: you cannot use this option to build a working
>>>>>> version of ardour.
>>>>>>
>>>>>>
>>>>>> On Sun, May 26, 2013 at 1:37 PM, outro pessoa <outro.pessoa at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Add this to FreeBSD install:
>>>>>>> Compile without lv2 until I can see what the problem is with the
>>>>>>> search method.
>>>>>>> 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"
>>>>>>>
>>>>>>> Now, Ardour3-3.1 will build but it does not install.
>>>>>>>
>>>>>>> Build failed
>>>>>>>   -> task in 'libmidipp' failed (exit status 1):
>>>>>>>        {task 689150380: cxx ipmidi_port.cc -> ipmidi_port.cc.1.o}
>>>>>>>
>>>>>>>
>>>>>>> On Sat, May 25, 2013 at 3:28 PM, outro pessoa <
>>>>>>> outro.pessoa at gmail.com> wrote:
>>>>>>>
>>>>>>>> Took care of that.
>>>>>>>> Eliminated the dlopen from the wscript.
>>>>>>>> Really not  too sure about the GMP and MPFR selection. At what
>>>>>>>> point would the sound card crap out?
>>>>>>>> Here looking at using an i386 for wine and having NFS export the
>>>>>>>> necessary directories, libraries, etc to a powerpc machine.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, May 24, 2013 at 1:22 PM, Paul Davis <
>>>>>>>> paul at linuxaudiosystems.com> wrote:
>>>>>>>>
>>>>>>>>> boost does not provide pkg-config info. it is really pathetic.
>>>>>>>>>
>>>>>>>>> you need to use system-level stuff to make boost discoverable
>>>>>>>>> (e.g. symlinks) etc. etc.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, May 23, 2013 at 4:38 AM, outro pessoa <
>>>>>>>>> outro.pessoa at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> 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.
>>>>>>>>>>
>>>>>>>>>>  The wscript file does not contain enough information to change
>>>>>>>>>> the variable and search path with vi.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> ardour-dev mailing list
>>>>>>>>>> ardour-dev at lists.ardour.org
>>>>>>>>>> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> ardour-dev mailing list
>>>>>>> ardour-dev at lists.ardour.org
>>>>>>> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> ardour-dev mailing list
>>> ardour-dev at lists.ardour.org
>>> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-dev-ardour.org/attachments/20130603/d010ccd0/attachment-0002.htm>