[ardour-users] any help for a freebsd & want-to-be ardor user?

Taybin Rutkin taybin at earthlink.net
Mon Apr 18 14:50:21 PDT 2005

I bet it's related to the jack_frames_t casting.  I have no idea what a fix for it is.  Ardour doesn't use ALSA directly.  It uses Jack to talk to the hardware.


-----Original Message-----
From: Brian Howe <bwhowe at gmail.com>
Sent: Apr 18, 2005 2:42 PM
To: Paul Davis <paul at linuxaudiosystems.com>
Cc: ardour-users-ardour.org at lists.ardour.org
Subject: Re: [ardour-users] any help for a freebsd & want-to-be ardor user?

I was googling for an answer to the lrintf issue and saw a reference to 
ffmpeg listed. It was not the exact problem I was having but it was more of 
a lead than I had at the time. I installed ffmpeg and that resolved the 
lrintf problem. Not being a programmer by nature, I cannot explain. However, 
it does seem to have resolved the issues I had... for that problem.

Does the "__builtin_types_compatible_p" problem look like it could be 
related to ALSA? Since this is a freebsd box and therefor not able to use 
ALSA, it may be a result of that? Sorry for postulating wildly here, but I'm 
completely at a loss.

On 4/18/05, Paul Davis <paul at linuxaudiosystems.com> wrote:
> >session_export.cc:221: error: `__builtin_types_compatible_p' 
> undeclared=20
> >(first use this function)
> >session_export.cc:221: error: (Each undeclared identifier is reported 
> only=
> [ ... ]
> these errors are completely unfamiliar to me. i have no idea where
> they come from. i do not recall them ever being reported by linux
> users. also, "lrintf error was due to a missing ffmpeg" is completely
> wrong. lrintf() is a C library function. ffmpeg has nothing to do with
> it unless updating and/or installing it also updated your C library.
> --p

Brian Howe
- press to test
- release to detonate
The shortest distance between 
two puns is a straight line

More information about the Ardour-Users mailing list