Re: [ports-gcc] Unbreak and fix audio/audacious-plugins

2019-05-24 Thread Charlene Wendling
On Fri, 24 May 2019 21:47:36 +0200 Christian Weisgerber wrote: > Christian Weisgerber: > > > > So i've stopped sndiod in the chroot, restarted sndiod on my main > > > install, then started audacious in the chroot: the white noise > > > issue is back. > > > > The chrooted audacious doesn't

Re: [ports-gcc] Unbreak and fix audio/audacious-plugins

2019-05-24 Thread Christian Weisgerber
Christian Weisgerber: > > So i've stopped sndiod in the chroot, restarted sndiod on my main > > install, then started audacious in the chroot: the white noise > > issue is back. > > The chrooted audacious doesn't see the /tmp/sndio/sock0 socket. It > acts as if there was no sndiod running.

Re: [ports-gcc] Unbreak and fix audio/audacious-plugins

2019-05-24 Thread Christian Weisgerber
Charlene Wendling: > So i've stopped sndiod in the chroot, restarted sndiod on my main > install, then started audacious in the chroot: the white noise > issue is back. The chrooted audacious doesn't see the /tmp/sndio/sock0 socket. It acts as if there was no sndiod running. libsndio will

Re: [ports-gcc] Unbreak and fix audio/audacious-plugins

2019-05-24 Thread Jeremie Courreges-Anglas
On Fri, May 24 2019, Charlene Wendling wrote: > Hi, > > On Fri, 24 May 2019 13:41:32 +0200 > Christian Weisgerber wrote: > >> Charlene Wendling: >> >> > - It doesn't build with ports-gcc (macppc [0], sparc64 [1]) >> > >> > The problem here is again a macro vs function issue. I've applied >>

Re: [ports-gcc] Unbreak and fix audio/audacious-plugins

2019-05-24 Thread Charlene Wendling
Hi, On Fri, 24 May 2019 13:41:32 +0200 Christian Weisgerber wrote: > Charlene Wendling: > > > - It doesn't build with ports-gcc (macppc [0], sparc64 [1]) > > > > The problem here is again a macro vs function issue. I've applied > > the same thing upstream still does on audacious proper

Re: [ports-gcc] Unbreak and fix audio/audacious-plugins

2019-05-24 Thread Christian Weisgerber
Charlene Wendling: > - It doesn't build with ports-gcc (macppc [0], sparc64 [1]) > > The problem here is again a macro vs function issue. I've applied > the same thing upstream still does on audacious proper [2]: > undef'ing feof(3). That part is fine. > - At least on macppc, it does

[ports-gcc] Unbreak and fix audio/audacious-plugins

2019-05-16 Thread Charlene Wendling
Hi, audacious-plugins has two issues, that still exist as of 3.10: - It doesn't build with ports-gcc (macppc [0], sparc64 [1]) The problem here is again a macro vs function issue. I've applied the same thing upstream still does on audacious proper [2]: undef'ing feof(3). Renaming

fix: audio/audacious-plugins

2009-01-31 Thread Tobias Ulmer
fix audioplayer with unspeakable name, fallout of earlier audio/faad update. compile-tested only. Index: patches/patch-src_aac_libmp4_c === RCS file: /nfs/obsd0/cvs/ports/audio/audacious-plugins/patches/patch-src_aac_libmp4_c,v

Re: fix: audio/audacious-plugins

2009-01-31 Thread Federico G. Schwindt
On Sat, Jan 31, 2009 at 10:51:49PM +0100, Tobias Ulmer wrote: fix audioplayer with unspeakable name, fallout of earlier audio/faad update. compile-tested only. i will take a look as i have some changes to this port that i can add to the commit. f.-