PulseAudio Team:
The decision was made recently to integrate PulseAudio into Solaris, so
that is pretty exciting. I am not exactly sure when it will integrate.
At the moment, I am just working to get it building and working okay.
I have encountered a few build issues, and I am wondering if Pul
2011/10/15 Brian Cameron :
>
> PulseAudio Team:
>
> The decision was made recently to integrate PulseAudio into Solaris, so
> that is pretty exciting. I am not exactly sure when it will integrate.
> At the moment, I am just working to get it building and working okay.
Indeed, exciting.
> I have
On Sat, 15.10.11 16:29, Brian Cameron (brian.came...@oracle.com) wrote:
Heya,
> The decision was made recently to integrate PulseAudio into Solaris, so
> that is pretty exciting. I am not exactly sure when it will integrate.
> At the moment, I am just working to get it building and working okay.
'Twas brillig, and Lennart Poettering at 17/10/11 02:48 did gyre and gimble:
>> 3) On Solaris, the PulseAudio GConf module does not compile since the
>>"module_info" structure defined in the PulseAudio code conflicts
>>with a structure with the same name in /usr/include/sys/stream.h.
>>
On Mon, 17.10.11 10:33, Colin Guthrie (gm...@colin.guthr.ie) wrote:
>
> 'Twas brillig, and Lennart Poettering at 17/10/11 02:48 did gyre and gimble:
> >> 3) On Solaris, the PulseAudio GConf module does not compile since the
> >>"module_info" structure defined in the PulseAudio code conflicts
Lennart:
The decision was made recently to integrate PulseAudio into Solaris, so
that is pretty exciting. I am not exactly sure when it will integrate.
At the moment, I am just working to get it building and working okay.
On which backend? OSS? Note that OSS support in PA never came close in
2011/10/17 Brian Cameron :
>> (And yupp, here too this sounds like a bug if clients ever end up
>> linking against libpulsecore. That library is not API stable, and things
>> will end in desaster if this happens).
>
> Now that I am looking at this more closely, I suspect that my attached
> patch to
'Twas brillig, and Lennart Poettering at 17/10/11 12:30 did gyre and gimble:
> On Mon, 17.10.11 10:33, Colin Guthrie (gm...@colin.guthr.ie) wrote:
>
>>
>> 'Twas brillig, and Lennart Poettering at 17/10/11 02:48 did gyre and gimble:
3) On Solaris, the PulseAudio GConf module does not compile s
2011/10/17 Brian Cameron :
> I found this issue when I try to build PA clients. For example, when
> PulseAudio tries to build pactl, I see these errors. I see similar
> errors trying to build any PA client:
>
> Undefined first referenced
> symbol
2011/10/17 Brian Cameron :
> I found this issue when I try to build PA clients. For example, when
> PulseAudio tries to build pactl, I see these errors. I see similar
> errors trying to build any PA client:
>
> Undefined first referenced
> symbol
Maarten:
I updated the patch as attached to address your comments. This
has "#ifdef __sun" used more properly and a comment.
Also note that I added a comment to the bug to answer your question
that LOG_INFO and LOG_WARNING are defined in the system syslog.h
header, not in PulseAudio.
Brian
Maarten:
Thanks for the pointers, you helped me figure out how to get PulseAudio
building on Solaris without libpulsecommon needing to link against
libpulsecore.
The issue seems to be caused by the fact that libpulsecommon includes
pulsecore/pstream.c, which includes pulsecore/core-scache.h to
2011/10/19 Brian Cameron :
> The issue seems to be caused by the fact that libpulsecommon includes
> pulsecore/pstream.c, which includes pulsecore/core-scache.h to gain access
> to the PA_SCACHE_ENTRY_SIZE_MAX #define.
>
> Moving this #define so it is in pulsecore/memchunk.h (a header already
> ass
Maarten:
Thanks for trying this workaround and confirming that this is indeed
the problem.
(core-cache.h includes core.h, sink.h and others, which define objects
using PA_DECLARE_PUBLIC_CLASS, that cause trouble when not linked in.
I'm wondering why this is no problem on Linux)
Probably becau
14 matches
Mail list logo
