From 6a6c43798f9205239189404501b7bc4afd3283bf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Duval?= <korli@users.berlios.de>
Date: Fri, 4 Aug 2006 19:20:01 +0000
Subject: [PATCH] have ring_buffer built on non-haiku platforms

git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@18391 a95241bf-73f2-0310-859d-f6bbb57e9c96
---
 src/system/kernel/util/ring_buffer.cpp | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/system/kernel/util/ring_buffer.cpp b/src/system/kernel/util/ring_buffer.cpp
index 752ab017c6..359500a112 100644
--- a/src/system/kernel/util/ring_buffer.cpp
+++ b/src/system/kernel/util/ring_buffer.cpp
@@ -7,11 +7,16 @@
 #include "ring_buffer.h"
 
 #include <KernelExport.h>
+#if 0
 #include <port.h>
+#endif
 
 #include <stdlib.h>
 #include <string.h>
 
+#ifndef HAIKU_TARGET_PLATFORM_HAIKU
+#define user_memcpy(x...) (memcpy(x), B_OK)
+#endif
 
 /**	This is a light-weight ring_buffer implementation.
  *	It does not provide any locking - you are supposed to ensure thread-safety