openbsd-ports/audio/jack/patches/patch-jack_pc_in

$OpenBSD: patch-jack_pc_in,v 1.2 2008/06/28 05:49:30 jakemsr Exp $
--- jack.pc.in.orig	Thu Mar 13 16:40:00 2008
+++ jack.pc.in	Wed Jun 18 00:42:56 2008
@@ -6,5 +6,5 @@ includedir=@includedir@
 Name: jack
 Description: the Jack Audio Connection Kit: a low-latency synchronous callback-based media server
 Version: @JACK_VERSION@
-Libs: -L${libdir} -ljack -lpthread @OS_LDFLAGS@
+Libs: -L${libdir} -ljack -lm -pthread @OS_LDFLAGS@
 Cflags: -I${includedir}
maintainence update, plus - fix build on alpha by not comparing a va_list to NULL. problem noticed and fix tested by merdely@. - fix possible 100% cpu usage in full-duplex mode - fix net client/server - add @bin markers to PLIST 2008-06-28 01:49:30 -04:00			$OpenBSD: patch-jack_pc_in,v 1.2 2008/06/28 05:49:30 jakemsr Exp $
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@ 2008-03-23 23:01:28 -04:00			`--- jack.pc.in.orig Thu Mar 13 16:40:00 2008`
maintainence update, plus - fix build on alpha by not comparing a va_list to NULL. problem noticed and fix tested by merdely@. - fix possible 100% cpu usage in full-duplex mode - fix net client/server - add @bin markers to PLIST 2008-06-28 01:49:30 -04:00			`+++ jack.pc.in Wed Jun 18 00:42:56 2008`
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@ 2008-03-23 23:01:28 -04:00			`@@ -6,5 +6,5 @@ includedir=@includedir@`
			`Name: jack`
			`Description: the Jack Audio Connection Kit: a low-latency synchronous callback-based media server`
			`Version: @JACK_VERSION@`
			`-Libs: -L${libdir} -ljack -lpthread @OS_LDFLAGS@`
maintainence update, plus - fix build on alpha by not comparing a va_list to NULL. problem noticed and fix tested by merdely@. - fix possible 100% cpu usage in full-duplex mode - fix net client/server - add @bin markers to PLIST 2008-06-28 01:49:30 -04:00			`+Libs: -L${libdir} -ljack -lm -pthread @OS_LDFLAGS@`
import jack (jack-audio-connection-kit) JACK is a low-latency audio server, written for POSIX conformant operating systems. It can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin"). JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation. ok kili@ 2008-03-23 23:01:28 -04:00			`Cflags: -I${includedir}`