[LAU] Beast 0.8.0 Release

Florian Paul Schmidt mista.tapas at gmx.net
Wed Mar 27 08:44:53 UTC 2013


On 03/27/2013 09:22 AM, Florian Paul Schmidt wrote:
> On 03/27/2013 09:10 AM, Florian Paul Schmidt wrote:
>> On 03/25/2013 11:51 AM, Florian Paul Schmidt wrote:
>>> On 03/25/2013 02:02 AM, Tim Janik wrote:
>>>> CALL FOR MUSICIANS
>>>> ==================
>>>> If you are a musician and interested in Free Software, the Beast 
>>>> project
>>>> needs your input. You can contribute with testing, feature feedback,
>>>> demos and tutorials. Please see our website: http://beast.testbit.eu/
>>>>
>>>> BEAST RELEASE
>>>> =============
>>>> BEAST version 0.8.0 is available for download at:
>>>>    http://beast.testbit.eu/beast-ftp/v0.8/
>>>
>>> Hi,
>>>
>>> I tracked down dependencies. One of them seems to be rapicorn. Sadly 
>>> it's not building. I started to get into fixing the build (missing 
>>> #includes for C lib stuff, unistd.h, sys/types.h, etc..). Got stuck 
>>> here (and got kind of tired of fixing the includes ;D):
>>>
>>
>>
>> OK, I also tried rapicorn git. I'm no autotools guy, so I don't know 
>> how to fix this one either:
>>
>> configure.in:498: warning: AC_PYTHON_DEVEL is m4_require'd but not 
>> m4_defun'd
>> configure.in:344: RAPICORN_ROPE_REQUIREMENTS is expanded from...
>> configure.in:498: the top level
>> configure.in:351: error: possibly undefined macro: AC_PYTHON_DEVEL
>>       If this token and others are legitimate, please use 
>> m4_pattern_allow.
>>       See the Autoconf documentation.
>
> For everyone else trying: On ubuntu this was fixed by installing the 
> package autoconf-archive. And then the rapicorn build actually succeeds..
>
> Flo
>

OK, and I finally succeeded in building beast-0.8. Note though that I 
had to

LD_LIBRARY_PATH=/usr/local/lib make

and

LD_LIBRARY_PATH=/usr/local/lib make install

Running beast then fails, too, with

/usr/local/bin/beast-0.8.0: error while loading shared libraries: 
librapicorn1303.so.0: cannot open shared object file: No such file or 
directory

Runnning sudo ldconfig seems to fix it though (and in retrospect might 
have fixed the build errors above, too ;D)

Flo

-- 
Florian Paul Schmidt
http://fps.io



More information about the Linux-audio-user mailing list